svm: Instructions

@eco-incorp/sauce/svm is the Solana side: the client (createSauceSvmClient), clusters, PDAs, account resolution against the compiler’s account manifest, Kitchen and engine instructions, transactions and sending, token accounts, and compute planning for @sauce/router’s Solana venues. @eco-incorp/sauce/svm/engine exports the engine’s wire format and instruction builders, @eco-incorp/sauce/svm/verify verifies settle programs and engine CPI data, and @eco-incorp/sauce/svm/engine-artifacts (Node only) returns file paths to the packaged engine and Kitchen binaries.

import { createSauceSvmClient, SOLANA_CLUSTERS } from "@eco-incorp/sauce/svm";

Generated from the type declarations of @eco-incorp/sauce.

`buildExecuteInstruction`

Function · @eco-incorp/sauce/svm, @eco-incorp/sauce/svm/engine Builds the engine execute instruction. The supplied account list defines the program’s account indices. The first signer supplies the caller context (ctx.msgSender()); a list with no signer fails only if the program reads it. Include buildHeapFramePrepend() exactly once in the transaction.

export declare function buildExecuteInstruction({ programId, bytecode, accounts, }: ExecuteInstructionInput): Instruction;

`buildExecuteFromAccountInstruction`

Function · @eco-incorp/sauce/svm, @eco-incorp/sauce/svm/engine executeFromAccount: account 0 is the code, the caller’s tail follows at its natural indices, and the program is that account’s data verbatim. No payload beyond the discriminator. The pre-release engine took [flags][pin][offset,len][args] so a caller could pin the staged bytes at execute time; the released engine has no such grammar and the pin moved to the kitchen - buildCookFromAccountInstruction’s pin refuses unless the staged bytes hash to it. Needs RequestHeapFrame, like execute - see buildHeapFramePrepend.

export declare function buildExecuteFromAccountInstruction({ programId, code, accounts, }: ExecuteFromAccountInstructionInput): Instruction;

`assertNoExecutePin`

Function · @eco-incorp/sauce/svm, @eco-incorp/sauce/svm/engine Rejects a would-be execute-time content pin, naming where the enforceable one lives. Lives here because the reason is this module’s: executeFromAccount above emits the discriminator and nothing else, so a pin handed to a caller of it has no destination. The surfaces that used to accept one - StagedBufferRef.expectedSha256, SimulateStagedOpts.expectedSha256 - forwarded it and dropped it while documenting it as engine-verified, which is the failure this converts into a loud one.

export declare function assertNoExecutePin(expectedSha256: Uint8Array | undefined): void;

`buildCookAndPayInstruction`

Function · @eco-incorp/sauce/svm, @eco-incorp/sauce/svm/engine cookAndPay - the engine called directly, bytecode inline, paying the Kitchen’s execution fee itself: [discriminator | max_execution_fee u64 LE | bytecode]. No Kitchen, so no Pot: nothing signs for one, and the program acts with the signatures the transaction gave its tail - the wallet that signs is the authority a token transfer names. In exchange the program’s own CPIs start one level higher on the invoke stack than under a Kitchen cook, which CPIs the engine. Needs the same RequestHeapFrame as every cook - see buildHeapFramePrepend.

export declare function buildCookAndPayInstruction({ engineProgram, bytecode, tail, ...payment }: CookAndPayInput): Instruction;

`buildCookAndPayFromAccountInstruction`

Function · @eco-incorp/sauce/svm, @eco-incorp/sauce/svm/engine cookAndPayFromAccount - the staged direct cook: [discriminator | max_execution_fee u64 LE], the program being the code account’s data. Unpinned. The engine checks nothing about the code account - not its owner, not a finalized flag, not a digest - and runs it with the tail’s signatures. Whoever can change those bytes before the transaction lands chooses what the signer’s authority is used for. Prefer buildCookAndPayFromAccountPinnedInstruction unless the account is one only the signer controls.

export declare function buildCookAndPayFromAccountInstruction({ engineProgram, code, tail, ...payment }: CookAndPayFromAccountInput): Instruction;

`buildCookAndPayFromAccountPinnedInstruction`

Function · @eco-incorp/sauce/svm, @eco-incorp/sauce/svm/engine Builds cookAndPayFromAccountPinned, the pinned staged direct cook: [discriminator | max_execution_fee u64 LE | expected_sha256]. It verifies the code account’s SHA-256 digest before charging the fee and executes exactly those bytes. A mismatch fails with CodeHashMismatch.

export declare function buildCookAndPayFromAccountPinnedInstruction({ expectedSha256, engineProgram, code, tail, ...payment }: CookAndPayFromAccountPinnedInput): Instruction;