-
Notifications
You must be signed in to change notification settings - Fork 127
Comparing changes
Open a pull request
base repository: lightninglabs/taproot-assets
base: c28aacfbc3f0849b6e20460e4fd3825425725a0f
head repository: lightninglabs/taproot-assets
compare: f2b9b0f52a7d1f134b69ad136dc9d70f633bfe95
- 10 commits
- 16 files changed
- 1 contributor
Commits on Feb 26, 2025
-
tapfreighter+tapsend: don't use FundingDescriptor
We don't need the full funding descriptor, so this refactor makes it easier to use ValidateInputs and AssetFromTapCommitment in other situations.
Configuration menu - View commit details
-
Copy full SHA for 4aaae8c - Browse repository at this point
Copy the full SHA 4aaae8cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 3d39efb - Browse repository at this point
Copy the full SHA 3d39efbView commit details -
multi: refactor funding packet creation into functions
As a preparation for a larger refactor on how we create virtual packets and distribute the coins selected for funding a transfer, we turn previous methods into functions. This will allow us to move those functions and easier unit test them.
Configuration menu - View commit details
-
Copy full SHA for d5b9f95 - Browse repository at this point
Copy the full SHA d5b9f95View commit details -
tapfreighter: move funding related code into its own file
This is a pure code move. We're going to add unit tests for the moved functions in the next commit.
Configuration menu - View commit details
-
Copy full SHA for 7c34655 - Browse repository at this point
Copy the full SHA 7c34655View commit details -
key_ring+tapgarden: remove DeriveKey from iface, improve mock
The DeriveKey method is currently not used anywhere. To simplify the mock, we simply remove it.
Configuration menu - View commit details
-
Copy full SHA for 96441f7 - Browse repository at this point
Copy the full SHA 96441f7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3ff17e0 - Browse repository at this point
Copy the full SHA 3ff17e0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8eafc1f - Browse repository at this point
Copy the full SHA 8eafc1fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 31fec55 - Browse repository at this point
Copy the full SHA 31fec55View commit details -
Configuration menu - View commit details
-
Copy full SHA for f56b2d5 - Browse repository at this point
Copy the full SHA f56b2d5View commit details -
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.
Configuration menu - View commit details
-
Copy full SHA for f2b9b0f - Browse repository at this point
Copy the full SHA f2b9b0fView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff c28aacfbc3f0849b6e20460e4fd3825425725a0f...f2b9b0f52a7d1f134b69ad136dc9d70f633bfe95