A swarm of GPUs on Robinhood Chain. Read the docs

Token and launch

$ZKMOSQ launches on Pons v2 on Robinhood Chain, paired against NVDA. Pons deploys the token, the whole supply goes on the bonding curve, and 0.70% of every trade is paid to stakers in NVDA.

Launch on Pons v2

There is no Mosquito token contract. Pons v2 deploys the ERC-20, sells it on a bonding curve priced in NVDA, and on graduation moves the liquidity into a locked Uniswap v4 pool. The GPU network’s token trades against the company that makes the GPUs.

ParameterValue
Pair assetNVDA (NVIDIA • Robinhood Token). Buyers pay in NVDA and the curve graduates in NVDA.
Supply1,000,000,000 ZKMOSQ, 18 decimals. No mint after launch.
Allocation100% on the bonding curve. No team, VC or treasury allocation is minted. The team can buy on the curve like anyone else and discloses it if it does.
Trade fee1% on every trade, on the curve and after graduation. The pool’s LP fee is 0; the Pons hook charges the fee instead.
Creator share70% of the fee, which is 0.70% of every trade, paid in NVDA to the creator-fee recipient: the stock vault.
GraduationAt 41.6 NVDA, into a locked Uniswap v4 ZKMOSQ/NVDA position.
BuybackOff. Pons can divert part of the creator share to buyback-and-burn; the launch disables it so the whole creator share reaches stakers.
Creator taxOptional extra trade tax of up to 10%, paid entirely to the creator-fee recipient. A launch decision; the default is 0 to keep trading cheap.
Launch fee0.0005 ETH, paid once by whoever launches.

Where the fee goes

Pons credits the creator share to a per-recipient, per-token balance in its fee escrow, in the pair asset. For $ZKMOSQ that is NVDA, and the recipient is the stock vault.

Trade: 100 NVDA1% fee = 1 NVDAPons 30%Vault 70%0.30 NVDA to Pons0.70 NVDA to the vault, streamed to stakers

Example: one 100 NVDA trade. Pons charges 1% on every trade, on the bonding curve and after graduation, keeps 30% of it and credits the rest to the creator-fee recipient in NVDA.

Handing fees to the vault

After launch the current creator-fee recipient calls factory.transferCreatorFeeRecipient(token, vault). It takes effect at once and only the current recipient can call it. The vault has no function to pass those rights on, so nobody on the Mosquito side can redirect them later.

The alternative is to launch with the vault already set as creatorFeeRecipient, deploying the vault first against the token’s precomputed CREATE2 address. Separately, the Pons owner has a recovery path, setCreatorFeeRecipient, behind a public 3-day timelock and a 3-day execution window.

Reading and pulling the vault’s fees
escrow.balanceOfToken(vault, NVDA)   // what harvest would pull
vault.pendingHarvest(NVDA)            // same number, read through the vault
vault.harvest(NVDA)                  // escrow.claimToken(NVDA), then sync(NVDA)

Access tiers

Live inference is gated on holding $ZKMOSQ. Your on-chain balance sets the tier; nothing is spent. Pay-per-call in $ZKMOSQ through Permit2 also exists in the code and is switched on per deployment.

TierHoldUseRouting
TrialNothingPreview onlyStandard
Starter10,000 ZKMOSQ~2 hrs/day · 500 req/dayStandard
Pro50,000 ZKMOSQ~8 hrs/day · 2,000 req/dayPriority
Max250,000 ZKMOSQFair use · 10,000 req/dayTop priority

Contracts

Robinhood Chain mainnet. Pons and Uniswap addresses are read from the Pons factory.

ContractAddress
$ZKMOSQPublished at launch
MosquitoStockVaultPublished when deployed
NVDA stock token0xd0601ce157db5bdc3162bbac2a2c8af5320d9eec
NVDA / USD Chainlink feed0x379EC4f7C378F34a1B47E4F3cbeBCbAC3E8E9F15
USDG (Paxos)0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168
Pons v2 launch factory0x7ed598bcef8bd9edd8c97a195c6d13f40801ec7e
Pons v2 launch router0xe33e9e479df8802cb0866d5d05258bec4cf62948
Pons v2 meme hook0xE5e702641Ea86F4ae6cC3cDaeD2B886f976Be044
Pons v2 fee escrow0xd3AFEB2a57f70eF218Aa82451c51B2fb0416Ac9e
Pons v2 launch locker0x267444D099b10fB5Ed7c3Cc7B7c767AdcA574952
Uniswap v4 PoolManager0x8366a39CC670B4001A1121B8F6A443A643e40951
Uniswap v4 PositionManager0x58daec3116aae6D93017bAAea7749052E8a04fA7
Permit20x000000000022D473030F116dDEE9F6B43aC78BA3