Help
How accounts, wallets and operations fit together.
Getting started
Which wallet connects to my account?
Your MetaMask login identifies your account. Wallets you import or create for minting and transfers belong to a separate, private list.
Where are my wallets stored?
The planned default is an encrypted vault in this browser. Optional encrypted sync stores ciphertext with AMB. Each scheduled operation separately authorizes the selected wallets for the runner.
What should I test first?
Start with wallet creation, import and encrypted backup/restore. Disperse follows, then collection checks and minting.
Why is an action marked UNTESTED?
Its web flow has not yet received validation for the current source. Terminal approval alone does not enable the web action. A changed or failed path requires RETEST.
What happens after I schedule an operation?
The runner processes the accepted job independently of your open browser. Activity will show the result for each wallet. An unresolved broadcast is reconciled before any further attempt.
What does the runner receive?
For an authorized operation, the selected wallet keys are encrypted for the runner. The runner decrypts them during execution. A compromised runner can copy those keys; cancelling a job cannot revoke a copied private key.