# Institutional Vault sandbox enrollment and onboarding

This page covers two phases: **requesting** a hosted Blockdaemon Wallet sandbox and **onboarding** your technical team once the environment is ready. The sandbox demonstrates the Multi-Party Computation (MPC) self-custody workflow, including user management, governance policies, and disaster-recovery-related steps.

* * *

## Part 1: Request a hosted sandbox

### Step 1: Submit the request form

Complete the **Get Started with Blockdaemon Wallet** request form at [https://www.blockdaemon.com/get-started/wallet](/content/get-started/wallet/index.html). You must fill out and submit this form to begin the hosted sandbox process.

### Step 2: Provisioning

1. Blockdaemon reviews the request.
2. When approved, we provision a hosted sandbox wallet using **Blockdaemon's Okta identity provider** for authentication, configured for your sandbox tenancy.

### Step 3: Test tokens

If your evaluation requires balances or assets on supported **test** chains, tell us during onboarding or provisioning. We can supply **test tokens** where applicable so your team can exercise transfers and workflows without sourcing funds yourself.

### Step 4: Handover

When setup is complete, we provide access details and the URL for your hosted sandbox wallet UI.

* * *

## Part 2: Technical onboarding (after access)

### 1. Environment access and authentication

Your dedicated sandbox is served over HTTPS. Replace the placeholder with the hostname Blockdaemon supplied for your deployment:

- **Sandbox web UI:** `https://<your-domain>.blockdaemon-wallet.com/`

1. Open the sandbox UI link.
2. On the login page, choose **sign-up** to create a new account. Use the **same email address** you provided when you submitted the [Get Started with Blockdaemon Wallet](/content/get-started/wallet/index.html) request form so your sandbox login matches what Blockdaemon configured for your team.

3. Complete email verification for that address before the first successful sign-in.
4. Return to the UI and sign in with the email and password you set during sign-up.

### 2. Security setup: ApproverApp registration

Institutional Vault uses a maker and checker approval model, with mobile or desktop-based secure execution for approvers.

- **Approver registration:** After you authenticate in the browser, follow the instructions to register the ApproverApp on **mobile or desktop** (for example by scanning the **QR code** on mobile, or using the desktop app flow where applicable).
- **Secure identity:** Registration binds approver signing to the ApproverApp instance on your device, using hardware-backed or OS-level protections where available (for example Secure Enclave on supported Apple devices), for administrative and transaction approvals.
- **Governance:** You **cannot** approve your own operations. Administrative changes require approval from another member of your **Owner** group. Blockdaemon provisions Owner accounts for your tenant so your team can complete approvals during the evaluation.

### 3. Disaster recovery: ERS backup exercise

After ApproverApp enrollment, you may be prompted to complete a **one-time Emergency Recovery Secret (ERS)** backup download.

**Sandbox note:** In many hosted sandboxes, key shares are encrypted with a **non-production** ERS public key. You will **not** be able to recover the live master key material using the recovery tooling against that ciphertext. The goal is to walk through the **startup and recovery UX** your team would follow in production, not to perform a real key recovery.

### 4. Developer integration and API access

For programmatic integration, use the API host and tooling Blockdaemon gives you for your sandbox. Typical patterns (substitute your assigned hostname):

| Resource | Endpoint / URL |
| --- | --- |
| API base | `https://<your-domain>.api.blockdaemon-wallet.com/` |
| OpenAPI (Swagger UI) | `https://<your-domain>.blockdaemon-wallet.com/swagger.html` |
| Cold node 0 (if enabled) | `https://<your-domain>-cold-0.blockdaemon-wallet.com/` |
| Cold node 1 (if enabled) | `https://<your-domain>-cold-1.blockdaemon-wallet.com/` |

Not every sandbox includes cold nodes; confirm which endpoints are in scope for your deployment.

### 5. Technical documentation and resources

- **Wallet onboarding (browser + ApproverApp):** [Onboarding the Wallet](https://vault.docs.blockdaemon.com/docs/onboarding-the-wallet)
- **API quick start and API key:** [Quick Start — Blockdaemon Wallet](https://vault.docs.blockdaemon.com/reference/quick-start-blockdaemon-wallet)
- **Hot and cold pairing (if cold URLs are enabled):** [How to pair offline and online accounts in Blockdaemon Institutional Vault](https://vault.docs.blockdaemon.com/docs/how-to-pair-offline-online-accounts-in-blockdaemon-institutional-wallet)
- **Backup and emergency recovery concepts:** [Emergency Recovery](https://vault.docs.blockdaemon.com/docs/emergency-recovery)

Please contact us via [email](mailto:support@blockdaemon.com) or support chat if you encounter an issue, bug, or need assistance. Don't forget to include any relevant details about the problem. To request a wallet form and Institutional Vault Approver form, please click [here](/content/support/index.html) or contact [our sales team](/content/get-in-touch/?contact-sales/index.html).