Public beta is live. See something broken?
Unified access boundary
Brimstone needs one account boundary across decks, rewards, linked wallets, and future trade permissions. The auth surface keeps sign-in separate from custody while still attaching everything to the same player record.
Session policy
Remembered on this device
Custody network
Base
Authentication required
Google, email OTP, and MetaMask can all enter the same Brimstone account boundary. Wallet verification still happens separately when custody matters.
Wallet-first path
MetaMask can establish the session boundary, but verified custody wallets still need explicit linking before deposits, withdrawals, and off-chain ownership are attributed to this profile.
Brimstone verifies custody wallets separately from sign-in. Wallet activity on Base is attached to the player profile only after explicit verification.
Why auth now
Why auth now
The browser sandbox can already submit commander actions, but the real product needs one player account boundary across decks, rewards, linked wallets, and future trade permissions.
Custody rule
Custody rule
Linked wallets prove the source account for deposits and the destination account for withdrawals. Once assets enter the shared Brimstone game wallet, internal ownership moves independently of the chain wallet that brought them in.
What ships now
What ships now
Google OAuth, email OTP, linked-wallet verification, and wallet-bound deposit attribution groundwork are in scope now, with profile security expanding to passkeys or biometrics on supported devices. Full custody settlement, trading, and market pricing stay on the next delivery step.