orquestra-tx-builder

An unsigned Solana transaction requires translating resolved instruction inputs, including exact accounts and arguments, into a base64-encoded wire format. This ensures the transaction is correctly structured for signing or manual RPC submission.

Before constructing a Solana instruction encoding, you need pre-resolved accounts, signer and writable flags, exact instruction arguments with types, and a fee payer. Upstream IDL-driven research must be completed to avoid invalid transactions.

To prevent invalid Solana transactions, you must use only pre-resolved accounts and arguments without guessing. Missing values like program_id, instruction_name, or fee_payer should trigger a follow-up request instead of generating an incomplete transaction.

No, you cannot derive PDAs or discover programs while building an unsigned transaction. The workflow requires using only pre-resolved accounts and arguments, avoiding any PDA derivation or program search calls during the instruction construction phase.

Your Solana transaction builder fails because it requires exact instruction arguments with types and rejects placeholder or guessed values. You must supply fully resolved inputs from upstream research to generate a valid base64 wire transaction.