# DBIS sandbox.d-bis.org and interop.d-bis.org

**Prerequisite:** Public read APIs and developer portal baseline stable ([DBIS_WEB_AND_INSTITUTION_MASTER_BLUEPRINT.md](../02-architecture/DBIS_WEB_AND_INSTITUTION_MASTER_BLUEPRINT.md)).

## sandbox.d-bis.org

**Purpose:** Isolated execution for simulated transactions, GRU **test** issuance (if/when defined), compliance checks against non-production rulesets.

**Infra options (Proxmox-first):**

- Dedicated Besu network namespace or Chain 2138 testnet profile.  
- Fabric channel for permissioned samples.  
- No production keys; faucet and reset policies documented.

**Safety:** Separate RPC URLs, separate NPM upstream, clear UI banner “Sandbox”.

## interop.d-bis.org

**Purpose:** CBDC and cross-chain **lab** — corridor simulation, CCIP-style flows.

**Alignment:** CCIP and bridge runbooks under [docs/07-ccip/](../07-ccip/) (e.g. [TRUTH_NETWORK_BRIDGE_SPEC.md](../07-ccip/TRUTH_NETWORK_BRIDGE_SPEC.md), [CW_BRIDGE_APPROACH.md](../07-ccip/CW_BRIDGE_APPROACH.md)).

**Deliverables:**

1. Lab UI listing supported test corridors and reset schedule.  
2. Links to Gitea `reference-implementations` and SDK quickstarts.  
3. Optional: scheduled soak tests with published results JSON.

## Verification

Add hosts to E2E inventory as optional-until-live; run `verify-end-to-end-routing.sh` after DNS and upstream provisioning.