Skip to content
VaultDock logoVaultDock
fomo

Blocks / recipe

Fee furnace

Burn a share of your pons token fees for good; the rest of the tokens and all the ETH go to your team.

A recipe is several blocks wired together and deployed as your own copies in one transaction.

This pons recipe takes 2 transactions: one to deploy everything, then one to make your PonsFeeSink your fee recipient on pons.

Deploy this recipeReviewedA person reviewed the code against a checklist. No external audit yet.

What it does

No README published.

The parts, deployed together

A recipe is only as trusted as its lowest-tier part, and caps follow that tier.

  1. Step 1

    Fee splitter v1

    Burns the token share, pays the team

    Reviewed
    Protocol fee per lane
    LaneFee
    Splitter inflowwhen money enters from outside VaultDock (deposits and direct transfers). Free when it comes from your pons fee sink, and free on the way out to your vault.0.5%

    Fees are fixed into each contract at deploy and can never change for it. Claims, withdrawals and refunds are never charged. Hard cap 1%, written into the code.

  2. Step 2

    Pons fee sink v1

    Receives your pons fees

    Reviewed
    Protocol fee per lane
    LaneFee
    pons creator feesonce, on every pons fee collected (ETH and tokens). Nothing more is charged when the sink hands it to your splitter or vault.0.5%

    Fees are fixed into each contract at deploy and can never change for it. Claims, withdrawals and refunds are never charged. Hard cap 1%, written into the code.

Risks in plain English

  • The recipe's tier is the lowest of its parts.
  • Step 2 moves your future pons fees to the sink. Claim what is already credited to your wallet first.
  • Burned tokens are gone for good: the total supply goes down.

What if…

What if I skip step 2?
Nothing flows. The contracts sit idle until the sink is your fee recipient.
What if I want a different burn share later?
The splitter changes through a public 72-hour timelock, unless you locked it forever.
What if the team wallet can't receive ETH?
Its share is kept as owed and the team wallet can claim it later. Burns still happen.

Settings you choose at deploy

  • Your pons tokenLocked forever
  • Team walletGets all the ETH fees and the unburned share of token fees.Changeable
  • Share of token fees to burnChangeable
  • Also try to sweep pending pool feesUsually skipped: pons only lets its operator run sweeps that need a swap.Changeable