lightninglabs / taproot-assets / 11838616455

Pull #1181

github

tapfreighter: de-duplicate passive asset creation

Because we now check all active and passive packets for uniqueness in
their commitment keys, this issue has surfaced. If we're spending
multiple different assets from the same on-chain input commitment, we
used to create duplicate passive assets.
That wasn't a problem until now because within the trees everything
would just be overwritten and collapsed back to a single asset. But
because have the uniqueness check on the virtual packet slice level,
this duplication became apparent.

57 of 119 new or added lines in 6 files covered. (47.9%)

25222 of 61438 relevant lines covered (41.05%)

56797.08 hits per line