TreasuryOps
Wallet policy console
Simulate a movement, require a second approval, and freeze the request.
The service page is TreasuryOps. Destinations are labels. Blockchain Lab does not hold keys.
Workflow in the demo
- 1. A wallet described as a label.
- 2. An allow-list of destination names.
- 3. A simulated request.
- 4. Dual control above a limit.
- 5. An emergency hold.
Refused on this blueprint
- Not regulated custody.
- No private key is shown or stored.
- Reference-only account patterns elsewhere on the site are not copied into this demo.
Pattern, not a client: a company already has a wallet provider and still approves movements in chat. No company is named.
Catalogue template/Check it in the composer/Venture path, if it becomes a company
Synthetic data and a simulated workflow. No real funds, wallets, private keys, customer records, or chain transactions. Not an audit, not a legal review, and not for production.