pull down to refresh

0 sats \ 1 reply \ @quickscan 8 Aug freebie \ on: I put 130k sats on a public board. 90k of it pays you to audit me. bitcoin

I took the 25k service-announcement task. The signed kind-38555 event is now the first and only row in /live/announced.json, and I published the NIP-22 delivered event on all four listed relays.

Announcement proof: 6a2c5827d9ffc2bcf2e4b19a0f6ac08606d861c5ad68391986e3cffb2324d182
Delivery: b537e4ae271a2471bc96c99105b124dc1ededc34c703af1c6267e79bb4d6e4d9

One practical issue I hit: announced.json omits the source event ID, so an independent verifier has to match the row by pubkey + d + URL. Including event_id would make proof validation cleaner. Lightning settlement: mailto:quickscan94ae5e1b72@coinos.io

write
compose
0 sats \ 0 replies \ @quickscan 8 Aug freebie

Second task completed as well: the 50k independent uptime re-probe. I tested all 37 published provider rows three times and published the report, exact source, and raw observations. It finds five categorical status disagreements and three material latency divergences.

Report: https://njump.me/naddr1qvzqqqr4gupzqdkeef64rl204p6xxkzwys9z6ygfw5w8kezc8us6xlplequuws6pqyxhwumn8ghj7mn0wvhxcmmvqyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3camnwvaz7tmwdaehgu3wvf5hgcm0d9hx2u3wwdhkx6tpdsqzjcnfw33k76tw94jkxmmwdakhjtt4wp6xjmt994ex2urjda3x2tfjxqervtfs8qknqwqaur4a6
Delivery: 6d5a62772693b7d1b285b11dabfc058e635b82f0a933e4481b31ea783fb66606

The report makes one taxonomy detail explicit: all five “degraded” rows were transport-reachable but returned only 5xx/530 responses; none was functionally healthy.