THE BNC4
PIGGY BANK
Fill it by trading.
Smash it to redeem.
Every trade pays a tax in BNC4. Most of it is burned or set aside as rewards you claim; the project’s share fills a public reserve you can burn JAR against. Two routes, one tax, both paid in BNC4.
BNC4 in. BNC4 out.
The jar fills from trading tax. Its colour tracks the reserve once a node responds.
Read it off the chain.
Visual only. The gauge tracks BNC4 held in the reserve against fixed marks. It is not a price, a target, or a return.
Every unit of tax, accounted for.
Four dispatches trading tax on a delay, so the token always holds some that has not been sent on yet. Showing only what has already moved makes the contract look like it is short. All three numbers are here, read from the token itself.
Two ways BNC4 reaches you.
Trade
Buy or sell JAR through its BNC4 market on Four.meme. Every trade pays a tax in BNC4.
Fill
Four splits that tax four ways. Part is burned, part is set aside as holder rewards, part goes to liquidity, and the project's share goes to the vault — which banks 90% of what it actually receives as the redeemable reserve.
Claim
Holder rewards are claimed, never pushed. The token keeps a BNC4 balance for you until you go and take it — nothing arrives on a schedule.
Smash
Burn JAR in one atomic transaction and receive its proportional share of the BNC4 reserve.
Redemption does not create additional value. It exchanges a user’s share of JAR supply for the corresponding share of the existing BNC4 reserve.
Where the tax goes
Two things reach a holder, by two different routes. 40% of the tax is set aside as holder rewards you claim from the token itself. 10% goes to the vault, which banks 90% of what it actually receives as the reserve you can burn JAR against.
No fixed percentage of any single trade is promised. Platform fees, dispatch thresholds and timing all sit upstream of the vault, so the reserve grows by what actually lands in it — which is why the ledger above shows tax that has been collected but not yet sent on.
What the contract guarantees
- No withdrawal path for the reserve. BNC4 in the reserve can only leave through proportional redemption — there is no owner function that moves it, and the operations share is accounted separately.
- Burn and payout are one transaction. If any part fails, the whole thing reverts. There is no burn-now-claim-later step.
- A zero payout reverts. You cannot burn JAR and receive nothing.
- Amounts are measured by balance delta, so a fee-on-transfer JAR can never over-credit a redeemer.
These are properties of JarVault’s source, which is verified on BscScan. They do not cover BNC4 itself: BNC4 is an upgradeable beacon proxy with a pause() function, and while it is paused redemption cannot execute. Read the full permissions →