Canary

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

Server withholder left out an entry it had signed for.

Data withheld Finding 79ec3cb71656

Block
35172ef80792f8633d70f19945464df62f82a267b68ee3e113199e9d11a5e41d58a
Position in the list
0
Left-out transaction
ad56b9bb4aa382fdaec664abc1dcaf57b0477905c5c17c2c7669d6212d5fe21e
Server named
withholderdb6145604bce8440aecbdd33356ad9116d495b780c97e36ef214e132e655d48c
First seen
2026-10-01 12:35 UTC
Last seen
2026-10-01 12:35 UTC

What happened

The server left out an entry it had signed for, while the block sat inside the 144-block window.

What this shows

The server signed a record for this block that includes the entry. Then it served and signed a list that marked the entry's position empty, while the block sat less than 144 blocks below its signed tip.

What this does not show

It does not show whether the entry paid you, or what the server did in other blocks. It says nothing about payment outputs, which Canary v1 does not check.

Can you prove it to others?

Yes. The evidence file carries the server's signed receipt, so anyone can check it offline with canary verify.

Evidence file

Download omission-regtest-351-ad56b9bb-db614560.json

Anyone can check this file offline. canary verify recomputes every step and trusts nothing the file says about itself.

./canary verify evidence/omission-regtest-351-ad56b9bb-db614560.json

Canary's check of this file

Checks out

The server signed a record that includes this entry, then signed a list that left it out.

  1. Passed Read the file Format canary-evidence/1, claim omission.
  2. Passed Record signature The signed record's id and signature are valid.
  3. Passed Signer The record is signed by the accused key.
  4. Passed Block The record names block 351 on regtest, the block this file names.
  5. Passed Inclusion Entry 0 of 5 proves into the signed root.
  6. Passed Receipt The receipt is signed by the same key, names the same block and covers these 269 bytes.
  7. Passed Served list The served list has 5 positions, and position 0 is marked absent.
  8. Passed Retention window The server's signed tip was 351, so the block was 0 blocks deep, inside the 144-block window.
Accused key
db614560…e655d48c
As npub
npub1mds52czte6zyptktm5en26kez9k5jkmcpjt7xmhjznsn9ej46jxqdmqpte
Block
351 on regtest
Left-out entry
Position 0, transaction ad56b9bb…2d5fe21e
Signed tip
351