Skip to content

Fix: Accept Signed FROST Transactions as Input#193

Merged
scaraven merged 4 commits intomainfrom
fix/accept-signed-transaction-as-input
Apr 9, 2026
Merged

Fix: Accept Signed FROST Transactions as Input#193
scaraven merged 4 commits intomainfrom
fix/accept-signed-transaction-as-input

Conversation

@scaraven
Copy link
Copy Markdown
Member

@scaraven scaraven commented Apr 8, 2026

See pr #191 for the full information. I've opened a new PR as I don't have write access to the original PR. Closes #189

jk89 and others added 4 commits April 6, 2026 12:32
…TransactionSignature as input, only raw unsigned ZkApp or Legacy transaction JSON. This means the output of one FROST signing session cannot be fed as input to a subsequent signing session, preventing chained multi-group signing of the same transaction. The test uses a real signed fixture from a deploy-v0.0.6 ceremony and currently fails documenting the limitation.
…FROST signing session) as input to from_str_network, enabling chained multi-group signing where the output of one signing session is fed directly as input to the next. The parser now tries TransactionSignature first and extracts the inner payload which already contains the previous groups injected signature, then falls back to the existing ZkApp and Legacy parsing. Resolves the failing test from the previous commit.
@scaraven scaraven merged commit 2c9d685 into main Apr 9, 2026
11 checks passed
@scaraven scaraven deleted the fix/accept-signed-transaction-as-input branch April 9, 2026 17:10
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.

Allow FROST tool output to be pipelined back into input for new signing session

3 participants