Block Gemini

Explore the connected ecosystem.

Who can approve a treasury payment or recover access?

Walk a fictional treasury instruction through a two-person approval policy. Then inspect a separate recovery request and the team responsible for it.

Scope my wallet operations

Interactive example · fictional records

Choose an operator action

Treasury instruction W-22 · Supplier payment

Authorisation

Preparer recorded

Instruction
Supplier reference attached
Authorisation
Preparer recorded
Operations state
Second approval required
Payment draft
Review decision

Send the instruction for independent review

The preparer can propose a payment. A different authorised reviewer checks the beneficiary, amount and policy before the instruction can be released.

Scope my wallet operations

What we can build with you

A wallet operations model defining custody boundaries, approval roles, recovery ownership and reconciliation with your finance system.

Bring to discovery
Bring one payment instruction, the roles that can approve it and the current process for recovering an operator’s access.
How to test the pilot
Replay a single approval, a changed beneficiary and a recovery request. Verify the authorisations and resulting audit trail in a test environment.
Implementation details and questions

Platform teams that need a wallet experience with explicit signing authority and custody responsibilities.

Build wallet interfaces and signing workflows around a defined custody and authority model. We address transaction preparation, policy approval, key-system integration and recovery responsibilities as separate engineering decisions.

  • Wallet interfaces within a business application
  • Policy-controlled transaction approvals
  • Custody-provider and signing-system integration
  1. Define custody and authority

    Map the account, key and recovery owners. Specify transaction policies, approval thresholds and the systems permitted to request a signature.

    A custody and signing responsibility model
  2. Prepare and approve

    Build clear transaction preparation and review screens. Integrate the agreed key or custody system without exposing secrets in the application interface.

    A reviewable transaction and approval trail
  3. Track and recover

    Reconcile submitted transactions and final status. Design handling for rejection, pending states and recovery under the chosen custody arrangement.

    Transaction status and recovery procedures

Application → transaction policy → authorized signing/key service → network submission → indexing and reconciliation. Custody responsibilities are not transferred implicitly by building an interface.

  • Custody and authority architecture
  • Wallet and transaction interfaces
  • Signing-policy and key-system integration
  • Recovery and reconciliation workflows

Decide who controls keys and approvals before designing the transaction experience. The interface must reflect those responsibilities.

  • Block Gemini is presented here as an engineering provider, not a licensed custodian or guarantor of asset recovery.
  • Supported networks, signing methods and recovery options depend on the selected providers and architecture.

Bring to discovery

  • Custody provider and authority decisions
  • Target networks and transaction types
  • Approval, recovery and operating requirements
Who holds the keys?

The custody design specifies that explicitly. Options depend on the operating business, selected providers and required controls; website examples do not decide custody.

Can we use an existing custody provider?

We assess its APIs, signing model, approval features and reconciliation support before defining the integration.