@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.
@eco-incorp/sauce.
prepareExecuteTransaction
Function · @eco-incorp/sauce/svm
buildExecuteTransaction’s transaction, compiled now and signed only when asked.
buildExecuteTransaction
Function · @eco-incorp/sauce/svm
Builds and fully signs a v0 transaction, optionally compressed through address lookup tables.
measureExecuteTransaction
Function · @eco-incorp/sauce/svm
The transaction buildExecuteTransaction builds from the same fee payer, instructions and
tables, compiled with no signature and a placeholder blockhash: what it measures
(getTransactionSize) and the accounts it lists (lookupTableAddresses), known without a
blockhash and without asking any signer for anything.
TRANSACTION_SIZE_LIMIT
Variable · @eco-incorp/sauce/svm
The largest legacy or v0 transaction on the wire, in bytes - every transaction the SDK builds is
one. Kit keeps its own copy of the number private since its v1 transactions, which allow more.
SignedExecuteTransaction
Type · @eco-incorp/sauce/svm
BuildExecuteTransactionInput
Interface · @eco-incorp/sauce/svm
PreparedExecuteTransaction
Interface · @eco-incorp/sauce/svm
The transaction buildExecuteTransaction builds, compiled with every signature slot empty,
and how to sign it: for a caller that simulates or checks it before anything is signed. Signing
compiles the same message, so the signed transaction’s bytes are these.
MeasureExecuteTransactionInput
Interface · @eco-incorp/sauce/svm
