Recorded run, not live. The dashboard as it stood after our regtest run on 1 Oct 2026.

Files and hashes

Recorded runsRun of 1 Oct 2026

regtest: a private test chain, not a public network

Last check 2026-10-01 12:35 UTC · blocks 0–351 · regtest · canary 0.1.0 (3a1417f)

Rendered from state.json, SHA-256 a6c42aabe72b1f33fa3e869df27fdccd6023fb109a5e8bee3b62f5e09914203a

Block 172

Checked

Two or more servers signed the same root, and a served list matched it.

What does this mean? Checked

Canary recomputed the root over every position in the tweak list, and it matched the server's signed record. No position needed filling. This checks the tweak list only. It never checks the payment outputs a wallet matches against, so a server could still hide a payment there, and Canary v1 would not see it.

Block hash
6980350c6373c1d12b37f9d4cc451b7509bd96e344214558087550dc28de3272

Each server

Fieldhonestwithholder
ResultCheckedChecked
WhyTwo or more servers signed the same root, and a served list matched it.Two or more servers signed the same root, and a served list matched it.
Signed record06512676…5e3ce6747c9a1dcf…058dbfc8
Entries signed for00
Signed root5ec35533…8671dec75ec35533…8671dec7
Served list0 full, 0 hash only, 0 absent0 full, 0 hash only, 0 absent
Entries Canary filled00
Receipt covered the listYesYes
Server's signed tip351351

honest

Result
Checked
Why
Two or more servers signed the same root, and a served list matched it.
Signed record
06512676…5e3ce674
Entries signed for
0
Signed root
5ec35533…8671dec7
Served list
0 full, 0 hash only, 0 absent
Entries Canary filled
0
Receipt covered the list
Yes
Server's signed tip
351

withholder

Result
Checked
Why
Two or more servers signed the same root, and a served list matched it.
Signed record
7c9a1dcf…058dbfc8
Entries signed for
0
Signed root
5ec35533…8671dec7
Served list
0 full, 0 hash only, 0 absent
Entries Canary filled
0
Receipt covered the list
Yes
Server's signed tip
351