How the rules
hold.

机制详解。游戏阶段、争夺规则、协议切分、16 条 FAQ。

These are the exact rules the contract follows. Every claim, every fee, every King transition. Read once. Read carefully. Then decide whether to enter. If anything here disagrees with on-chain behaviour, on-chain wins.

Two phases,
three states.

协议生命周期。

The protocol lifecycle has two stages. The presale is a one-off public mint that ends at sell-out and is never re-entered. The live game runs as 24-hour rounds, each ending into the next, looping forever.

★ 预售期
Presale
协议初次部署到预售售罄之间
  • 10.5M REBEL released in one batch at a fixed price of 0.000001 ETH
  • Only the presale buy entry is open; betting / claiming / three-pool buying are unavailable
  • No whitelist, no vesting, first-come, first-served
  • Sellout auto-locks the contract; anyone can then trigger the launch
  • Once the presale ends, it is never re-entered
View presale archive
★ 主场
Live game
上线后所有回合的统称
  • Three buy pools (ETH / USDT / USDC) open; the last qualified buy or legal bet in any pool updates the current King
  • Each round is fixed at 24h (with a +1 minute extension on every qualified action during the endgame, capped at 1h); the jackpot accumulates both ETH and REBEL
  • Betting / exiting are fully enabled in-round; the dividend you earn from betting comes from 80% of other people's newly placed REBEL bets
  • Round-end splits the jackpot 50 / 30 / 10 / 10 across King / three-pool Top 5 / this-round Top 5 bettors / next round's seed; winners claim through the matching entry, paying a 15% protocol fee for 85% net
  • When a round ends the next one begins, looping forever
Go to current round

Who counts
as the king.

谁才算 King。

The rule for the throne is simple: within the current round, the address behind the most recent qualified action (a qualified buy in any of the three pools, or a legal bet) is the current King, and each qualified action overwrites it. The details follow.

  1. 01 · Any pool's last qualified buy (ETH pool > 0.0001 ETH / USDT pool > 0.3 USDT / USDC pool > 0.3 USDC, with at least 1 REBEL received) updates the current King; any legal bet (minimum 1 unit) can also crown you. The three pools each maintain a Top 5 cumulative-buy leaderboard for the round, 15 slots in total, forming the this-round Top 5 reward pool (independent of the King).
  2. 02 · Cumulative buys are counted by the actual REBEL received from each buy (not by ETH spent), i.e. effective REBEL after the 1% protocol fee.
  3. 03 · The moment a round starts, all cumulative buys reset. The previous round's King has no inherited claim in the new round; everyone starts from zero.
  4. 04 · If two addresses end up with identical cumulative buys (extremely unlikely), the throne goes to whichever reached that value first.
  5. 05 · Every flip emits an on-chain event. The last qualified buy or bet decides the final King for the round.
  6. 06 · At round-end the jackpot is split 50 / 30 / 10 / 10: the King takes 50%, the three-pool Top 5 (15 positions) takes 30% weighted [5,4,3,2,1]/15, the this-round Top 5 bettors takes 10% with the same weighting, and the next round's seed pool takes 10%. Winners claim through the matching entry (15% protocol fee, 85% net); unclaimed positions stay in the contract forever and never expire.

Bigger bets,
bigger share.

按占比分红。

Betting does not enter the three-pool buy leaderboards, but any legal bet updates the current King. Dividends only come from 80% of later REBEL bets, split by active share.

When you place a bet, a dividend basis is locked in for you. Every later bet bumps the current dividend basis; swap buy fees do not enter bet dividends and are routed by pool to the jackpot, current King or dev. Your accrued dividend is the gap multiplied by your share. The protocol never needs "active distribution". Your accrued dividend is readable through the contract at any time.

▸ Math appendix (developer-facing, optional)
// Bet unit price (anchored at contract deploy)
bet unit = max(0.0001 ETH-equivalent, 1 REBEL)

// Share earned by betting N REBEL
your share = N / bet unit

// Dividend increment from a later bet
dividend increment = later REBEL bet × 80% / total active share

// Your accrued dividend at any moment
your accrued = your share × (current dividend basis − your basis at bet)

