We are SO excited to roll out server wallet access to all participants of ETHGlobal’s first ever AI-focused hackathon: Agentic Ethereum. Please use this as your quickstart guide to setting up server wallets. We’ll be in the ETHGlobal Discord and in our Dev Slack for any questions!

How do I get access to server wallets?

In order to gain access to server wallets, please email [email protected] with your Privy AppID and we’ll get you set-up with access ASAP. Get started with the quickstart below or read more about the server wallets and their architecture in our docs.

What are server wallets?

Server wallets enable you to create and manage embedded wallets via a low-level, flexible API. Privy supports server wallets for EVM via a TypeScript SDK or our REST API.

Server wallets are programmatically controlled by an app or bot’s backend, allowing developers to automate workflows like fund transfers, trading, or escrow services without user involvement. Unlike Privy’s embedded wallets, where users control their keys, server wallets place operational control with the developer to handle specific use cases at scale.

Server wallets are perfect for backend-heavy applications like treasury management, shared wallets for collaborative apps (like DAOs), onchain gaming economies, trading bots (like Bankr and Cleopetra), and other workflows where direct user involvement isn’t needed.

A note on early access:

While server wallets are early access right now, they are production ready. In fact, they are built on the same cryptosystem that enables all Privy embedded wallets today.

A core part of our work at Privy is about working very closely to developer champions with whom we can shape our infrastructure so it is purpose-built. This means collaborating with the earliest users of libraries to refine ergonomics and ensure the tool is working just right for you. In giving you early access to server wallets, we are hoping you will actively share feedback with us.

We’re iterating quickly on these surfaces so please share feedback liberally so we can continue to improve server wallets ahead of GA release.

<aside> 💡

Privy’s server wallets support:

• Secure authorization using your Privy app secret, and signed payloads to ensure that all wallet approvers have signed off on transactions.
• A flexible policy engine for managing what wallet actions can be taken.
• Creating wallets on EVM (automatic support for Base, Polygon, Celo, and all other EVM-compatible chains).
• Executing arbitrary transactions with wallets, including smart contract interactions.
• Idempotent transaction execution with an idempotency key. You can ensure the same transaction is never sent twice by simply including the same idempotency key on any retries of that same transaction request.
• Custom metadata for managing wallet ontologies. This means managing and identifying wallets with a custom ID (unique to each wallet) and custom tags (non-unique to each wallet, used to associate multiple wallets to a single group, for instance a given Bridge customer).
• Querying balances for native tokens, arbitrary token addresses, and aggregated balances across groups of wallets.
• Gas management using a third-party gas payer on EVM. </aside>

Early access feature releases

As part of our work iterating with champions on early access, we are operating on a regular release cycle for server wallet features. Please reach out if you’re interested in particular features listed below, or if there are any you don’t see.

Use the table below to see what functionality is available in production.

Getting started with the server wallets SDK

0. Prerequisites

• Set up a Privy app
  • Retrieve your App ID and App secret