BlackSwan Smart Contract Addresses, ABIs, and Networks

Deployed BlackSwan contract addresses on Polygon Amoy and Ethereum Sepolia testnets, with links to block explorers and ABI access via the SDK.

BlackSwan’s core logic lives in two smart contracts deployed on each supported testnet: P2PLending, which manages on-chain peer-to-peer lending interactions and credit state, and BlackSwansSBT, the Soulbound Token contract that anchors a non-transferable credit identity to each wallet. Use the addresses below to verify deployments on the block explorer or to interact with the contracts directly.

Polygon Amoy (Testnet)

Contract	Address	Explorer
P2PLending	0x7E04C0a283d372537E547086D37642776199C1DC	View on Polygonscan
BlackSwansSBT	0x6665e5E15Ee295d9de05C6D57c629F33653687D7	View on Polygonscan

Ethereum Sepolia (Testnet)

Contract	Address	Explorer
P2PLending	0x20D2E08E283FF4052B2B02A3475dda1B320cD26f	View on Etherscan
BlackSwansSBT	0xf8D2F43227Ea25a7fD0B34E1b74FF6FF2722879F	View on Etherscan

ABIs

You don’t need to source ABIs manually. The BlackSwan JavaScript SDK exports fully typed contract references — including addresses and ABIs — as named exports for each network:

import { AMOY_CONTRACTS, SEPOLIA_CONTRACTS } from "blackswan-sdk";

// Access the P2PLending contract address on Amoy
const lendingAddress = AMOY_CONTRACTS.P2PLending.address;

// Access the ABI for direct use with ethers.js or viem
const lendingAbi = AMOY_CONTRACTS.P2PLending.abi;

Both AMOY_CONTRACTS and SEPOLIA_CONTRACTS expose address and abi fields for each contract, making it straightforward to instantiate contract instances with your preferred Web3 library.

Mainnet contract deployments are planned for v1.1. Once live, addresses for Polygon mainnet and Ethereum mainnet will be published here and exported from the SDK as POLYGON_CONTRACTS and ETHEREUM_CONTRACTS. See the Roadmap for the full release timeline.