Launch token · Not launched
To be created through the Pons v2 factory with tokenized NVDA as its pairing asset. The project token address will be published here after launch.
source code, not source of wealth
The receiver and signed oracle are deployed and source-verified on Robinhood Chain. The token has not launched and the receiver has not been bound, so the permanent vault does not exist yet.
The receiver, locked vault, signed oracle, and reporting tools have local tests. A live-state fork test creates a new token through the real Pons V2 factory, installs our receiver as fee recipient, binds the launch, and creates the permanent vault. Independent signer operation, reporting-policy review, and an independent contract security review remain outstanding.
Open the deployed receiver on Blockscout
Open the deployed oracle on Blockscout
View the public NVDA lite contracts repository
The liquidity system
Liquidity fee receiver · Deployed · verified
Deployed at 0x13038CeFF8B614226816a4A42988c21c12fF8039. It will claim its own Pons escrow balance and split actual receipts equally between liquidity and the fixed project treasury.
Liquidity vault · Created after launch binding
The receiver creates this permanent full-range vault when the Pons launch is bound. The token does not exist yet, so there is no vault address yet.
claimFeesAndInject() · Deployed · waits for launch
The public function is present on the receiver. Anyone can connect now; fee collection and injection become actionable after the Pons token is launched and bound.
payTreasury() · Deployed · no fees accrued
Anyone can submit the call, but it pays only the accrued developer share to the immutable treasury address and cannot access reserved liquidity.
Signed price reference · Deployed · verified
The 6-of-10 signed oracle is deployed at 0x4061185f8431264a3c1ab44727c0622cdd134e29. Reporter operation and the calculation policy still require independent review before live injections.
Protocol references
These are third-party references, not proof that our integration has been deployed or independently audited.
What must be verifiable before launch
- The actual Pons launch, pairing asset, fee policy, and creator-fee recipient.
- Published custom source and compiler settings matching deployed bytecode.
- The 50/50 split of contract receipts between liquidity and the project treasury, cost accounting, and handling of pending funds.
- Liquidity position ownership, permanent withdrawal restrictions, and every administrative power.
- Integration tests for public callers, graduation, fee collection, swaps, failed execution, reentrancy, and liquidity increases.
- Fixed execution destinations and price protections that a public caller cannot weaken.
- Security-review results and any remaining Pons fee-routing or operator dependencies.
The receipts belong here
The receiver and oracle transaction records are linked above. After launch and binding, this page will add the token, vault, pool, position ownership, and completed reinvestment transactions.