-
Notifications
You must be signed in to change notification settings - Fork 56
feat(platform-wallet): multi-output shielded transfers + output-aware fee predictor (two-note invites) #4301
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
Closed
bfoss765
wants to merge
2
commits into
dashpay:v4.2-dev
from
bfoss765:feat/shielded-two-note-invites
Closed
Changes from all commits
Commits
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
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.
🔴 Blocking: Reject bundles over the effective transition-size limit before proving
This gate accepts any bundle with at most
max_shielded_transition_actions, currently 16, but the versionedmax_state_transition_sizeof 20,480 bytes is already the tighter acceptance limit. A seven-actionShieldedTransferserializes to 21,594 bytes at this head, so six recipients plus the mandatory change output—or a fragmented wallet selecting seven spends—passes this check and reachesprove_and_sign_bundle, only to be rejected later by DAPI's raw-byte prefilter and Drive-ABCI's consensus decoding check. The new Kotlin/FFI API admits up to 16 recipients, making this guaranteed-failure path externally reachable and unnecessarily consuming the expensive Halo 2 proving worker. Add a version-aware pre-proving limit derived from both the transition byte ceiling and the structural action ceiling, cover output- and spend-dominated bundles, and align the binding recipient ceiling with the effective limit; under the current 20 KiB limit, at most five recipients fit alongside mandatory change.source: ['codex', 'coderabbit']