READ-ONLYTESTNET / SIGNET

How HashiScan knows what it knows.

HashiScan separates raw evidence, protocol interpretation, and demonstration data. It never signs a transaction, holds a key, or treats absence from this vertical slice as proof that an operation does not exist.

Live sources

Sui checkpoint data comes from Sui Testnet GraphQL. Hashi governance and digest status come from the official @mysten/hashi SDK over Sui gRPC. Bitcoin Signet tip height comes from mempool.space’s Signet API.

Lifecycle interpretation

Deposit phases are Request → Approve → Confirm/Safety delay → Mint. Withdrawal phases are Request → Approve → Build TX → Sign → Broadcast → Confirm. Labels follow the protocol design, not generic bridge assumptions.

Honest limitations

A complete historical explorer needs a durable Sui/Bitcoin indexer and controlled Bitcoin Core node. This vertical slice performs direct live reads and therefore cannot discover every operation from an arbitrary BTC txid.

Demonstration records

Synthetic records exist only to exercise every UI phase before enough public history is indexed. They carry fixture provenance in every lifecycle step and appear with an above-the-fold DEMO DATA badge.

Authoritative references

Safety note

Hashi is pre-production. Testnet uses Bitcoin Signet coins with no value. Hashi creates hBTC; there is no $HASHI governance, utility, presale, or airdrop token.