Edge case: cross-round bet. If you still hold a betting position at the end of round #6 going into round #7, your basis is preserved but accrued dividend at the round boundary is snapshotted into a cross-round-pending slot. Your basis only resets when you bet again in the new round. Cross-round-pending must be withdrawn via the settle channel, with a 50% discount.

Two exits,
two penalties.

两种退出通道，两种折损。

There are two exit channels: same-round exit and cross-round settle. Same-round exit takes the 15% fixed protocol fee. Cross-round settle adds an extra 50% discount. No partial exit, rules kept as lean as possible.

同回合退出−15%
触发方式user-called
可用阶段回合进行中
净到账accrued × 85%
副作用your share → 0 · basis → 0

Exit once = take your full accrued dividend = leave this round. Subsequent buys in this round will not generate dividend for you. To keep earning, you must re-bet.

跨回合结算−15% · −50%
触发方式user-called
可用阶段回合进行中 · 回合间歇
净到账accrued × 42.5%
副作用cross-round-pending → 0

Cross-round-pending must be settled before betting in a new round. Old-position dividends are halved first; the claimable half then pays the 15% protocol split, so you net 42.5%. The other half rolls into the current jackpot.

Where the
15% goes.

15% 协议切分去向。

Every claim / settle takes a 15% protocol cut. Where it goes depends on which path. Both are hardcoded at deploy and no account can tune them.

Path A · Winner-prize (King / three-pool Top 5 / this-round Top 5 bettors)
85% winner
15% dev

Three independent claim entries (King reward / three-pool Top 5 reward / this-round Top 5 bettors reward) all route here. The 15% lands entirely in the implicit dev bucket; referrers don't see a cent of it.

Path B · Bettor exit (full this-round / half cross-round)
85% you
9% L1 direct referrer
1% L2 upstream
5% dev / team

The bar above shows the case when both referrer layers are bound. Degenerate cases:
· L1 only (no L2) → L1 takes 10%, dev takes 5%
· No referrer → dev takes the full 15%

User net (same on both paths)gross × 85%
Bytecode hardcodedyes · no account can tune
Tunablenone (no upgrade proxy)

Dev is a single anonymous EOA (DEV_ADDR, immutable at deploy) — no admin, no upgrade, no owner. This 15% is the protocol's only dev income: no team allocation, no private sale, no governance token, no continuous skim. With no referrer bound, dev takes the whole 15%; with referrers bound, the on-chain layers split as shown and referrers pull separately via claimReferralRewards().

Inviting
in 2 layers.

两层邀请关系。

The referrer system is an auxiliary monetisation channel, paying up to two layers upstream (L1 + L2) with three-layer cycle detection. Splits come from the bettor-exit 15% only; the winner-prize 15% never routes through referrers.

Binding a referrer is one-shot: once written, it cannot be modified. The referrer's referrer is walked up the chain on-chain, with no manual designation required from the invitee. Cycle detection walks three layers upstream: the direct referrer can't be you, the second-layer walk can't loop back to you, and the third-layer walk can't loop back to you. This covers all "A → B → A" / "A → B → C → A" style attacks.

▸ Two-tier split breakdown (developer-facing, optional)
// Referrer splits come from the 15% exit fee, bettor path only (this-round 100% / cross-round 50%)
// Winner-prize path: 15% all to dev, no referrer cut

2-layer referrer:  L1 9% + L2 1% + team 5%
1-layer referrer:  L1 10% + team 5%
no referrer:       team 15%

// 1% buy fee split (independent of referrer)
ETH pool:    50% → current round jackpot / 50% → dev
USDT/USDC:   50% → current King instantly / 50% → dev

// Cycle detection (hardcoded at deploy)
A → B → C → A is rejected at binding time
(prevents address-loop farming)

Note: referrer earnings accumulate in dividend mode, not pushed immediately. Referrer positions and betting positions are tracked separately and can be claimed independently. This logic is independent of the round structure; referrer pending isn't reset at round transitions.

Immutable.
Not safe.

不可变。但仍非安全资产。

