Skip to main content
@eco-incorp/sauce/svm is the Solana side: staging a program through the kitchen, resolving accounts against the compiler’s account manifest, building and sending transactions, and verifying settle programs. Solana execution goes through the Kitchen client here; the SDK’s SVM route helpers emit a legacy instruction that the released engine does not accept.
This page covers sdk/dist/svm/verify.d.ts.
Generated from the type declarations shipped in @eco-incorp/sauce 0.99.4. Each entry shows the package authors’ JSDoc and declaration for this SDK version. For runtime compatibility and deployed addresses, see architecture and deployments.

verifySvmSettleProgram

Function · sdk/dist/svm/verify.d.ts Verifies a compiled SVM settle program is genuine AND enforces expected - the SVM analogue of the EVM check, done by recompile. It:
  1. takes the escrow count N (or infers it from the manifest’s 3N + 3 slots),
  2. recompiles svmSettleSource(N) with expected as defines, and
  3. byte-compares the result, and asserts the manifest’s slot names equal svmSettleRefs(N).
A genuine result means the bytecode IS the reusable settle logic for N escrows, compiled for exactly this floor and this split - all three are the same bytes, so one comparison pins them all. The resolved account identities (from the executed instruction) remain the caller’s own check. Never throws for a non-genuine program; returns { genuine: false, mismatch }.

decodeSvmSettleExecution

Function · sdk/dist/svm/verify.d.ts Decode the released engine’s 65-byte gate header and full CPI account list. This inspects bytes and positions; it authenticates neither execution nor account roles. A Kitchen instruction has a different layout and must be decoded separately.

verifySvmSettleExecution

Function · sdk/dist/svm/verify.d.ts Compare inline bytes, or caller-supplied staged bytes/pin, with a canonical recompile. This does not check the callee, gate derivation/signature, account roles, or transaction success. Engine calldata has no staged content pin; the caller must connect its pin to the code account.

SvmSettleExpectation

Interface · sdk/dist/svm/verify.d.ts The values a settle program was compiled with. Both are folded into the bytecode, so they are what a recompile pins: naming them is how a caller says “prove the program enforces THIS floor and THIS split”, rather than reading them back out of an execution and trusting them.

SettleManifestLike

Interface · sdk/dist/svm/verify.d.ts Just enough of an account manifest to count and name its slots.

SvmSettleVerification

Interface · sdk/dist/svm/verify.d.ts

SvmExecutionWireFormat

Type · sdk/dist/svm/verify.d.ts Released engine CPI wire, or an explicitly selected pre-gate inspection format.

SvmSettleAccountLike

Type · sdk/dist/svm/verify.d.ts

SvmSettleExecutionInput

Interface · sdk/dist/svm/verify.d.ts

SvmExecutionGate

Interface · sdk/dist/svm/verify.d.ts Parsed derivation material only; this does not validate the Pot PDA or its signature.

DecodedSvmSettleExecution

Interface · sdk/dist/svm/verify.d.ts

SvmSettleExecutionVerifyInput

Interface · sdk/dist/svm/verify.d.ts

SvmSettleVerifiedBy

Type · sdk/dist/svm/verify.d.ts

SvmSettleExecutionVerification

Interface · sdk/dist/svm/verify.d.ts