EVM Protocol SDK - Swig

Introduction

The EVM Protocol SDK connects your application to Swig wallets through your own RPC connection and signing keys.

Use when: you need direct control of wallet creation, permissions, and transaction execution.
For: app developers integrating a compatible EVM deployment in TypeScript, Rust, or Python.

How it works

Connect to a compatible deployment and choose an application signer.
Create a wallet with a root authority, then fund its vault.
Add roles with permissions for the tasks their signers need.
Execute through the wallet config and check the transaction or UserOperation result.

Wallet structure

Concept	Purpose
Account / config	Holds roles and receives wallet execution requests
Vault	Holds the assets the wallet spends
Authority	Identifies who may approve a role’s operations
Permission	Sets a role’s capabilities and spending allowance
Role ID	Selects the authority and permissions used for an operation

Execution paths

Path	Authorization	Gas payer
Direct transfer	Role’s EOA sends a transaction	That EOA
Sponsored transfer	Role signs a UserOperation	Paymaster through a compatible bundler

Both paths spend assets from the vault and enforce the selected role’s permissions.

SDK example

The EVM SDKs are currently consumed from source. Obtain the repository first:

git clone https://github.com/anagrambuild/swig-protocol-sdk.git
cd swig-protocol-sdk

Then install the language you use:

cd evm/typescript
bun install --frozen-lockfile

cd evm
cargo build --locked -p swig-evm --examples

cd evm/python
uv sync --locked

Start with Environment setup, then create a wallet. The examples use Secp256k1 authorities; sponsored operations require an already deployed account, EntryPoint v0.9, and a compatible provider.