Immutable rules don't mean zero risk. Below is every known risk, layered, including the parts intentionally preserved by design. Read this before deciding whether to play.

▲ 已知风险清单 · Read carefully

Boundary clauses retained by design: Cross-pool arbitrage can deliberately collect the USDT pool's instant King fee income + the this-round Top 5 ranking + a last-mile King-grab (this is the game mechanism, not a bug). The three-pool Top 5 cumulative leaderboards can be manipulated via multi-pool Sybil play (also a game mechanism). The 1% protocol-fee split, the 50 / 30 / 10 / 10 jackpot allocation, and the 15% to dev on every claim entry are hardcoded and cannot be tuned (this is the immutability guarantee).

Out-of-contract risks the protocol cannot protect against: MEV bots front-running the King race (mempool is public, no commit-reveal); ETH / REBEL secondary market price volatility; regulatory uncertainty (participation may be classified as gambling or a security in some jurisdictions; judge for yourself); your own decision to send funds to this contract.

Reminder: There's no "trust the dev" step (and no dev to trust). The contract is immutable once deployed; rules are guaranteed solely by the on-chain bytecode. The source is publicly published and anyone can verify it independently.

Sixteen
questions, in full.

完整 16 题 FAQ。

The 10 questions from the landing page are kept here in full, plus 6 more covering technical, contested, and legal edges.

01Why no team allocation?Why no team allocation?

A team allocation implies an unquantifiable window of sell pressure, which contradicts the protocol's core "individual expected value is zero-sum" narrative. All 21,000,000 REBEL are minted via the public presale at a uniform price. Anyone who wants chips queues up at the same price, on the same timeline. This is so "zero-sum" holds from day 0.

02How is the protocol fee structured? Is this a rake?How is the protocol fee structured?

Each buy takes a 1% protocol fee. ETH pool: 50% to jackpot, 50% to dev. USDT / USDC pools: 50% sent instantly to the current King as fee income, 50% to dev. Betting layer: 20% of your REBEL bet goes into the jackpot, 80% is split among other active bettors in proportion to their share (independent of the 1% buy fee). At round end the jackpot is split 50 / 30 / 10 / 10 to King, the three-pool Top 5, the this-round Top 5 bettors and the next round's seed; winners net 85% (15% protocol fee). Versus traditional casino 5–8% house edge, 1% is fairly restrained.

03If individual expected value is zero, what's in it for me?If expected value is zero, why play?

"Zero-sum" means the jackpot returns to winners through the 50 / 30 / 10 / 10 split; the dev share is a fixed fee and does not participate in the player-versus-player game. Variance between players is huge. Outcomes are decided by entry timing, capital size and your read on other players. Treat it as a public-rules on-chain game, not a yield product.

04Why 24-hour rounds?Why 24-hour rounds?

24 hours is one full working day plus one full night cycle, covering activity windows across all time zones. Rounds are short enough that the King can't sleep through unchallenged, long enough that you don't lose the throne in a five-minute bathroom break. The last hour's countdown turns orange, a signal to late entrants: "is there still a play here?"

05Can all three pools contest the throne?Can USDT / USDC buyers become King?

Yes. Any pool's last qualified buy (ETH pool > 0.0001 ETH / USDT pool > 0.3 USDT / USDC pool > 0.3 USDC, with at least 1 REBEL received) updates the current King; a legal bet (minimum 1 unit) can also crown you. The USDT / USDC pools also forward 50% of the 1% fee to the current King in real time as fee income. The three pools each maintain a Top 5 cumulative buy leaderboard for the round, 15 slots total forming the this-round Top 5 reward pool (independent of the King). Cross-pool arbitrage can double-dip (large cumulative buys across pools to grab the this-round Top 5 + a last-mile king-grab); this is intentional design.

06Can I stake across rounds?Can I stake across rounds?

Yes, but you must settle first. An old position carried from round #6 into #7 without an active exit is frozen; it must be settled (with the 50% non-current-round discount) before betting in #7. This rule keeps cross-round dividend accounting simple.

07How much is deducted from claim within the same round?Claim within the same round?

