Bands

Status#

The band contest is funded by the Spoils user pool, through SpoilsSplitter — it takes a share alongside the battlepass and seasons. See Spoils.

What a band is#

A band is a numbered on-chain roster: who is in it, what rank they hold, and who backed which coup. Three facts and nothing else. A band has no name on chain — the display name is metadata, and a band is a number here. Ids start at 1.

The rule that decides what is in the contract is stated in its own source: an assertion goes on chain, a computation does not. Volume, the four band statuses, the succession walk and the monthly winner are all computed off chain and are deliberately absent from storage.

Gas may be sponsored: BandRelay.executeSigned accepts an EIP-712 signature under the “The Hood Bands” domain (verifying contract: the relay, which BandRegistry deploys), with no relayer allowlist — an opt-in is ActionKind.OptIn, with the coup in bandId and the side in value. Opening a coup is the one action with no sponsored form — a sponsor able to pay would decide who may open one.

Founding, joining and every hostile coup action carry a ForceAttestor attestation for the caller and the band, issued only when the caller holds a force — for a band action, its leader’s force. An unaligned account cannot found; nobody joins or raids a band of another force.

How many bands exist#

How many bands may exist at all follows an owner-set rule over the platform’s cumulative revenue, derived live and never stored:

// the cap createBand enforces; the rule is BandRegistry.bandCapRule(), set with setBandCapRule
cap = baseBands
    + max(0, lifetimeFeesWei - thresholdWei) / feesPerBandWei;   // integer division

The owner may change any of the three with setBandCapRule; the call, and a fee splitter repoint, are refused when they would leave the cap below the bands that already exist (BandCapBelowExistingBands). The bands page reads the live rule.

Ranks, tithes and caps#

The slot caps are what make a per-officer rate safe: nine fixed seats mean the tithe total cannot grow with the band. The tithes themselves are applied off chain, in the root — this contract holds the ranks, not the money. Each tithe is prorated by the UTC days the rank was held that month: a rank change counts from the UTC day of its block, and the rank held at a day’s close is that day’s rank.

A leader cannot leave while they lead. Leadership moves in two steps: the leader proposes a member (proposeLeader) and the seat moves only when that member accepts (acceptLeadership); the old leader is then an ordinary member and may leave. A leader who is the band’s only member may instead dissolve it (dissolveBand): the band ends, its number is never reused, its slot under the cap is freed, and the leader takes the usual 24-hour rejoin cooldown. Whatever the band vault still holds is paid to that leader (BandVault.claimDissolved): ETH and other currencies at once, THD and Hood launch tokens over 90 days. Joining, kicking, accepting leadership and dissolving are all refused while a coup is open on the band or a hostile race runs on it, and a leaver who opened the band’s open coup voids it: nobody is removed and the fee is not refunded.

Coups#

The coup fee is coupFeeWeiPerMember × memberCount, and msg.value must equal it exactly — overpayment is refused, because ETH in this contract has no way back out. The per-member figure is settable storage rather than a constant, because it is ETH-denominated and drifts; the design figure is 0.0005 ETH per member, which is 0.025 ETH against a full 50-member band.

The whole fee is forwarded to ProtocolFeeSplitter in the same transaction, using the measured msg.value and never address(this).balance — forwarding a balance would let anyone donate ETH and buy THD emission one-for-one, which is the hole closed on 23-08-2026.

Internal and hostile

Hostile coups — the three rulings of 27-09-2026

Party, suspension and force — the rulings of 27-09-2026

An ERC-20 trade counts at the posted price in force at its own block; with no price at that block it is excluded and the page shows how many trades were not counted — never face value.

What a band is paid#

BandRewardsDistributor performs no comparison, holds no volume, knows nothing about forces and cannot name a band. It holds the money and pays what a proof proves. The formula it implements off chain:

period  = a UTC calendar month; the first starts with Spoils (seededAt + 24h) — pre-TGE volume never counts
volume  = curve buys and sells + ETH stakes on settled markets, at event-time value, platform addresses excluded
banded  = the leg's account was in a band at that leg, and the leg's force was the band leader's force then
contestants = every force whose bands generated banded volume that period (> 0)
winner  = the contestant with the most band volume over the period
payout  = the pot × the WEAKEST CONTESTANT's share of the period's banded volume
fewer than two contestants, or a tie at the top = nothing paid, the whole pot rolls
loser   = nothing
tithes  = Leader 6% · Vice 4% · 3 Directors 2% · 4 Executives 1%   (20%, volume-gated)
          each prorated: rate × UTC days held in that rank ÷ days in the month; the rest of the slice goes to the members
the rest = split by member volume across the winning force's banded members
leaves  = one per member per month, keccak256(abi.encode(uint32 monthIndex, account, that month's THD)) — never a leader's to pass on

“The reward is the strength of the opposition”: winning against nobody pays nothing, because the pot released is sized by the weakest contestant. A force with no banded volume in the period is not a contestant, so a dormant force cannot hold the pot at zero for everyone else.

reserved()            =   Σ over published months (allocated − claimed)
reserved()           <=   thd.balanceOf(this)
unallocatedBalance()  =   balance − reserved()

The quarterly pot paid against the season leaderboard is separate: Seasons.