BluBox Never Asks to Connect a Wallet — a version that does is fake.

BluBox answers to one address: blubox.watch. The name is the promise — BluBox watches; it never touches. It is read-only by construction: no connecting, no signing, nothing secret, ever — so the only thing an imposter can fake is the address, and now you know the real one. If the address reads anything else, you are not looking at BluBox — no other domain, no app store, no "v2" will ever be the real thing. We registered the lookalike spelling, bluebox.watch, only so nobody else could wear it; it shows a one-line correction and never the app. So when someone asks "How's your blu box?" — the answer starts with the address: blu, no e, dot watch.

BluBox works with any HTML browser. BluBox references several RPCs — using a Tor or Onion Browser reduces the likelihood of an RPC — or someone watching RPCs — linking multiple addresses.

BluBox updates the Global T-Share Rank twice daily — at 00:10 and 01:10 UTC, just after the 00:00 UTC HEX-day flip; the second pass catches any late data.

The Day number in the header is HEX's on-chain calendar. It shows gold until the HEX contract itself confirms today's number, and Blu once the chain has vouched — if a device clock drifts, the contract's count wins. Tapping, Forces a Browser Reload and turns Gold to Blu, if data is valid. BluBox sends no alerts: a Validator SLASHED Notice can be at most as old as your last look (The chain itself marks a slashing within minutes). BluBox Reloads fresh, each time opened from the Home Screen.

Three colors, one meaning everywhere:
• Red — SLASHED; Red outranks everything.
• Gold — Gateway refused, dated last-look + clock.
• Blu — Chain vouched just now.

Export your String to recover your BluBox state easily — addresses, validators, settings. Version updates never require reloading the String: new code arrives with any Refresh, your String Data stays, until you Delete it.

v0 · sample data · All Rights Reserved