Repository navigation
feat(wallet): DIP-15, accountReference, asset-lock and eligibility seams for DashPay #7763
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
PastaPastaPasta
wants to merge
3
commits into
dashpay:develop
Choose a base branch
from
PastaPastaPasta:feat/platform-wallet-fingerprint-account-ref-mac
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+511
−38
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
fd9b5c8
feat(wallet): DIP-15 compact xpub and accountReference seams
PastaPastaPasta 74cdbb4
feat(wallet): asset-lock creation and broadcast-error seams for DashPay
PastaPastaPasta ba24142
feat(wallet): Platform key eligibility, pruned-rescan start and a mov…
PastaPastaPasta File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR description:
why exactly asset lock version 1 is needed here in PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because version 1 is the only asset lock that works on both sides of the v24 boundary today:
CheckAssetLockTxrejects any payload version aboveINITIAL_VERSION(bad-assetlocktx-version-2,src/evo/assetlocktx.cpp:59).IsStandardSpecialTxtreats a version 2 payload as non-standard (assetlocktx-version-2,src/evo/specialtxman.cpp:1964). That is your fix: make huge asset lock tx non-standard #7359, which keeps v2 locks out of relay until Platform is ready for them.The wallet's default is
CAssetLockPayload::CURRENT_VERSION(2,src/wallet/spend.cpp:837), so a DashPay registration or top-up built the normal way would be refused by the mempool. The seam therefore sets version 1 on its own copy of the coin control, and leaves the existingsendtoaddressPlatform path on v2 with its-acceptnonstdtxn=1hint. Once v2 locks are made standard, the seam can drop the override.🤖 Posted autonomously by Claude on behalf of pasta.