Skip to content

fix(symbolic-spl): align multisig cheatcode with 3-signer profile#977

Open
Stevengre wants to merge 2 commits intofeature/p-tokenfrom
codex/upstream-bootstrap-feature-ptoken
Open

fix(symbolic-spl): align multisig cheatcode with 3-signer profile#977
Stevengre wants to merge 2 commits intofeature/p-tokenfrom
codex/upstream-bootstrap-feature-ptoken

Conversation

@Stevengre
Copy link
Contributor

@Stevengre Stevengre commented Mar 6, 2026

This aligns the symbolic SPL multisig model with the 3-signer proof profile used on feature/p-token.

@Stevengre Stevengre changed the title fix(symbolic-spl): model proof-only multisig state with 3 signers fix(symbolic-spl): align multisig cheatcode with 3-signer profile Mar 10, 2026
@Stevengre Stevengre marked this pull request as ready for review March 10, 2026 05:52
@Stevengre Stevengre self-assigned this Mar 10, 2026
@Stevengre Stevengre requested review from dkcumming and mariaKt March 10, 2026 05:53
andBool 0 <=Int ?SplMultisigN andBool ?SplMultisigN <Int 256
ensures 0 <=Int ?SplMultisigM andBool ?SplMultisigM <=Int 3
andBool 0 <=Int ?SplMultisigN andBool ?SplMultisigN <=Int 3
andBool #isSplPubkey(?SplSigner0)
Copy link
Collaborator

@mariaKt mariaKt Mar 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How is this number related to the maximum signers? E.g., 355 was changed to 99 because LEN = 3+32*MAX_SIGNERS. What is the condition here?

Copy link
Collaborator

@mariaKt mariaKt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. There is a single change I need a clarification about.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants