Skip to main content
Privy enables you to interface directly with wallets by sending JSON-RPC requests or directly requesting signatures over messages and transaction payloads. This allows you to use Privy for low-level key management and achieve any onchain use case with Privy wallets. RPC splash

​
Taking actions with wallets

To take an action (such as executing a signature, transfer, or other transaction), there are three approaches. While using wallet actions is generally recommended for most use cases, your application may need to interface with wallets directly for more custom functionality. This is fully supported in parallel with wallet actions via RPCs.

​
Using RPCs

For Tier 3 chain types, Privy supports the standard set of JSON-RPC methods for that chain type (e.g. EIP-1193 for EVM chains including Tempo) – including message signing, transaction signing, and transaction broadcasting. View guides for using each of these JSON-RPC methods with Privy in the left navigation. For Tier 2 and Tier 1 chain types, Privy supports using the wallet’s private key to sign custom payloads – allowing you to construct transactions of your choosing and sign them with the wallet. Your application can then broadcast this signed transaction to the chain to execute it.
The wallet RPC endpoint is a synchronous endpoint, and a successful response indicates that the transaction has been broadcasted to the network. Transactions may get broadcasted but still fail to be confirmed by the network. The endpoint does not wait for confirmation or retry if the transaction fails to be confirmed. To handle these scenarios, see our guide on speeding up transactions.