Learn
How Xenn Web3 works
Xenn uses embedded wallets to keep the music product approachable, but the on-chain rules still matter. This page explains where the flow is gasless, where ETH is still required, and why the new wallet hub exists.
1. Identity
Xenn wallet vs browser wallet
A Xenn wallet is an embedded wallet linked to an email login. It keeps the user inside the Xenn flow. A browser wallet like MetaMask still works as an external option, but it is no longer required for creator minting.
2. Creator Flow
Minting is gasless for creators
The creator signs with the embedded wallet, then Xenn’s relayer-backed queue handles the on-chain mint work. That means artists do not need to preload ETH just to mint collector releases.
3. Buyer Flow
Buying is direct on-chain settlement
Collector checkout calls the contract’s buy path directly. The buyer wallet pays the NFT price and the network fee in native ETH. That is why embedded-wallet buying only works after the buyer wallet is funded.
4. Wallet Hub
Why the new /wallet page matters
The wallet hub gives users one branded place to inspect balance, receive funds, send funds out, and eventually buy ETH, swap, and cash out without exposing raw vendor wallet screens.
Current Operator Truth
Funding path right now
Until Xenn wires a native on-ramp, the practical way to fund an embedded wallet is to send ETH into it from MetaMask, Coinbase, or another external source on the correct chain. The /wallet page makes that operational truth visible instead of hiding it.
Roadmap Shape