Activation block
—blocks until signals count
Observatory / Measuring Instrument
BITMAP SIGNAL MAP
See who leads each Hood and Sector, computed from on-chain signals. Hoods are local 2016-block windows. Sectors are 210,000-block epochs. Every displayed result can be counted and verified.
Activation block
—blocks until signals count
How It Works
Step 1
District signalsA District reinscribes a JSON signal on its sat, naming another District or casting veto.
Step 2
Hood countsEvery 2016 blocks, signals inside a Hood are tallied. Only self-nominated Districts can receive votes.
Step 3
Seat assignedThe District with the most signals becomes Hood Seat. Veto wins if it leads. Ties remain ties.
Step 4
Sector electsEvery 210,000 blocks, Hood Seats roll up. Points determine the Sector Elect and Capital.
Live Hoods
Sector Rollup
Verification Surface
Open the counter, inspect contributing signals, then drill into raw proof items with txid, reinscription reference, JSON signal, and deterministic reasoning notes.
Layer 1
Local windows count self-signals, nominations, and vetoes inside a fixed boundary.
Layer 2
Hood seats roll up into sector points, elect a capital, and expose unresolved ties.
Layer 3
Every seat is deterministic: counted inputs, boundary logic, exact tie-breaks, raw proof.
Hood Viewer
A Hood spans 2016 blocks — one difficulty adjustment window. Districts inside a Hood can signal support for each other. Only self-signalled Districts become candidates. The District with the most signals at the end of each window becomes the Hood Seat. If veto leads, no Seat is assigned. Insufficient data means not enough Districts have signalled yet to prove a winner.
Signals
Deterministic Counter
Exact Inputs
Sector Viewer
Candidate Points
Ruleset
About / Method