Essential Tooling
  • Introduction
  • Guides
    • NFT Global Entry
      • EssentialContext
      • React
    • Gasless Transactions
      • Relayer API
      • EssentialContext
      • React
    • Burner Wallets
    • Account Delegation
  • API Docs
    • Contracts
    • React
    • Signer
Powered by GitBook
On this page
  • Why Use Burner Wallets
  • Architecture
  1. Guides

Burner Wallets

Zero-custody keys for auto-approved transactions

PreviousReactNextAccount Delegation

Last updated 2 years ago

0xEssential's Burner Wallet service allows users to create a username / password based persistent Burner Wallet. Private keys are computed client side to create a zero-custody EOA that never needs assets.

The browser uses the Burner Wallet private keys to sign Gasless Transactions. NFT Global Entry is supported by delegating the Burner Wallet address, allowing your game to send rewards to the authorizing EOA rather than the Burner address.

Burner Wallets are in beta.

Why Use Burner Wallets

Signing messages for game interactions takes users out of flow. With proper delegation, Global Entry and Gasless Transactions, you can offer a seamless UX without sacrificing any security. Your game can run on any EVM chain so the transactions you sponsor are cheap.

Burner Wallets are safe and simple to adopt. They don't have funds to pay for gas, so they depend on Gasless Transactions, but don't require any additional smart contract changes.

Architecture

Our current Burner Wallet solution is based on . We're actively exploring ERC-4337 Smart Contract Wallets, so our approach here is subject to change.

Burner Wallet API

0xEssential provides an API for persistent, zero-custody wallets. Our API does not store private keys. The service also cannot support password resets, so we encourage developers and users to treat these as ephemeral wallets. User accounts are currently shared across applications.

Contact us on Discord to get an API key for Burner Wallets.

Hedgehog, an open-source project from Audius