Elias Rohrer

> @tnull so you want an older version of BDK to understand changesets that a newer version of BDK outputs. Can you elaborate why this would be useful? Thank you...

> Note in `bdk_file_store` we don't serialize changesets with a length so the decoder is expected to understand everything in a changeset. We could improve this by first bincode serializing...

> Do we really need forward and backwards compatibility baked into the data structures for persisted data? My understanding is that the data BDK persists should always able to be...

> This should be doable by just creating a custom `KeysInterface` where you make `get_shutdown_scriptpubkey` and `get_destination_script` get addresses from LDK. I can now confirm that by implementing a custom...

> @tnull do we only need to expose the existing rust [`add_foreign_utxo`](https://docs.rs/bdk/1.0.0-alpha.1/bdk/wallet/tx_builder/struct.TxBuilder.html#method.add_foreign_utxo) function in the language bindings? That should allow you to create a transaction in BDK that spends a...

+1 to both of these. Maybe this should be called 'make ricochet behave like a Mac app'.

It's really unfortunate to hear that MSRV support is not planned. If projects need to maintain longer-term support, not having MSRV guarantees means they can't rely on a `rusqlite` dependency....

> For a library, if you care about an MSRV it's only important that there exist a set of packages that satisfy the MSRV under your requirements, rather than have...

If this is refactored anyways, wouldn't it make sense to introduce a dedicated type for `UnixSeconds`, or at least re-use the `Duration` type?

For this purpose, wouldn't it make sense to use the last-seen tip height rather than a UNIX timestamp?