⚠ Unverified mock data. No protocol contract exists on any chain yet (decision 0001), so every amount, price, and timer below is a simulation fixture — not a protocol fact.
Two ways to earn
Stay in the payout line. Help your side win.
A confirmed buy moves you to #1 and adds time. Newer buys can take the seat. Your personal payout-line position stays separate from your faction position; when the round settles, the contract decides both outcomes.
Know the risk: a later buyer can replace you, and you can lose everything you spend.
- 1Buy a key
- 2Take #1 + add time
- 3Keep a paying seat + help your side win
✕ No round has been read from the network yet, so there is nothing to assault. This control enables itself the moment a subscription reads one — nothing else has to be switched on. The only rounds this build can read at all are unverified mock data (decision 0001 §6, cit-d7c.7).
No panel open.
What will my wallet ask me to approve?
Nothing yet — no wallet can connect in this build (cit-5lg.1), and this button only opens a panel. When it does: a wallet shows you a request and you approve or reject it, and nothing leaves your account until you approve. Two different kinds of request look similar. A signature proves you control the account and costs nothing; a transaction spends ETH and its gas is charged even if the assault then fails. The request itself will always say which one it is, and the amount it shows is the amount that can leave — if that number is not what you expected, reject it.
Tithe vault (Current round pot)
Not read yet
No fiat estimate: no price source is configured, and none is ever shown against a testnet balance (decision 0007). A made-up rate would read as a real one.
Countdown (Time until round can end)
—
Countdown unavailable.
?No round state
No deadline is known, so no countdown is shown. The client never invents one.
The seat's take
Nobody is in line yet
No purchase has been read in this round, so there is no tail and no seat to value. This is an absence, not a zero.
Live competition
Faction leaderboard
No standings reported
No faction standing has been reported: no standing-changed event has been folded in on this page. That is the absence of a report, not the configured factions level with one another, and this build invents no standing for a faction the events have not mentioned.
Previous moves
Recent round history
No round history yet
Live competition
Faction stakes
No canonical round has been read, so no faction is shown as empty, controlling, favored, or funded.
Your position
No connected player
Connect an account and read its protocol state before this page can show spend, proceeds, break-even, personal tail, or faction exposure. None is invented from the selected faction.
Faction story
Round campaign
No canonical faction story has been read yet.
Payout ladder
No tail reported
The connected protocol has not reported who the vault would pay, so none is shown. This build does not invent a settlement.
Where the spend goes
Nothing spent yet
No confirmed purchase has been folded into this round, so there is nothing to divide. This is an absence, not a set of zeroes.
Seated outlaw (Current last eligible buyer)
No ruler seated
Your unsettled assaults (Buy keys/shares)
None.
A pending assault never moves the ruler above: the ruler is only ever what a confirmed chain event said.
Quote (Current quoted cost)
No quote
A quote needs an amount and a connected wallet. The assault panel asks for an amount (cit-ci2.12); no wallet can connect in this build (cit-5lg.1), so nothing has been quoted here.
What is gas?
Gas is the fee the network charges to process your transaction. It is paid in ETH whether or not the transaction succeeds, and it is separate from the amount you spend on the assault. Paying more gas does not buy you a better position in the queue on this network: transactions are ordered first-come-first-served by the sequencer.
Can the cost change after I am quoted?
Yes. A quote is a reading taken against one block, and the price can move between that block and the one your transaction lands in — someone else's assault in between is enough. The block and the age of the reading are shown above so you can see how stale it is. A limit on how far the price may move before the transaction is abandoned is not something this HUD offers: it belongs to the assault panel (cit-ci2.12), which offers one only when the connected protocol takes such a parameter — and whether a real contract does is unknown (cit-d7c.7). So do not read this HUD as protecting you from a price move.
Latest confirmed event
No confirmed event yet
What does “confirmed” mean here?
A confirmed event is in a block. On this network the final, unchangeable point trails the newest block by roughly eleven to seventeen minutes, so “confirmed” and “final” are different things and this HUD says which one it means. The block depth that would count as final has not been decided yet (cit-d7c.3), so nothing here claims to be settled.
Direct read vs events
No read reconciled yet
Nothing has been compared: no periodic getRoundState() read has been reconciled against the folded events on this page yet. That is not agreement — it is the absence of a comparison, and it is also what a build with reconciliation switched off shows permanently.
Network
?Network status unknown
No transport has reported in yet. Nothing is being read from a live network in this build.
Robinhood Chain Testnet (test network — no real value).
Display and sound
Sound is never the only way anything is said: every cue you could hear also changes text on this page, so captions are not a mode you have to turn on. No sounds exist yet (cit-ci2.14, cit-ci2.15) — the controls above are the switches those will have to obey.
Motion is allowed. Nothing ever flashes more than 3 times a second.
Nothing has been measured on this device yet, so this is the starting profile rather than a recommendation. A profile is recommended once the scene has drawn enough frames to time it, which a scene held still by reduced motion never does. Choosing one here overrides that. High draws full particles, dynamic lighting and shadows; Balanced fewer of each; Low is static lighting and minimal particles; 2D mounts no 3D scene at all. Every control on this HUD works in 2D.
The simulation
⚠ A scripted round, played on this device. These controls change when it happens and what the stand-in wallets do — never a price, a timer, a balance, or anything a protocol would say. Nothing is sent or signed.
Playback
Playing one beat every 220 ms. A beat is one scripted step, and a quiet one mines a block without emitting anything. Slower than real time the countdown drifts: it is extrapolated from the last block on your device clock, so it runs ahead of the simulated chain and is pulled back each time a block arrives.
Assault as
Outlaw A is 0x00000000000000000000000000000000000000a1. Outlaw B is 0x00000000000000000000000000000000000000b2. Outlaw C is 0x00000000000000000000000000000000000000c3. Stand-in addresses derived from an index, not anybody's wallet. The referral names whoever is seated at the time, which is the only referrer a spectator could name; a wallet is never its own. One assault mines a confirmed purchase and whatever follows it — a seat change, a timer extension, a dividend to the outgoing outlaw, a faction standing.
Round events
The chain's own beats rather than a player's: time passing, a purchase that reverted, a block reorganised out from under the events in it, the deadline passing, the contract settling, the winner claiming. Only a contract ends a round — pressing Settle makes the simulation say it settled, which is why the phase it produces is labelled as coming from a mock.
Activity
⚠ Unverified mock data. No protocol contract exists on any chain yet (decision 0001), so every amount, price, and timer below is a simulation fixture — not a protocol fact.
The activity feed is empty.
Addresses are shortened. No wallet aliases are shown: no name service is configured and none is looked up (decision 0006). Faction names, glyphs and colours are configuration (PLAN.md §8.5): an entry shows the configured faction, or the id exactly as the event carried it when this build has no configuration for that id, or says the event reported no faction at all. Hashes and addresses below are not linked to the block explorer: this is mock data (decision 0001), so nothing here exists on the network and a link would suggest otherwise.
Not on chain yet (0)
Nothing in this group is a chain fact. Each entry is this client's own record of a transaction it sent or saw, so it can still fail, be replaced, or land after the seated outlaw has already changed. None of them is in a block, which is also why none of them can be placed in chain order.
Nothing has been sent or seen from this device.
Confirmed on chain (0)
Mined facts, newest first, ordered by block number, transaction index and log index. "Confirmed" is not "final": on this network the unchangeable point trails the newest block, and the depth that would count as settled has not been decided (cit-d7c.3), so no entry here is labelled finalized or settled. This list is also only what this client has read since it started watching: nothing fetches the history from before that (cit-ci2.72), so a short list here means little was read, not that little happened.
No chain event has been read yet.
Withdrawn or superseded (0)
Facts that held and no longer do: a block replaced by a chain reorganisation, or a transaction replaced from the same account. They are kept rather than deleted, because a withdrawal is itself a fact about the chain.
Nothing has been withdrawn.