Description
Problem
Contract execution workflows currently assume a single signing path. Applications requiring N-of-M authorization must manually coordinate signature collection and construct the final transaction.
This makes multi-party contract execution difficult to implement consistently.
Solution
Implement a contract execution workflow that separates transaction preparation, signing-request creation, signature collection, validation, and final submission.
The workflow should support configurable signer thresholds and prevent execution until the required valid signatures have been collected.
Acceptance Criteria
Note for Contributors
Reuse existing transaction signing and verification utilities. Do not introduce an independent signing format unless there is a documented protocol requirement.
Description
Problem
Contract execution workflows currently assume a single signing path. Applications requiring N-of-M authorization must manually coordinate signature collection and construct the final transaction.
This makes multi-party contract execution difficult to implement consistently.
Solution
Implement a contract execution workflow that separates transaction preparation, signing-request creation, signature collection, validation, and final submission.
The workflow should support configurable signer thresholds and prevent execution until the required valid signatures have been collected.
Acceptance Criteria
src/soroban/index.tsandsrc/index.ts.Note for Contributors
Reuse existing transaction signing and verification utilities. Do not introduce an independent signing format unless there is a documented protocol requirement.