orquestra-tx-builder

What problem does it solve?

Constructing a correct Solana unsigned transaction is hard because every account, signer/writable flag, and argument must exactly match the target instruction definition.

Core Features & Use Cases

• Orchestrated transaction construction: Produces a base64-encoded unsigned Solana wire transaction using Orquestra MCP’s build_instruction output.
• Strict upstream-research workflow: Uses only pre-resolved accounts and arguments and avoids PDA derivation, program search, or guessing.
• Guardrails for correctness: Enforces a checklist so missing program_id, instruction_name, accounts, arguments, or fee_payer triggers a follow-up request instead of generating an invalid transaction.

Quick Start

Ask the AI: "Build an unsigned transaction for program <program_id>, instruction <instruction_name>, using these resolved accounts and signer/writable flags, these exact instruction arguments (with types), and fee payer <fee_payer>, and return the base64 wire transaction."