CREATE
The full fixed supply is minted directly to the Pons curve.
$SHRED / PRE-LAUNCH
$SHRED is the planned optional settlement rail for SHREDDAR services: one privacy operation, one posted price, one completed output. Launching through the public Pons v2 bonding curve on Robinhood Chain.

The intended utility is simple: price and settle completed privacy work for humans, software wallets, and autonomous agents. $SHRED is planned as an optional payment asset—not equity, revenue share, governance, or a requirement to use the SHREDDAR product.
Pons mints the launch supply to its curve. There is no private presale and no pre-minted team grant. A project treasury purchase must use the same public mechanism and will be disclosed with its receipt.
The full fixed supply is minted directly to the Pons curve.
Public buys and sells establish price through the bonding curve.
The curve closes when its configured threshold is reached.
Trading continues in a full-range Uniswap v4 pool with the liquidity position locked by Pons.
Planned and fixed at token creation on the quote leg of ordinary buys and sells.
Current v2 factory setting observed at block 52,964,130.
If the Pons base fee is unchanged at launch. Opening anti-snipe charges are separate.
VERIFIED PROTOCOL SNAPSHOT / 2 SEPTEMBER 2026 / FACTORY 0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e / FINAL LAUNCH TRANSACTION GOVERNS
These are two different moments. At creation, 100% goes to the curve. After launch, the project intends to acquire 20% through that public curve for a disclosed longevity reserve.
Not a completed allocation. No purchase receipt exists yet. The target is 20%, not a pre-mint, and the live balance, acquisition transactions, cost basis, and any later treasury sales will be published before this status changes.
Utility activates only when the corresponding service route exists in code. Until then, every item below is a roadmap commitment—not present-day token functionality.
Pay for one completed privacy operation before an agent calls a model, tool, or external service.
Expose machine-readable prices through HTTP 402 so autonomous clients can pay, verify, and receive one output.
Offer SHREDDAR detection, conceptualization, SHARD, and receipt functions as metered MCP tools.
List bounded privacy work as an agent service that can be requested, delivered, and settled through ACP-compatible workflows.
Let a human or software wallet buy a single completed result without a subscription or prepaid credit balance.
Give higher-volume users a posted per-output schedule and consolidated receipts while every operation remains individually priced.
No subscriptions, prepaid credits, bundles, or consultant tiers. Higher volume changes the posted per-output schedule, not the unit of sale.
The intended 20% position is a long-horizon project treasury target. If acquired and later used or sold, proceeds may fund documented build and operating costs. Holdings are not locked unless a verified onchain lock says so.
Build the local compiler, document tools, agent interfaces, and privacy receipts.
Fund testing, independent review, hardening, incident readiness, and recovery work.
Cover documented infrastructure, model, indexing, and delivery costs.
Develop x402, MCP, Virtuals ACP, SDK, and wallet-native PAYG adapters.
06 / HOLDER + RISK BOUNDARY
Holding $SHRED will not represent equity, ownership, revenue share, a claim on treasury assets, guaranteed access, or an expectation of profit.
Tokens can be volatile, illiquid, or lose all value. Pons, wallets, smart contracts, RPCs, bonding-curve execution, and graduation carry separate risks.
Final addresses, parameters, treasury wallet, transactions, and acquisition status will be published together only after independent onchain verification.