Lloyd Fournier
Lloyd Fournier
note this is ready to fix in `bdk_chain` if @danielabrozzoni or anyone else has a vision for how it should work. Any problems with the current impl I no doubt...
This `verify` method belongs on `TxGraph` in `bdk_chain` feature gated on the `bitcoinconsensus` feature. `Wallet` can just call it internally.
@notmandatory this is very relevant to #1374. The problem we should solve here is the RBF feature being mis-designed. You shouldn't just RBF a transaction by looking at the inputs...
Not sure if our architecture actually supports this kind of usage. The problem is how do you figure out when an output has been spent? The only way is that...
@notmandatory yeah cool I didn't know about this setting but that also works. I feel like the usage is a little niche: 1. You don't want to run an archival...
mempool.space is just esplora. We actually use mempool.space as the default backend in `gun` because it's much more reliable than blockstream.info.
Yeah I think mempool.space does indeed have more data and indexes but to be clear I mean that the `Blockchain` trait can just use the esplora API it supports and...
> I just want to add that the cool thing about our API is that it can also run on a Raspberry Pi - this probably better enables integration with...
I agree we should distinguish between `u64` which is the timestamp we last saw a transaction vs actual locktime. I think we could use the rust-bitcoin definition for actual chain...
> Currently, the nature of `TxGraph` is fully monotone. Nothing can be added or removed. I think things can be added!