nvda lite

Launch through Pons v2 on Robinhood Chain. Trade against tokenized NVDA. Route project fees to a dedicated contract and reserve half to grow liquidity in that same market. The design lets anyone trigger a deposit when the pool and budget are ready.

The token name is not a valuation model. More liquidity means more trading depth at a given price; it does not guarantee demand, profit, a price floor, or the ability to exit at a particular price.

The intended pairing asset is NVIDIA • Robinhood Token. Buyers spend that asset and sellers receive it. Our token is separate from tokenized NVDA; holding it does not make you a shareholder or give you a right to redeem it for NVIDIA shares.

A pair is not a peg. The market price can move against NVDA, and tokenized NVDA can move against dollars. The project is independent and is not affiliated with NVIDIA or Robinhood.

The fee model is 2% on buys and 2% on sells: a 1% Pons base fee plus a 1% creator tax. With native Pons buybacks disabled, Pons takes 0.30%. The remaining 1.70% is intended for our contract, registered as the launch’s creatorFeeRecipient.

The receiver contract splits actual receipts equally between the liquidity budget and the project treasury: a nominal 0.85% each. Half funds liquidity; half remains treasury funding. Launch settings must be confirmed before creation; temporary opening-buy protection and execution costs are separate.

The deployed receiver exposes claimFeesAndInject() to everyone. After the token is launched and bound, it claims available tokenized NVDA fees from Pons, reserves half for liquidity, exchanges part of that budget for our token, and adds both assets to the existing pool after graduation.

The caller starts the transaction and pays gas. The contract controls the split and destination; triggering it gives the caller no right to take the fees or withdraw liquidity.

The vault adds liquidity to its own permanent position in the same pool and exposes no withdrawal, position-transfer, upgrade, or arbitrary-call function. Local and Pons fork tests cover this path. The signed oracle is deployed; independent review and secure reporter operation remain before live injections.

The amount deposited is the liquidity budget after swap fees, slippage, and any allocated operating costs. Sending tokens to a pool address alone does not create active liquidity.

Trading begins on Pons’s bonding curve. At graduation, Pons creates the Uniswap v4 pool and locks its initial liquidity. Our additional permanent position starts only after that pool exists.

Before graduation, the liquidity share accumulates in the fee receiver. If graduation never happens, that budget remains undeployed because the implemented contracts provide no recovery path.

The implemented entry point is public. A community member or an optional bot can trigger the same function without waiting for a team signature. Execution runs in bounded batches when enough fees are available and contract-enforced price checks pass.

The price guard uses a signed 30-minute time-weighted average from confirmed pool events. A quorum of configured reporters must sign the same update; anyone can relay it. Stale, future, replayed, or insufficiently signed reports are rejected.

Pons holds claimable fees in an escrow. The receiver calls claimToken(NVDA) on its own behalf. Some accrued fees first need a sweep, and conversions involving an internal swap require Pons’s authorized operator. Our public function cannot bypass that dependency.

Insufficient funds, a stale oracle, or an unsafe pool price leaves the liquidity budget pending. The caller cannot choose another recipient or weaken price protections. Pons’s native buyback-and-vesting option stays disabled.

The custom source and integration tests are published. Before launch, the final signer setup and price policy need independent review, followed by verified deployment addresses. The fee recipient, liquidity lock, administrative powers, and fee-routing dependencies remain inspectable.

The site now reads claimable fees, treasury balances, and funds awaiting reinvestment from the deployed receiver. Until launch transactions exist, those balances remain zero and the displayed fee split is the configured launch plan.