Installation

yarn add @relayprotocol/relay-ton-wallet-adapter @relayprotocol/relay-sdk

Also make sure to install the peer dependencies required by the adapter if your application doesn't already include them:

yarn add viem @relayprotocol/relay-sdk @ton/core @ton/ton

Usage

adaptTonWallet turns a connected TON wallet into an AdaptedWallet the Relay SDK can execute against. The user's key lives in their wallet, so the adapter never signs — you pass a sendTransaction callback that signs + broadcasts the request via your wallet provider (e.g. Dynamic or TonConnect UI), and the adapter handles request building and on-chain confirmation.

import { adaptTonWallet } from '@relayprotocol/relay-ton-wallet-adapter'

const adaptedWallet = adaptTonWallet(walletAddress, async (request) => {
  // `request` is a TonConnect-style { validUntil, messages, network? }.
  // Forward it to your wallet provider's send method (e.g. Dynamic's TON
  // connector, or `tonConnectUI.sendTransaction`) and return the result. The
  // adapter accepts { boc } (the signed external-message BOC most TonConnect
  // wallets return) or { transactionHash }.
  const boc = await wallet.sendTransaction(request)
  return { boc }
})

Confirmation endpoint

handleConfirmTransactionStep polls a read-only @ton/ton TonClient to confirm the origin transaction. The RPC endpoint comes from the TON chain's httpRpcUrl in the Relay client's chain configuration, so to use a custom endpoint (e.g. a keyed provider for production), override the TON chain's httpRpcUrl when configuring the SDK client rather than passing it to the adapter.

Note: message signing (handleSignMessageStep) is not implemented, as it is not used by deposit/bridge flows.