Note: This package is currently in beta. Please test thoroughly in development environments before using in production.
A flexible manager for orchestrating WDK wallet and protocol modules through a single interface. This package lets you register blockchain-specific wallet managers, derive accounts, and coordinate multi-chain wallet flows from one WDK instance.
This module is part of the WDK (Wallet Development Kit) project, which empowers developers to build secure, non-custodial wallets with unified blockchain access, stateless architecture, and complete user control.
For detailed documentation about the complete WDK ecosystem, visit docs.wdk.tether.io.
npm install @tetherto/wdkimport WDK from '@tetherto/wdk'
import WalletManagerSolana from '@tetherto/wdk-wallet-solana'
import WalletManagerTon from '@tetherto/wdk-wallet-ton'
import WalletManagerTron from '@tetherto/wdk-wallet-tron'
const seedPhrase = 'abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon about'
const wdk = new WDK(seedPhrase)
.registerWallet('solana', WalletManagerSolana, {
rpcUrl: 'https://api.devnet.solana.com',
commitment: 'confirmed',
})
.registerWallet('ton', WalletManagerTon, {
tonClient: { url: 'https://testnet.toncenter.com/api/v2/jsonRPC' },
})
.registerWallet('tron', WalletManagerTron, {
provider: 'https://api.shasta.trongrid.io',
})
const account = await wdk.getAccount('solana', 0)
const address = await account.getAddress()
console.log('Address:', address)
wdk.dispose()- Wallet Registration: Register multiple blockchain wallet managers through one WDK instance
- Unified Account Access: Retrieve accounts by chain, index, or derivation path through a consistent API
- Multi-Chain Operations: Coordinate balances, fee lookups, and transaction flows across registered chains
- Protocol Registration Support: Attach swap, bridge, lending, fiat, and swidge protocols to registered blockchains
- Middleware Hooks: Intercept account derivation with custom middleware
- Transaction Policies: Local policy engine that intercepts write-facing operations and enforces user-defined ALLOW/DENY rules at project (global or wallet-bound) and account scopes — with simulation, nested-call handling, and structured
PolicyViolationErrors - Seed Utilities: Generate and validate BIP-39 seed phrases
- Selective Disposal: Dispose specific registered wallets or clear the full WDK instance
Register policies on a WDK instance to gate write-facing operations on every wallet account. Each registered rule can ALLOW or DENY an attempted operation based on a condition function; matching DENYs throw a PolicyViolationError before the underlying method runs.
import WDK, { PolicyViolationError } from '@tetherto/wdk'
import WalletManagerEvm from '@tetherto/wdk-wallet-evm'
const wdk = new WDK(seedPhrase)
.registerWallet('ethereum', WalletManagerEvm, { provider: '...' })
.registerPolicy({
id: 'value-cap',
name: 'Cap value at 1 ETH',
scope: 'project',
rules: [{
name: 'allow-under-1-eth',
operation: 'sendTransaction',
action: 'ALLOW',
conditions: [({ params }) => BigInt(params.value) <= 10n ** 18n]
}]
})
const account = await wdk.getAccount('ethereum', 0)
try {
await account.sendTransaction({ to: '0x…', value: 5n * 10n ** 18n })
} catch (err) {
if (err instanceof PolicyViolationError) {
console.log(err.policyId, err.ruleName, err.reason)
}
}
// Run the same evaluation without executing the transaction.
const result = await account.simulate.sendTransaction({ to: '0x…', value: 1n })
// → { decision: 'ALLOW' | 'DENY', policy_id, matched_rule, reason, trace }Policies have two scopes — project and account. A project-scope policy applies globally by default, or only to the wallets named in its wallet field (wallet: 'ethereum' or wallet: ['ethereum', 'ton']). The wallet value is the same string passed to registerWallet. It might be a chain name like "ethereum", but it could equally be "treasury-cold" or any label the consumer chose; the engine treats it as an opaque key. An account-scope policy must declare a wallet and targets specific accounts within it, identified by either derivation path (accounts: ["0'/0/0"]) or integer index (accounts: [0, 1]) — index entries match accounts retrieved via wdk.getAccount(wallet, index); path entries match either retrieval style. Evaluation is narrowest-first with DENY winning across scopes. Account-scope ALLOW rules can opt into override_broader_scope: true to short-circuit broader policies for explicit exceptions (e.g., treasury accounts). Conditions can be sync or async and may carry user-owned state via closures. Templates (@tetherto/wdk-policy-templates) and a portal UI for editing policies are coming in later phases.
The engine is default-deny on governed accounts. As soon as any policy applies to an account, the engine wraps every method in OPERATIONS (the set of write-facing and signing primitives — sendTransaction, signTransaction, transfer, approve, sign, signTypedData, signAuthorization, delegate, revokeDelegation, and protocol methods like swap, bridge, swidge, etc.) on that account. Any call to a wrapped method whose operation is not addressed by an ALLOW rule throws PolicyViolationError with reason: 'no-applicable-rule'.
This is intentional: a "cap transfer at $100" policy must not be sidesteppable by sendTransaction({ to: token, data: <ERC-20 transfer calldata> }), approve(spender, MAX), an off-chain signTypedData Permit, or an ERC-7702 delegate to an attacker contract. The engine closes those bypasses by treating any unaddressed money-movement op on a governed account as DENY.
If you want permissive semantics on a specific account (allow anything that isn't explicitly denied), register a wildcard ALLOW rule as a baseline and layer specific DENYs on top:
wdk.registerPolicy({
id: 'permissive-baseline',
scope: 'project',
rules: [
{ name: 'allow-all', operation: '*', action: 'ALLOW', conditions: [] },
{ name: 'block-bad', operation: 'sendTransaction', action: 'DENY', conditions: [({ params }) => isSanctioned(params.to)] }
]
})Accounts that have no registered policies are not governed — the proxy is not applied, and method calls go straight to the underlying account at zero cost.
The engine wraps accounts through an ES Proxy so internal SDK code that uses this.method() naturally bypasses enforcement — nested-call escape (e.g. bridge internally calling sendTransaction) works without any async-context tracking. The same code path runs on every JavaScript runtime that supports Proxy, including Bare.
Policy enforcement applies to the surface of the proxy returned by getAccount / getAccountByPath. Reaching for underscore-prefixed fields (e.g. protocol._account) bypasses enforcement by design — treat them as private. The same applies to account-level operations invoked from inside a protocol's own methods (e.g. bridge.bridge(...) internally calling this._account.sendTransaction(...)), which is the documented nested-call escape; it lets protocols use the account they were constructed with without re-entering the engine on every internal step.
- WDK Wallet Modules including EVM, Solana, TON, TRON, and Bitcoin integrations
- Protocol Modules registered through the WDK interface
- Node.js and ESM-based applications that coordinate multiple wallet modules in one runtime
| Topic | Description | Link |
|---|---|---|
| Overview | Module overview and feature summary | WDK Core Overview |
| Usage | End-to-end integration walkthrough | WDK Core Usage |
| Configuration | Wallet registration and manager configuration | WDK Core Configuration |
| API Reference | Complete class and type reference | WDK Core API Reference |
| Example | Description |
|---|---|
| Getting Started | Generate a seed phrase, validate it, and create a WDK instance |
| Register Wallets | Register Solana, TON, and TRON wallet managers in one WDK instance |
| Manage Accounts | Retrieve accounts by index and path and inspect multi-chain balances |
| Send Transactions | Quote and optionally send native transactions across multiple chains |
| Middleware | Register middleware and inspect account access hooks |
| Error Handling | Handle missing registrations and dispose selected wallets safely |
For detailed walkthroughs, see the Usage Guide. See all runnable examples in the wdk-examples repository.
Join the WDK Discord to connect with other developers.
For support, please open an issue on GitHub or reach out via email.
Contributions are welcome! Please feel free to submit a Pull Request.
This project is licensed under the Apache License 2.0 - see the LICENSE file for details.