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 53

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
4463fce1a4a6149867ba818f90f25a08253accc43375179c2422dd2ced9533b1

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 record5fadf639…a76d2d234eb5a471…c6cd04a9
Entries signed for00
Signed rootb4079bd6…a8ed6e8eb4079bd6…a8ed6e8e
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
5fadf639…a76d2d23
Entries signed for
0
Signed root
b4079bd6…a8ed6e8e
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
4eb5a471…c6cd04a9
Entries signed for
0
Signed root
b4079bd6…a8ed6e8e
Served list
0 full, 0 hash only, 0 absent
Entries Canary filled
0
Receipt covered the list
Yes
Server's signed tip
351