Same-round exit takes a 15% fixed protocol cut, net 85%. Cross-round settle halves old-position dividends first, then applies the 15% split to the claimable half, so you net 42.5%; the other half rolls into the current jackpot. All rates are hardcoded; no account can adjust them.

08Is this a Ponzi?Is this a Ponzi?

A Ponzi pays older participants' "promised returns" from newer entrants' money, structurally guaranteed to collapse. There's no promised return here. The jackpot is already in the contract; round-end, it splits 50 / 30 / 10 / 10 to the winner group, with no dependency on future inflow. Round-end payouts come entirely from this round's buy taxation plus this round's 20% betting portion: a closed loop. It's a public-rules game, but not a Ponzi.

09Why mainnet rather than an L2?Why mainnet, not L2?

Mainnet has the strongest immutability, the most expensive state, and the highest entry barrier; it matches the "dynasty" narrative. Co-deploying a "distributed throne" on L2s would dilute scarcity. High gas is a design choice: a filter against speculators.

10Will there be a v2?Will there be a v2?

The current contract is immutable once deployed; no v2 upgrade exists. If the community confirms a serious design flaw, anyone could in theory deploy a v2 at a new contract address. But that would be a completely separate new protocol, with no state link to v1. v1 stays v1 forever, because no account can change it.

11Is MEV front-running of the King race a bug?Is MEV front-running a bug?

(Technical note: casual players can skip.) No, it's the cost of a design trade-off. The protocol doesn't use commit-reveal to hide trade intent, because that would make buying a two-step operation and significantly raise on-chain cost. MEV bots can watch the mempool and outrace an about-to-be-crowned player, but the bot itself must put up real ETH; its return is jackpot expected value minus entry cost. Everyone pays the same 1% fee rate.

If a round's jackpot is high enough that an MEV bot has positive expected value entering, then a whale is present and ordinary players are at a real disadvantage. Judging entry timing is itself part of the game.

12What if the jackpot transfer to King fails?What if jackpot transfer to King fails?

The contract is designed for "allocate, not push". At round end, the jackpot is only flagged in a pending-winners slot for the King; the actual transfer is triggered by the King claiming themselves. If the King is a contract address that cannot receive ETH, the prize stays in the pending-winners slot forever, neither flowing back to the jackpot pool nor going to anyone else.

This is deliberate "no rescue" design: the protocol doesn't know whether the King is a contract, and doesn't decide for anyone where the money should go. Every address is on its own.

13Is the source readable?Is the source readable?

The contract source is publicly published on chain and viewable through any block explorer. Anyone can independently compile and confirm the deployed bytecode matches the public source. There's no "trust the publisher" step; rules are determined solely by the post-deploy bytecode.

14Is participation gambling?Is this gambling?

Definitions vary by jurisdiction. In some jurisdictions, this protocol may be classified as gambling or an unregulated security. The protocol itself makes no representation about compliance for participants in any location. If your jurisdiction prohibits this kind of activity, do not participate. rebel-throne.com displays a geo-IP notice at the site entrance, but the dApp contract itself does not block anyone.

15How does the protocol resist Sybil farming?How does the protocol resist Sybil farming?

(Technical note: casual players can skip.) Economically, on-chain fees themselves are a high barrier. A bot address contending the throne must pay at least three on-chain transactions (referrer binding, approval, buy) starting at around 0.005 ETH. Protocol-side, the referrer graph has three-layer cycle detection, and referrer pending is tracked separately from betting pending. Mass fake-identity attacks (Sybil) are mathematically possible but usually negative-EV.

16Does REBEL have utility outside this game?Does REBEL have utility outside this game?

From the protocol's own perspective, REBEL is the betting entry ticket, the jackpot accounting unit, and a tradable ERC-20 in the secondary market. Beyond that, no on-chain utility. The community may build around REBEL spontaneously (DEX liquidity mining, NFTs, derivatives), but that's outside v1 protocol scope; builders decide for themselves.

Rules understood.
Throne awaits.

规则讲完。王座已等好。

Every mechanism clause is laid out on this page. If you still have doubts, check Hall of Kings first to see past kings, then decide whether to enter the App.

Enter the AppHall of Kings