Backend wallets
Backend wallets are developer-controlled wallets managed within your server environment. Unlike client-side wallets—where the user holds the keys and must authorize every interaction—backend wallets allow your application to programmatically sign transactions and manage assets.
Choosing the right wallet
Understanding the trade-offs between backend and client-side wallets is key to your architecture:
| Feature | Backend wallets | Client-side wallets |
|---|---|---|
| Control | Developer-controlled (API) | User-controlled (PKI) |
| Primary use | Automation, minting, treasury | User transactions |
| Signing | Programmatic | User-authorized |
| Ideal for | High-throughput system tasks | Personal asset ownership |
Why use backend wallets?
Seamless automation
Perform on-chain actions instantly based on server-side triggers, without waiting for a user to be online or approve.
Enterprise-grade security
Isolate administrative keys within your secure infrastructure. Leverage Openfort's TEE-based signing for maximum protection.
High throughput
Manage multiple nonces and sign hundreds of transactions in parallel to scale with your user base.
Abstracted complexity
Remove crypto friction. Users interact with your app while your backend handles blockchain orchestration.
Common use cases
- Programmatic rewards: Automatically drop tokens or NFTs into player wallets when they complete an achievement.
- Gas sponsorship: Fund your paymasters through a backend wallet to ensure your users never see a gas fee.
- Administrative operations: Periodically sweep funds, rebalance treasuries, or update smart contract configurations.
- Marketplace clearing: Settle trades and distribute royalties programmatically as soon as off-chain conditions are met.
Backend SDKs and API
Start building with our server-side libraries, optimized for performance and secure credential management.
