TreasuryOps

Who it is for

Companies that already use a wallet or a custody provider and still approve movements in a chat.

The workflow, before and in the demo

Modules

• Wallet inventory as labels
• Roles and a spend limit
• Counterparty allow-list
• Request and simulation
• Dual control
• Emergency hold
• Reconciliation note
• Audit history

What would integrate later

• A custody or wallet provider the buyer has already selected. This page does not select one and does not connect one.
• Execution, if it ever happens, stays at that provider.
• An accounting export is a later design, not a live feed.

Controls, and the limit on them

• The custody console uses labels, an allow-list, and a hold. It does not display a private key.
• Holding client assets is out of scope. So is a claim that the policy has been certified.
• Account-abstraction and wallet-session references elsewhere on the site are reference-only. They are not copied into this line.

Commercial shape

If a pilot is later agreed, the shape is a controls fee. No price on this page is a quotation.

• Fit scan

  Exploring whether the workflow is real

  A role, limit, and custody-gap note. The gap is not filled by Blockchain Lab holding keys.

  Illustrative range if a team is later free: 1–2 weeks. Not a delivery promise.

• Working demo

  Needs something colleagues can click

  The custody console: synthetic policy, dual control, and an emergency hold.

  The synthetic demo is already on this site. A private walkthrough is not scheduled here. Not a delivery promise.

• Pilot scope

  Ready to discuss a limited pilot, with counsel

  A policy model for a provider the buyer already uses. No sandbox credential is issued here.

  Illustrative range only after counsel and a provider are chosen: 6–12 weeks. Not a delivery promise.

• Integration design

  A provider or system of record is already chosen

  Where that provider's export would land. Not a connection.

  Illustrative range for a later pilot: 3–6 months. Not a delivery promise.

• Managed design

  A pilot exists and someone must keep it current

  Policy review and a drill after a pilot exists. Not a custody mandate.

  Monthly, only after a pilot exists. Not a delivery promise.

A pattern, not a customer

Pattern, not a client: a company with a wallet provider still approves movements in a chat. No company is named because none is claimed.

Questions worth answering first

• Who holds the keys today?
• What amount requires a second person?
• Which destinations are allowed, as names?
• What should an incident freeze stop, and who may lift it?

Nearby, and what it is not

• Custody.io

  A public product that compares custody providers. It is not itself a custodian. This service line does not operate it and does not hold client assets.

Adjacent lines

• PayoutOps
• DataOps

What this line will not do

• Not regulated custody. Blockchain Lab does not hold client assets.
• Not payment execution. A rail, when one is used, is operated by a provider the buyer and its counsel select.
• Not legal advice.
• Not financial promotion and not an offer.
• Not an AML or KYC certificate. A demo case file is not a compliance opinion.
• Not a statement of returns. Return: Not shown.
• Not a production security clearance. No audit is claimed.
• Not a new chain by default.
• Demos use synthetic data. No real funds, wallets, private keys, or customer records.
• Business documents do not go on a public chain.