vampchain

The mechanics

How fees actually work

Every transaction on a vampchain generates revenue. It's made two different ways on the vampchain — but by the time it's yours to withdraw on the base chain, it's one pool.

Where it comes from

Two sources, one pool

Gas on a vampchain has two parts, generated the ordinary Ethereum way — a tip and a base fee. They're handled differently on the vampchain, but both end up as the exact same thing: withdrawable revenue on the base chain.

Tips

Every transactionPiles up at the chain's wallet

A small tip on top of every transaction lands as real balance and just accumulates there — nothing ever has to move. We keep an exact running count.

Base fee

🔥
Every transactionDestroyed on the vampchain

The rest of the gas fee is destroyed outright — standard Ethereum rules. Burning it on the vampchain frees up an exactly-equal amount of backing on the base chain, which becomes real funding. We keep an exact running count of it too.

So the tip/base-fee distinction only matters for how it's created. Once it's revenue you can withdraw, it's a single number — that's all the rest of this page is about.

Split three ways

Every claim pays three parties, automatically

Whichever kind of revenue it is, once it's claimed it splits the same way: a third to whoever created the chain, a third to the protocol, and a third into a wallet dedicated to keeping the chain funded.

Creator

Protocol

Runway

Every claim splits into three equal shares. Any leftover wei from rounding (0–2 of them) tops off the runway share — nobody else is ever shorted.

No single address can redirect this or block another party from getting paid — every recipient is looked up live from the contract itself, never chosen by whoever submits the claim.

One counter, one claim

How the running total works

Your revenue is one number that only ever goes up. Two lines matter: the total earned so far, and how much has already been paid out. What you can claim right now is simply the gap between them — and one transaction always takes the whole gap, whether you claim after a day or a year.

Press the buttons: let time pass, then claim, and watch the paid-out line jump up to meet the total.

total earnedtime →

0

total earned

0

already paid

0

you'd get now

The contract remembers only the dashed line — how much it has already paid. Your claim shows the current top. You get the gap. Same scale on both, so it can never pay past the top.

Both lines live on the same scale, counted from the same zero. The contract stores only the paid-out line and pays you the distance up to what your receipt shows — so it can never pay past the top, and the same revenue can never come out twice.

Who actually does this

Anyone can press the button — and that's safe

Anyone can submit the claim, because the button doesn't choose where the money goes. The three destinations (creator, protocol, runway) are fixed in the contract. Whoever clicks it just pays the gas; the money always lands in the same three places.

So there's nothing to steal by racing you to it. If someone submits before you do, they've just paid gas to send your money to you — and your transaction simply sees it's already done and stops. In practice it's the chain's creator or a small script pulling revenue in whenever it's worth the gas.