OpenViSTAI · Agents · Blockchain · Crypto
Menu
Wallets

Wdk

Wdk is a JavaScript modular plug-in framework for assembling and orchestrating multi-chain cryptocurrency wallets through a unified interface. It lets applications register blockchain-specific wallet managers and protocols, derive accounts, coordinate wallet operations, apply transaction policies and dispose of selected modules or the complete instance.

Independent OpenViST project profile, based on linked sources.

Wdk — OpenViST project profile in Wallets.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Wdk when a crypto application needs a modular wallet layer spanning multiple chains and wants consistent account access and policy handling rather than a standalone consumer wallet interface.

Who it is for

  • Developers building multi-chain, non-custodial crypto wallets.
  • Teams integrating wallet functionality into blockchain applications.
  • Engineers creating tooling around account derivation, protocol flows and transaction controls.

Documented uses

  • Register wallet managers for multiple blockchains through one WDK instance.
  • Retrieve accounts using chain identifiers, indexes or derivation paths.
  • Coordinate balances, fee lookups and transaction flows across registered chains.
  • Attach protocol modules for swap, bridge, lending, fiat and related flows.
  • Apply project- or account-level rules to write-facing wallet operations.
Before you choose

Requirements & limits

The repository is public and licensed under Apache-2.0. The package is marked beta in its README, and the documented setup uses npm installation plus wallet-provider configuration.

  • The central package coordinates modules but requires separate chain-specific wallet managers and provider or client settings.
  • The framework uses a seed phrase to initialize the WDK instance, so the integrating application must define how wallet credentials are handled.
  • Transaction policies can be scoped globally, to selected wallet labels, or to specific accounts, with DENY taking precedence unless an explicit broader-scope override is configured.
  • The documented package is JavaScript-based and includes account, protocol, middleware, seed-utility and disposal capabilities.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Register wallet modules and derive an account

Set up one WDK instance with documented Solana, TON and TRON wallet managers, then retrieve a Solana account address.

Before you start

  • JavaScript project with the @tetherto/wdk package installed.
  • The @tetherto/wdk-wallet-solana, @tetherto/wdk-wallet-ton and @tetherto/wdk-wallet-tron modules.
  • A seed phrase and the provider or RPC configuration required by each registered wallet manager.

Steps

  1. Install @tetherto/wdk.

  2. Create a WDK instance with a seed phrase.

  3. Register the Solana, TON and TRON wallet managers with their documented provider settings.

  4. Retrieve the Solana account at index 0 and request its address, then dispose of the WDK instance.

Expected outcome

A configured WDK instance can expose a derived address through the unified account interface.

Guide limitations

  • The repository labels the package beta and recommends development testing before production use.
  • The example uses development or test network provider URLs; it does not establish production-network readiness or successful execution.
Source-based practical guide

Evaluate a transaction policy before execution

Register a project-level value cap for an EVM wallet and simulate whether a transaction is allowed.

Before you start

  • The WDK package and an EVM wallet manager.
  • A configured provider and seed phrase.
  • A policy rule using the documented operation, arguments and action fields.

Steps

  1. Create a WDK instance and register an EVM wallet manager.

  2. Register a project-scope policy for the wallet that allows transactions at or below the specified value.

  3. Retrieve an account and call the documented simulation method with transaction arguments.

  4. Read the returned decision and policy details without executing the transaction.

Expected outcome

The policy engine returns an allow-or-deny decision with policy, rule, reason and trace information.

Guide limitations

  • The example documents policy evaluation and simulation, not a completed blockchain transaction.
  • Policy behavior depends on the registered wallet and the conditions defined by the application.
COMPARE OPTIONS

Compare options for Wallet connections

These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.

ProjectDocumented purposePlatformAccess and requirements
WdkRegister wallet managers for multiple blockchains through one WDK instance.Cloud, Desktop, Mobile, ServerThe repository is public and licensed under Apache-2.0. The package is marked beta in its README, and the documented setup uses npm installation plus wallet-provider configuration.
Dioxus Wallet AdapterAdd Solana wallet connectivity to a Dioxus web application.Web
Vue CLI Plugin Web3ModalConfigure injected browser and WalletConnect provider options.Web
Evidence and transparency

Sources & review

Source record details
Source availability
Active
Sources checked
3 October 2026
Original website title
tetherto/wdk · Official homepage title · retained in its source language