Proof
Everything on this site that can be checked from the outside is listed here. Sixteen contract deployments across two mainnets serve the Solidity I wrote, readable on their explorers rather than compiled past you, and the rest of the deployment is listed underneath them. A third party audited the protocol before launch and those reports are public too. The critical finding closed the day the audit opened, every remediation shipped before mainnet launch, and nothing here has been exploited.
Third party audit
Grey Swan audited the protocol before mainnet launch. I ran the engagement as the release gate rather than a formality, from scoping through remediation and verification. The reports are public and I would rather you read them than take my word:
github.com/Portaldefi/security-audit-reportOne thing to know before you read the two lists. Ethereum mainnet carries the token, the gateway and the liquidity path, so its transaction counts are modest by design. The matching engine, the settlement path and the penalty and incentive machinery run on Portal chain, which is where the protocol's volume actually sits: the orderbook contract there has processed over eleven thousand transactions. Both chains have public explorers and every address below links into one.
Ethereum mainnet
Source verified and readable · 9
Open any address below and the Contract tab serves the Solidity, not bytecode. That is the part worth checking: a deployment proves something exists, verified source proves who wrote it and what it does.
InvoiceManager
2025-11-22
The settlement core: invoice creation, payment, settlement and locked fund recovery on the hash timelocked path.
NativeLiquidityManager
2025-11-22
Native asset liquidity accounting on the Ethereum leg.
ValidatorRegistry
2025-11-22
The validator set the settlement path checks against.
ValidatorRegistry
2025-12-02
Second registry deployment, ten days after launch.
LiquidityManagement
2025-12-26
Liquidity provisioning and accounting for the swap path.
SwapManagement
2025-12-26
Swap lifecycle management across the two legs.
SwapBroker
2026-01-30
The broker contract routing swaps into the settlement path.
PortalToken
2025-08-21
The PTB token implementation, an upgradeable ERC20.
PortalToken proxy
2025-08-21
The ERC1967 proxy the token is used through, deployed through the CREATE2 factory and owned by the foundation Safe.
Deployed, source not published · 3
Live on Ethereum mainnet from the same deployment machinery. The team never published source for this batch.
InvoiceManager
2026-02-09
Second settlement core deployment.
NativeLiquidityManager
2026-02-09
Second native liquidity deployment.
PortalGateway
2026-02-09
The gateway contract users enter the protocol through on the Ethereum side.
Portal chain
Source verified and readable · 7
Open any address below and the Contract tab serves the Solidity, not bytecode. That is the part worth checking: a deployment proves something exists, verified source proves who wrote it and what it does.
OrderbookMarket
2025-11-30
The onchain orderbook itself: a red black tree over price levels with a linked list inside each level. This is the contract the matching engine case study is about, and it carries the protocol's trading traffic.
OrderMatchingLib
2025-11-30
The matching logic that crosses orders against the book, called by the market through DELEGATECALL, which is why it holds no transactions of its own.
SwapManager
2025-12-03
The swap lifecycle on the Portal chain leg, from committed quote through settlement or unwind.
LiquidityManager
2025-11-30
Liquidity accounting under the book.
AssetManager
2025-12-03
Asset registry and ERC-6909 multitoken balances, so new assets onboard as data rather than as a redeploy.
PenaltyManager
2025-12-03
The penalty side of the incentive design, the part that makes stalling cost more than completing.
ValidatorRegistry
2025-11-30
The validator set on the Portal chain side.
Deployed, source not published · 2
Deployed on Portal chain from the same machinery, source not published. Both are internal libraries the contracts above call through.
OrderbookMathLib
Price and size arithmetic for the book, rounding directions fixed per call site.
VolumeTrackingLib
Volume accounting feeding the fee mechanics.
One address appears on both chains, holding ValidatorRegistry on Ethereum and VolumeTrackingLib on Portal chain. That is expected rather than a mistake: a contract address on an EVM chain is derived from the deploying account and its nonce, so one deployer running the same sequence on two chains lands on the same address twice. It is a useful thing to be able to read off a deployment.