Matthew Zipkin

Ok I understand this now - it's not a mistake. This guard and the checks in [`mempool._handleReorg()`](https://github.com/bcoin-org/bcoin/blob/3623d04a9fc0ea1ad223597b2be941c07d16e0e9/lib/mempool/mempool.js#L294) are in place to make TXs from disconnected blocks reentering the mempool much...

Pushed update to verify blocks with `VERIFY_BODY` and ensure that mempool contents are always valid in the next block after each relevant test.

Wow this is super cool! Will it require maintenance, ie. updates to homebrew with each new bob release?

The only problem with this is the possibility to mess up future wallet recoveries by making too big a gap in the bip44 chain. Advanced users can already get new...

yeah i have no problem with this, really. I use Wasabi wallet for BTC and it will give me as many new addresses as I want. Maybe there could simply...

holy crap you're right, uh oh i may need to patch the hip2-server code

Ok Im going down the rabbit hole of this bug - still Bob could be smarter i suppose. Maybe we need to total up ins and outs we control for...

This data may be very flimsy, remember there is no "the mempool" -- when you start up your node your mempool is empty, so you could be missing bids that...

another option is maybe to refactor the shakedex actions so we unlock the wallet first before sending IPC commands to shakedex. I know the shakedex lib has `context` which handles...

Just looking at package.json, Electron has around 70 dependencies, Tauri has none. Thats dope.