Recorded runsRun of 1 Oct 2026Act 5
Last check 2026-10-01 12:35 UTC · blocks 201–201 · regtest · canary 0.1.0 (3a1417f)
Rendered from act5/state.json, SHA-256 5e0d80131a3330f14266b9d209590698b5508e4f949a08b66bf8526ce095f8d1
Act 5 ran canary check again on block 201 alone, with only withholder pinned.
The 1 block could not be checked.
The block had a signed record, but Canary could not recompute its root. The server left an entry out of a block past the 144-block window. Your node confirmed its chain, and nobody supplied the entry. Can't be checked is neither a pass nor an accusation.
1 block couldn't be checked. A payment in it could be missing from what your wallet shows, so treat its balance as a lower bound.
Coverage
Range tableBlocks by state
-
Checked
0
The tweak list matched the record its server signed.
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.
-
Checked, gap filled
0
The tweak list matched its signed record once Canary filled the gaps.
What does this mean? Checked, gap filled
Some positions arrived only as hashes, or were empty and Canary found the entry elsewhere. Canary filled every position first, then recomputed the root, and it matched. An entry sent only as a hash is a known limit. Canary can't tell a server that pruned it from one that hid it.
-
Can't be checked
1
Canary could not recompute the root for this block.
What does this mean? Can't be checked
Something the root needs was missing. An entry nobody could supply ends here, and so does a list the server signed for but did not serve. This is neither a pass nor an accusation. A payment in this block could be missing, and Canary would not know.
-
Not checked
0
There was no signed record to check against.
What does this mean? Not checked
No server gave Canary a signed record it could use for this block. The server may sign nothing, may not have reached the block yet, or may not have answered. The data may still be fine. Canary checked nothing about it.
-
Servers disagree
0
Two servers signed different records for this block.
What does this mean? Servers disagree
Two servers each signed a record for the same block hash, and the records differ. At least one of them is wrong. Canary can't tell which, so it names both servers and accuses neither.
-
Data withheld
0
A named server left out an entry it had signed for, or the entry for a payment you declared.
What does this mean? Data withheld
One server signed a record that includes an entry, then served a list that left it out. Or its record or list left out the entry for a payment you declared. Canary names that one server. Whether you can prove it to others depends on the evidence, and each finding says which.
Findings
No findings. No server was caught leaving out an entry it had signed for.
Servers
You pinned each server's key with --pubkey, and Canary never learns a key from the server itself. A signed tip came from a valid receipt. Policies and unsigned tips come from the server's /info, which nothing signs.
| Server | Public key | Signs records | Signs receipts | Answered | Tip | Declared policy | Last error |
|---|---|---|---|---|---|---|---|
withholder http://127.0.0.1:28482 |
db614560…e655d48c | Yes | Yes | Yes | 351, signed | Prunes nothing, no dust filter, unsigned | None |