Docs / faq
Launch status and FAQ
What is available and which destinations remain unconfigured.
Has CARRY launched?
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.
No. The website describes the current planned model and includes clearly labeled educational examples. It does not execute trades, stock purchases or reward claims.
What is implemented locally?
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.
The FundedStaking conservation correction is complete in the local V1 candidate.
RewardFundingVault is implemented and tested locally as the current V1 candidate, not deployed. It provides the bounded ETH → WETH → USDG → FundedStaking path. The local deployment sequence and one-time CARRY/staking bindings are implemented and tested. Reward Funding Keeper V1.2 is implemented, tested and feature-frozen for intended mechanical automation of bounded conversions, but is not production-enabled. Full fork rehearsal, production calibration, security review and deployment remain. ETH awaiting conversion is not funded USDG.
Protocol Reserve custody and control remain unresolved. No specific use or automatic spending of the allocation is guaranteed.
StockTreasuryVault exists locally as a V1 candidate for manually directed SPY/MSFT/NVDA acquisitions using fixed approved routes and hard execution controls. It is not deployed. Local implementation is not production availability or a completed audit.
Where will trading happen?
Through the verified Pons token page before graduation and the verified DEX market afterward. The launch and DEX URLs are not supplied yet; disabled actions are intentional.
Do holders own the stocks or receive a fixed yield?
The Stock Treasury target is protocol-owned tokenized exposure. StockTreasuryVault is a local V1 candidate, not deployed. CARRY holders do not directly own company shares and have no redemption rights against underlying stocks or specific treasury holdings.
No fixed yield, guaranteed APY or CARRY staking emissions. Only converted, deposited USDG can fund schedules.