How AssetChain protects your assets

• Reserves are controlled by contract code only. Nobody — not the team, not even the Safe — can move backing. Tokens leave a vault only through a valid burn-on-Base.
• Governance (fees, caps, pause, peers, fee treasury) runs through a Gnosis Safe multisig, 3-of-5, on both chains.
• Operations (PayDirect payments on Base) use agent keys with zero bridge-admin power.

Each onboarded token gets its own vault contract. A malicious, upgradeable, or broken token can only ever affect its own reserve — never another token's. This containment is the single most important property of a multi-token bridge.

The amount minted on Base can never exceed the amount locked on BSC. Locking is enforced by LayerZero's OFT lock-and-mint model, and our indexer continuously checks vault.balanceOf(token) == oft.totalSupply() for every token. Any drift is surfaced immediately on the dashboard.

You connect your own wallet and hold your own Base tokens. AssetChain never takes custody, never holds your keys, and cannot freeze or reverse your transactions. That also means you are responsible for the transactions you sign — see the risk disclaimer.

Anyone can onboard a token — there's no gatekeeper. The safety comes from an on-chain validator that simulates a transfer and rejects fee-on-transfer / rebasing / non-standard tokens before a vault is ever deployed. A token being listed is not an endorsement.

• Audit: not yet completed. The contracts pass a full local test suite (including a lock→mint→burn→unlock round-trip), but no third-party audit has been published.
• Mainnet: not live. We deploy to mainnet only after an audit and once the Safe is configured.
• Until then, treat everything as testnet / experimental.