Skip to main content

Overview

The Solana delegated client mirrors the EVM delegated client one-for-one — same auth model, same webhook decrypt helper, same revocation. Only the chain client type and the signature format differ. For the full delegation flow (how the webhook is sent, what the encrypted envelope contains, security best practices), see EVM Delegated Access. This page covers only the Solana-specific bits.

Prerequisites

  • EVM Delegated Access — read this first for the full flow
  • An RSA private key registered with Dynamic for webhook decryption (PEM-encoded PKCS#8)

Decrypting the Webhook

Identical to EVM:

Building the Delegated SVM Client

DelegatedSvmWalletClient is AutoCloseable — wrap it in try-with-resources or close it explicitly.

Signing a Solana Message

signatureB58 is the base58-encoded 64-byte Ed25519 signature.

Signing a Solana Transaction

signTransaction accepts the serialized message bytes (bytes(transaction.message) — not the full serialized tx) and returns the Ed25519 signature as lowercase hex (not base58 — note the format difference vs signMessage):
Splice the hex-decoded signature into your wire envelope at the appropriate signer slot — see Sign SVM Transactions § Assembling the Wire Envelope.

Exporting a Private Key

Exporting bypasses MPC entirely — see Export SVM Private Key for the same one-way-operation caveats.

Revoking Delegation

Same as EVM — call revokeDelegation on the base delegated client:
Last modified on August 3, 2026