13415729112

Committed 17 Feb 2025 03:39PM UTC coverage: 54.486% (+0.03%) from 54.458%

Build # 13415729112

Build Type

Pull #1402

github

Committed by

guggero

Commit Message

tapfreighter: create anchor output keys correctly

Once we have multiple asset IDs (and with that multiple distinct virtual
packets), we need to make sure that we create our anchor outputs
correctly.
We need to make sure that the anchor outputs for the same index are
actually the same (e.g. same internal key). If we just blindly loop over
them and assign new keys, then two virtual outputs that reference the
same anchor output index would have different keys and we'd fail a check
then attempting to commit those packets to a BTC anchor transaction.

Pull Request Pull Request #1402: [wallet]: refactor in preparation for group key channel funding

Coverage Stats

393 of 610 new or added lines in 11 files covered. (64.43%)

70 existing lines in 15 files now uncovered.

48737 of 89448 relevant lines covered (54.49%)

0.8 hits per line

Source File
Press 'n' to go to next uncovered line, 'b' for previous

52.98

/tapdb/sqlc/mssmt.sql.go

Build SHA Not Found

The commit SHA "840267de86a3da0b4ab02ddd08f703f6d3ea2556" was not found in your repository, so the file cannot be loaded. This may be because you posted from a local development environment, or your CI created an ephemeral commit.

lightninglabs / taproot-assets / 13415729112

Source File Press 'n' to go to next uncovered line, 'b' for previous

Build SHA Not Found

Source File
Press 'n' to go to next uncovered line, 'b' for previous