Docs / permissions
Permissions and security
Infrastructure responsibilities and remaining integration work.
Responsibility boundary
Pons handles launch infrastructure, trading-fee collection and permanent LP locking. CARRY is responsible for its planned revenue handling, bounded stock acquisitions, USDG conversions and staking schedules. The website is not proof of deployed or audited protocol logic.
CarryRevenueRouter is implemented locally and frozen as the local V1 candidate. It has not been deployed.
FundedStaking is implemented and tested locally as the frozen V1 candidate. It has not been deployed. Full fork rehearsal, production calibration, security review and deployment remain.
RewardFundingVault is an implemented and tested local V1 candidate, not deployed. StockTreasuryVault is also a local V1 candidate, not deployed. Full fork rehearsal, production keeper enablement, parameter calibration, final feed policy, fork validation, Protocol Reserve custody/control, security review, deployment and final live addresses remain pending. Fresh Pons verification is required immediately before launch. No audit or security certification is claimed.
No fabricated connections
Current planned terms. Pons parameters will be reverified immediately before launch and are not permanently guaranteed. CARRY has not launched. No token address, trading URL, pool address or live balances are published.
External trading actions remain disabled until verified destinations are configured.