PonsVault

Launch your token
with a vault attached

A vault layer for pons launches on Robinhood Chain. Decide what your creator fees do, and let the contract enforce it.

Pick a vaultDocumentation
vault · $PONSVExampleActive
ConfigurationImmutable
Template
Buyback & Burn
Burn share
80%
Treasury
20% · 0x2f4a…a91c
Buys every
0.05 WETH in fees
Recent runs24h
  • 12:04Burned1,284,910 PONSV
  • 06:02Bought back0.0391 WETH
  • 06:02Harvested0.0489 WETH
  • 00:01Burned902,441 PONSV
  • 18:00Treasury paid0.0098 WETH
Pending fees0.0412 WETH
Callable by anyoneRun vault

One example — a Buyback & Burn vault. Each template has its own controls and its own rule.

01How a vault works

Your fees stop being a payout.
They start doing a job.

On a normal launch, creator fees leave the moment someone claims them. A vault holds them instead and spends them on the rule you picked at launch — on a schedule nobody controls.

Buyback & BurnExample template
Trading fees collect in the pons locker and route into the vault, which spends 80% buying back and burning the token while 20% goes to the treasury.Trading feesWETH · pons lockerVaultimmutable rulesBuy back & burn80% → 0x…dEaDTreasury20% → your wallet
Chain
Robinhood · 4663
Fee asset
WETH
Trigger
Permissionless
Operator keys
None

02Templates

Pick a vault. Ship it with your token.

Each template is a small contract behind a shared beacon, so your token gets its own instance without paying for its own deployment.

Buyback & Burn

Live

Fees buy your token off the open market and send it to the burn address. Supply falls with volume.

  • Burn share
  • Treasury split
  • Fees before a buy

Staking

Live

Holders stake your token and earn the fees in WETH, split by share of the pool. Real yield, and supply locked up while it earns.

  • Lock period
  • Fees before a payout

Lottery

In development

Fees accumulate into a prize pool and pay out to a holder drawn on-chain each round.

  • Round length
  • Prize share
  • Eligibility
  • Draw source

RWA Tax

In development

ETH is reserved for tokenized-stock purchases. Keepers sell supported RWA assets to the vault, and holders can claim RWA dividends.

  • Reserve share
  • Supported assets

03Launching

Four steps, one signature each.

  1. 01

    Connect on Robinhood Chain

    Your wallet stays yours. Every transaction is signed by you, from your own address.

  2. 02

    Choose your vault

    Pick a template and set it up — shares, destinations, how much has to build up before it acts, how much price movement it tolerates. Written once, then fixed.

  3. 03

    Launch through pons

    The token deploys through the pons factory and its creator fees are routed to the vault at creation.

  4. 04

    Let it run

    As trades accrue fees, anyone can trigger a run — you, a holder, or a bot. The vault does the rest.

04Guarantees

What the contract enforces.

Nobody controls the trigger

Running a vault is open to every address, so it cannot be quietly switched off or timed to benefit an insider.

Settings are permanent

Shares, destinations and thresholds are written when the vault is created. Nothing can change them afterwards — not the creator, not us.

Fees never touch a wallet

Collected fees move from the pons locker into the vault. No intermediary address can intercept them.

One vault per token

Each launch gets its own contract holding only that token’s fees. Nothing is pooled, so one token’s activity cannot touch another’s.

Outcomes are verifiable

Burns, prizes and splits are ordinary transfers. Whatever your template does, anyone can audit it from chain data alone.

Runs without you

Our bot triggers each vault once the fees are worth the gas. It has no special permission — if it stopped, any holder could run it instead.

Give your token a reason to hold.

Connect, choose a vault, and launch. It starts working with your first trade.

Launch a token