A considered start.
Before you create a vault, know how to access the beta, protect your devices, and keep a route back. A little preparation makes the next steps clearer.
1. Get beta access
Join the wallet waitlist for invitations and product updates. Access is limited during the private beta. Use the installation instructions supplied with your invitation; if a download or sender looks unfamiliar, confirm it with support@coinhost.com before proceeding.
The private beta is for testnet. Do not send mainnet bitcoin to a beta vault. Mainnet availability will be announced separately.
2. Protect your account
Follow the registration steps for your beta build. Use a unique password wherever one is required, protect the email account used for recovery, and enable the additional authentication options available to you.
Read the Terms and Privacy Policy before joining. Account access and signing authority are different: signing in to an account is not a replacement for the keys needed to spend.
3. Understand your mobile key
Your mobile key is one participant in the 2-of-3 design. Your hardware signer holds another key; Coinhost holds the recovery key. Everyday signing uses your two keys.
Before setup, check how your beta build protects and backs up the mobile key, and how you would recover after losing the phone. Do not assume that an ordinary phone backup also restores signing access.
4. Protect device access
Use a strong device passcode, keep your operating system current, and configure the app's available access protections. A PIN or biometric check adds an access barrier; it does not replace a backup or make a compromised device safe.
Keep recovery information away from the devices it is meant to recover. Never send a seed phrase, private key, PIN, or password to Coinhost support.
5. Before your first vault
- Confirm your hardware model and firmware are supported by the beta build.
- Have the signer ready and understand its own backup procedure.
- Know where you will keep the vault descriptor and recovery instructions.
- Plan a testnet receive, send, and recovery rehearsal before relying on the setup.