Skip to main content
Avok does not wrap sending and signing in framework hooks. createAvokClient announces a standard provider, and you transact with the standard ecosystem tools. There is nothing Avok-specific in how you send.

​
What gets announced

  • EVM: an EIP-1193 provider, announced over EIP-6963. wagmi, viem, ethers, and RainbowKit discover it like any other injected wallet.
  • Solana: a wallet registered through the Solana Wallet Standard. @solana/wallet-adapter discovers it automatically.
The announced identity (name, icon, and reverse-DNS id) is the operator’s, supplied at config. See Trust and defaults.

​
Supported EIP-1193 methods

The provider answers these JSON-RPC methods:

​
Supported Solana Wallet Standard features

standard:connect, standard:disconnect, standard:events, solana:signMessage, solana:signTransaction, and solana:signAndSendTransaction, on chains solana:mainnet and solana:devnet.

​
Get the provider directly

If you are not using a connector library, client.getEip1193Provider() hands you the EIP-1193 provider for direct use with viem’s custom() transport. See Send a transaction.