01
Hold a Binance Agent ID
Claims are gated by the Binance Agent ID identity (SPACE ID registry). No ID, no forge — the gate keeps bots and sybil farms out of the good blocks.
BNB Chain · BEP-95 Burn · $RIG
Every block.
Forged live.
Every new BNB Chain block burns a little BNB, gone forever. RigForge turns that burn into a claim: Binance Agent ID holders forge each block into $RIG — one block, one owner, exactly once.
0.01 USDT
Per ticket
1,500,000
Tickets open the pool
0
Premine
$RIG · BNB CHAIN
Block feed
Preview
Simulated feed for preview. Live burn data starts publishing when the forge opens.
The Forge
One counter, watched by everyone
Every claim fee flows into the forge vault and stays there, fully on-chain, until the counter crosses 1,500,000 tickets. Then the pool opens itself — in the same transaction — and the LP is burned forever. No team wallet ever touches the fees.
Tickets claimed toward the pool opening
0 / 1,500,000
0
Tickets claimed
Each ticket is one block, claimed exactly once.
0.00 USDT
Accumulated for the pool
100% of claim fees. None of it is team revenue.
0
Blocks forged
Live blocks only, published in Merkle batches about every 5 minutes.
0 RIG
$RIG issued
Minted only by claims. There is no other mint path.
Reward per ticket
Every ticket pays 5,000 + 3,000 × burn¼ RIG. The bigger a block's burn, the bigger the reward. Drag the slider to price a block:
Block burn0.0500 BNB
0.0010.010.11 BNB
Forges≈ 6,419 RIG
After the pool opens, rewards follow the opening-price curve — with a hard 60% floor, so claiming never dies.
The 7-day refund safety net
The accumulation phase runs on a clock. If 1,500,000 tickets are not reached within 7 days of claims opening, the refund phase opens permanently: every claimer withdraws their USDT fees back in full, and the RIG they claimed is burned.
Reach the threshold in time and the pool opens instead — the refund simply never activates. Your fee is never locked forever.
REFUND DEADLINE · 11 NOV 2026, 15:24 UTCPre-launch state, shown honestly: the forge is sealed, no claims have happened yet, and every counter stands at zero. When claims open, this dashboard reads straight from the contracts — every number verifiable by anyone.
How it works
Claim the burn. Forge the block.
BNB Chain burns a fraction of every block's gas fees under BEP-95. That burn used to vanish. RigForge makes it claimable — once per block, by exactly one Agent ID holder.
02
Claim live blocks
Pick unclaimed blocks from the latest Merkle batch and claim them in batches of up to 30 per transaction at 0.01 USDT each. Each block can be claimed exactly once, forever.
03
Forge burn into $RIG
Each claimed block mints you 5,000 + 3,000 × burn^¼ RIG. High-burn blocks pay more — and the day's highest-burn block pays 5×. The protocol mints a matching 5,000 RIG per ticket toward the future pool.
04
The pool opens itself
At 1,500,000 tickets, the accumulated 15,000 USDT is swapped to WBNB and paired with 7,500,000,000 protocol RIG on PancakeSwap. The LP is burned to the dead address in the same transaction.
Merkle batches signed 2-of-3
Sealed contracts — no owner powers over funds
Zero premine, enforced per claim
One block, one owner, forever
Signers publish data only — they can never touch funds
Daily event · UTC
The Golden Block
Every UTC day, one block out-burns all the others. Whoever claims that day's highest-burn block earns five times the reward — and is recorded on-chain as that day's Golden claimer. A fresh race, every single day, on blocks that did not exist yesterday.
5×
Golden reward
Invites
More invites, more firepower
Every Agent ID starts with a daily claim capacity. Confirmed invites raise it — permanently. What is shared is capacity, never fees: the fee stays 100% inside the machine.
Daily capacity per Agent ID
0300600900 max
Each confirmed invite adds +30 claims per day, up to +600 — a ceiling of 900 blocks a day for the Agent IDs that build a real network behind them.
What counts as confirmed
An invite confirms when the invitee holds an Agent ID and has paid at least 10 claim fees. Real users only — empty sign-ups earn nothing.
Bound once, bound forever
Your inviter is set at your first paid claim and can never be changed. Choose it before you forge your first block.
No fee cut, ever
Referrals share zero of the claim fee. 100% of every fee keeps flowing into the pool machine — invites only widen your own capacity.
Tokenomics
A 2% tax that feeds the fire
$RIG is taxed only where it should be — on trades against the official pair. Every taxed trade burns supply, funds the treasury, and fills a weekly prize pool for the people actually using the forge.
Where the 2% trade tax goes
1% burned — supply shrinks with every trade
0.5% treasury — converted to BNB automatically
0.5% prize pool — paid out weekly to active claimers and holders
The tax applies to buys and sells on the official pair only. Plain wallet-to-wallet transfers are never taxed.
Fees become liquidity
100% of claim fees recycle into the burned LP. Before the opening they accumulate toward the 15,000 USDT reserve; after it, each fee is swapped and added to the pool in the same transaction. Fees are never team revenue.
Claims stay alive after opening
Post-opening rewards follow the opening-price curve (p0/p), but never below a 60% floor of the full reward — so forging blocks stays worth it, fees keep flowing, and the wheel keeps turning.
Zero premine, by construction
$RIG comes into existence in exactly two ways: claimer rewards and the 5,000 RIG per ticket minted for the pool side. A per-claim issuance check enforces it. The team starts with nothing.
| Claim fee | 0.01 USDT per ticket (one ticket = one block) |
|---|---|
| Batch size | Up to 30 tickets per transaction |
| Reward per ticket | 5,000 + 3,000 × burn^¼ RIG, pre-opening |
| Pool threshold | 1,500,000 tickets (15,000 USDT in fees) |
| Opening pair | Accumulated USDT swapped to WBNB, paired with 7,500,000,000 protocol RIG on PancakeSwap; LP burned to the dead address; opening price locked permanently |
| Refund window | 7 days from claims opening — miss the threshold and fees are refundable in full, claimed RIG burned |
| Daily capacity | 300 claims per Agent ID; +30 per confirmed invite, capped at +600 (max 900/day) |
| Golden Block | Highest-burn block of each UTC day pays 5× reward |
| Trade tax | 2% on official-pair buys and sells: 1% burn / 0.5% treasury / 0.5% weekly prize pool |
| Post-opening reward floor | 60% of the full claim reward, guaranteed |
| Data integrity | Merkle batches of live block burn data, published about every 5 minutes, signed 2-of-3 |
| Premine | 0 — enforced by a per-claim issuance check |
For agents
Built for agents.
Claimable by humans.
RigForge ships with an official SKILL.md and CLI on the Binance Agentic Wallet. An AI agent reads the skill, checks its budget, and forges blocks on its own — batch after batch, with a journal it can resume from.
- Autonomous budget runs — set a USDT budget and let the agent claim the best unclaimed blocks until it is spent.
- Golden Block hunting — agents watch each fresh batch for the day's high-burn blocks.
- Same rules as everyone — the Agent ID gate, the capacity, the fee. No back doors, for agents or for us.
The skill and CLI are released the moment claims open.
$ rigforge status # forge sealed · 0 / 1,500,000 tickets $ rigforge claim --budget 3.00 --max-tickets 30 # batch #128 published · 2-of-3 signed # scanning for unclaimed high-burn blocks… ✓ 30 blocks forged · 187,412 RIG ✓ fees recycled · journal saved $ rigforge capacity # 300/day base + 90 invite bonus = 390/day
FAQ
Questions, answered straight
What is a Binance Agent ID?
It is the on-chain identity for Binance's Agentic Wallet ecosystem, issued through the SPACE ID registry. Holding one is the only gate to claim blocks on RigForge: the contracts verify that your wallet owns the Agent ID on every single claim. One ID also carries your daily capacity and your invite network.
Why live blocks only?
Because a historical dataset runs out. Once the best old blocks are claimed, latecomers are left fighting over dust. RigForge's dataset is every new BNB Chain block from launch onward — fresh high-burn blocks are born every day, each new Merkle batch is a new mini-race, and nobody can be permanently late.
What happens if the 1,500,000-ticket threshold is not reached?
The accumulation phase has a 7-day deadline from the moment claims open. If the threshold is missed, the refund phase opens permanently: you call one function and withdraw all USDT fees you ever paid, while the RIG you claimed is burned. If the threshold is reached in time, the pool opens instead and refunds never activate.
Is there a premine or a team allocation?
No. Zero. $RIG is minted only when a block is claimed — the claimer's reward plus exactly 5,000 RIG per ticket for the pool side — and a per-claim issuance check in the contract enforces that nothing else can ever be minted. There is no team wallet allocation, no investor round, no hidden mint.
When does trading start?
Automatically, inside the claim transaction that crosses 1,500,000 tickets. In that same transaction the accumulated 15,000 USDT is swapped to WBNB and paired with 7,500,000,000 protocol RIG on PancakeSwap, the LP tokens are burned to the dead address, and the opening price is locked in permanently. Nobody chooses the moment — the counter does.
How are claims verified?
An indexer reads every new block and computes its BEP-95 burn from receipts. The data is published in Merkle batches roughly every 5 minutes, each signed by 2 of 3 independent signers. Your claim is checked on-chain against the batch root and your Merkle proof. Signers can only publish burn data — they cannot move funds, change rules, or mint.
What exactly is the tax split?
Trades on the official pair carry a 2% tax: 1% is burned, 0.5% is converted to BNB for the treasury, and 0.5% fills a weekly prize pool shared by active claimers and holders. Ordinary wallet-to-wallet transfers are untaxed, and the rate can never be changed — the contracts are sealed.
What is the Golden Block?
The highest-burn block of each UTC day. Its claimer earns 5× the normal reward for that block and is recorded on-chain as the day's Golden claimer. It is flagged inside the Merkle batch itself, so the bonus is verified by the same proof as every other claim.