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.

Sign up for GitHub

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

Jump to bottom

Concurrent MSTs of the same proposals? #5224

Open

s8sato opened this issue Nov 7, 2024 · 0 comments

Labels

question

Contributor

s8sato commented Nov 7, 2024

Yes, the current design is that every transaction entry is unique through its lifecycle.

If it were a requirement that virtually identical instruction sets should be differentiated and concurrently processed, we could e.g. include an account nonce in hashing, but I don't see the motivation for splitting approvals atm

Originally posted by @s8sato in #5217 (comment)

s8sato added the question label

s8sato mentioned this issue

refactor(multisig)!: move from triggers to custom instructions #5217

Open

3 tasks

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