Left - the three-percent function. This is not market history. It is the deterministic relationship committed at launch: for every 100 units of VANNO trading volume, 3 units accrue as creator tax in the pairing asset. The line is mathematical, so it can be shown before the token begins trading.
Right - the allocation route. pons accounts for the full 3% creator tax in fee escrow. Policy then assigns 2% of volume to PONS acquisition and 1% to VANNO repurchase and permanent removal from circulation. No portion is reserved for team operations.
Explanatory instrument only. No token price, trading volume, tax balance or PONS holding is represented as live data. Those fields remain TBA until the relevant addresses exist.
What VANNO is
VANNO is an onchain treasury project built around two linked objectives: accumulate PONS and reduce circulating VANNO through market buybacks. It is issued through pons v2 on Robinhood Chain with a creator tax fixed at three percent when the launch is created.
The project borrows the central insight of digital-asset treasury companies without pretending that an onchain token is a registered public share. A treasury company uses access to capital and market demand to expand a strategic reserve. VANNO uses protocol-native trading revenue. Every buy and every sell produces a measurable inflow in the pairing asset; that inflow can be claimed, converted and placed into a public PONS treasury.
The product is therefore not merely the VANNO token. It is the relationship between VANNO activity, the PONS reserve and VANNO circulating supply: two percent grows the reserve while one percent funds permanent market removal.
The treasury engine
pons v2 separates an optional creator tax from its standard trading fee. VANNO sets that creator tax to 300 basis points. The rate is committed at launch and cannot later be raised. Fees are assessed in the launch's pairing asset rather than deducted from VANNO itself.
Buy and sell volume passes through the pons curve and, after graduation, its Uniswap v4 hook.
The creator tax is accounted for by pons and becomes claimable by the designated recipient.
Two parts acquire PONS. One part repurchases VANNO and removes it from circulation.
If VANNO is paired directly with PONS, the reserve allocation already arrives in the target asset while the buyback allocation purchases VANNO. If paired with ETH, two thirds of claimed ETH acquires PONS and one third repurchases VANNO. The team receives none of the creator-tax allocation.
The three-percent rule
The creator tax is deliberately simple. For gross trading volume V, the gross creator-tax accrual T is:
T = V × 0.03
PONS budget = V × 0.02
VANNO buyback budget = V × 0.01
// operations allocation = 0
The full three percent is protocol-directed: two percentage points toward PONS and one toward VANNO buyback. Market execution still involves gas and price impact, but there is no team or operations percentage. VANNO reports gross allocation and net assets received separately.
At 100 ETH volume: 2.00 ETH targets PONS / 1.00 ETH targets VANNO buyback / 0 operations.
Why PONS
PONS is the reference token of the pons launch ecosystem on Robinhood Chain. It sits close to the source of VANNO's own distribution, market structure and community. A PONS treasury therefore creates an ecosystem-native balance sheet rather than a reserve thesis imported from another chain.
The choice is strategic, not risk-free. PONS liquidity, holder concentration, protocol adoption and market price can all change. VANNO does not claim that accumulating PONS guarantees appreciation. It claims something narrower and verifiable: the project will make its PONS acquisition policy, balances and transactions observable.
The long-term metric is not a slogan or a chart of VANNO's market price. It is PONS per circulating VANNO. Once the token and treasury addresses exist, that ratio can be independently recomputed from public chain state.
Treasury accounting
VANNO will separate operational metrics so that observers can follow the entire route from trading activity to reserve holdings.
| gross volume | Total VANNO buy and sell volume settled by pons. |
| tax accrued | Creator-tax balance attributed to VANNO before it is claimed. |
| tax claimed | Pairing asset moved from fee escrow to the designated collector. |
| execution cost | Gas, slippage and price impact incurred while acquiring PONS. |
| PONS acquired | Net PONS received from the two-percent reserve allocation. |
| VANNO repurchased | VANNO acquired from the one-percent buyback allocation. |
| VANNO removed | Repurchased VANNO deposited into the published permanent-lock address. |
| PONS held | Current reserve balance controlled by the published treasury addresses. |
| PONS / VANNO | The reserve ratio: PONS held divided by circulating VANNO supply. |
Acquisition policy
Taxes accrue continuously, but the protocol should not execute on every trade. Claims are batched, then divided by policy: two thirds acquire PONS and one third repurchases VANNO. Both routes use bounded execution and publish their final destination.
- Claim threshold. Fees remain in pons escrow until the balance is large enough to justify execution.
- Bounded impact. A single purchase may not exceed the published maximum share of available PONS liquidity.
- Minimum output. Each acquisition enforces an onchain minimum amount received; failed conditions defer rather than force the trade.
- Observable routing. Collector, PONS vault and VANNO permanent-lock addresses are disclosed before activation.
- Zero operations share. No percentage of creator tax is assigned to the team or operating wallet.
- No invented NAV. The interface displays unavailable values as unavailable until a reliable onchain calculation exists.
Transparency covenant
Before the first treasury claim, VANNO will publish a registry of relevant contracts and wallets. Changes to operational control will be announced against that registry rather than silently substituted in the interface.
| VANNO token | TBA - created through the pons v2 factory. |
| pairing asset | TBA - finalized and disclosed before launch. |
| fee escrow | Resolved from the pons stack that launches VANNO. |
| fee recipient | TBA - the address authorized to claim VANNO creator-tax balances. |
| PONS vault | TBA - the published address holding strategic PONS reserves. |
| VANNO lock | TBA - the irreversible destination for repurchased VANNO. |
| PONS token | 0x39dBED3a2bd333467115dE45665cC57F813C4571 |
Risks and limits
VANNO is experimental crypto software, not a bank account, stablecoin, ETF or registered share. Its token can lose all value. A growing PONS balance does not guarantee a rising VANNO price, and trading volume can fall to zero.
Material risks include smart-contract failure, pons protocol changes, Robinhood Chain interruptions, thin liquidity, adverse execution, wallet compromise, regulatory treatment, inaccurate third-party indexing and severe movements in PONS or the pairing asset. The 3% creator tax also increases trading friction and may reduce volume.
LANGUAGE MATTERS
"Treasury" describes VANNO's onchain reserve strategy. "Share," "stock" and "equity" should not be used to imply legal ownership in a corporation unless a separate compliant legal structure exists. Nothing on this page is an offer of securities or investment advice.
Launch sequence
Finalize pairing asset, wallets, tax recipient and public treasury policy.
Create VANNO on pons v2 with the fixed 3% creator tax and disclose its CA.
Execute the 2% PONS reserve policy and 1% VANNO repurchase policy onchain.
// VANNO treasury settlement - descriptive policy, not deployed code const CREATOR_TAX_BPS = 300; const RESERVE_ASSET = PONS; const PONS_ALLOCATION_BPS = 6_667;
const VANNO_BUYBACK_BPS = 3_333;
const OPERATIONS_BPS = 0; function settleTreasury() { quote = ponsFeeEscrow.claim(VANNO); require(quote >= CLAIM_THRESHOLD); minPonsOut = oracleQuote(quote) .applyMaxSlippage(MAX_SLIPPAGE_BPS); ponsBudget = quote * PONS_ALLOCATION_BPS / 10_000;
buybackBudget = quote - ponsBudget;
ponsReceived = acquirePons(ponsBudget, minPonsOut); PONS.transfer(PONS_VAULT, ponsReceived);
vannoReceived = repurchaseVanno(buybackBudget);
VANNO.transfer(PERMANENT_LOCK, vannoReceived); emit TreasuryAcquisition( quote, ponsReceived, PONS.balanceOf(PONS_VAULT) ); } // public invariant: // reported PONS held must equal observable balances // across the addresses in the published treasury registry.