ffranr

In this issue, we are implementing the following changes: - Versioning support. - Introduction of fixed-point types for the in-asset and out-asset BTC fields. - Addition of a `transfer_type` field...

@Roasbeef > Was this due to a partially botched migration? We already have the pragama to enforce the foreign key constraints. I'm not sure. Possibly. This is why I think...

fts5 seems like a good solution for sqlite. I'm trying to think of a similar solution for postgres. We might get away with implementing the performance improvement for sqlite only...

`commitment: add asset type field to asset commitment structure`: https://github.com/lightninglabs/taproot-assets/pull/278

~~We should complete issue https://github.com/lightninglabs/taproot-assets/issues/694 before addressing this issue.~~ #691 is ready

> So the restart logic is fine, but we still shouldn't let inability to deliver a proof stop us from calling ConfirmParcelDelivery. In an observed case, a user had the...

> Reopening as the current itest tests proof courier restart but not tapd restart. @jharveyb I don't think that's true, see: https://github.com/lightninglabs/taproot-assets/blob/420f2467a6770a9c6042159dcd4c3ce194db25c2/itest/send_test.go#L378-L384

Thanks for looking into this @linden! And for the solution you've investigated. Can i cherry-pick your commit https://github.com/linden/taproot-assets/commit/a354337ac2c3d02a1f11d6faad4628b623e196d7 into a PR or do you mean to open a PR yourself?

The remaining itest flakes mentioned in this issue should all be limited to the terminal package. I will look into them when I can.

litd itest flake CI fail: https://github.com/lightninglabs/lightning-terminal/actions/runs/18164359497/job/51702542960?pr=1146