As a happy accident this reorg exposed a `testnet4` specific issue that can happen with the new version of `bdk-cli` + `kyoto` compact block filtering sync'ing I was testing. 🙌
#lazynostr does anyone have any tips on why this testnet4 tx keeps showing as unconfirmed, then confirmed, then unconfirmed on nostr:nprofile1qy28wumn8ghj7cnvv9ehgu3wvcmh5tnc09aqzrrhwden5te0vfexytnfduqzqwm285amxdvgx6ny68yq9y4edemf3mp45tju53gaa7nt6whna6uynewnpf ? I assume it's some reorgs going on, but how can I verify that? Do I have to use some testnet4 bitcoin-cli commands to double check?
https://mempool.space/testnet4/tx/ea3c1b2b65dd50963d9dc39b3760e66a69ef137861723c625d113474ab5f03aa
Discussion
No replies yet.