Block Gemini

Explore the connected ecosystem.

What can each participant see in a transfer?

Examine a reusable-container transfer as issuer, carrier and receiving verifier. Each role sees a different part of the same business event.

Scope my participant network

Interactive example · fictional records

Inspect a participant view

Transfer T-14 · Reusable containers

Packaging pool operator
Transport partner
Destination depot
Participant
Transport partner
Permitted action
Accept listed containers
Visible evidence
Dispatch reference and quantities
Carrier
Review decision

Record the carrier’s acknowledgement

The carrier checks the physical units and signs the handover. Commercial terms between the pool and the receiver stay outside its view.

Scope my participant network

What we can build with you

A multi-party transfer design with membership, signing authority, visibility rules and an agreed procedure for contested records.

Bring to discovery
Bring a sample transfer and a representative for each participating organisation to define the evidence they can share.
How to test the pilot
Run the same transfer under all three roles. Check signature visibility, access boundaries and the outcome when one party disputes the quantity.
Implementation details and questions

Enterprises and partner networks sharing transaction state without relying on one participant to own every record.

Design shared-ledger systems for organisations that need to coordinate records and transactions across boundaries. We scope participants, permissioning, network operations and integration with existing business systems before choosing a ledger architecture.

  • Cross-company procurement and transaction records
  • Partner networks with controlled participation
  • Shared records connected to enterprise platforms
  1. Agree the participants

    Map organisations, identities, permitted transactions and confidentiality boundaries. Specify how new participants join and existing access is removed.

    A participation and permission model
  2. Build the shared process

    Implement the agreed record and transaction rules with participant interfaces and enterprise-system adapters. Separate shared state from private business data.

    A working multi-party transaction flow
  3. Prepare network operations

    Define upgrade authority, node responsibilities, incident handling and recovery. Test the failure cases relevant to the chosen architecture.

    Network governance and operating procedures

Participant applications → permissioned identity → transaction/ledger services → private records and enterprise integrations. Network choice follows the governance and operating requirements.

  • Participant and governance model
  • Permissioned network architecture
  • Business-system and identity integration
  • Network operation and recovery design

Define who may participate, what they can see and how the network is governed before selecting the technology.

  • Permissioning does not remove key-management, confidentiality or operating responsibilities.
  • A shared ledger is not automatically the right answer; a central platform may meet the same need more simply.

Bring to discovery

  • Participant roles and trust requirements
  • Transaction rules and confidentiality needs
  • Identity, hosting and enterprise interfaces
Who operates the network?

The design specifies the organisations responsible for nodes, identity, updates and incident response. Operation is an agreed service responsibility.

Can different participants see different information?

The architecture can separate shared state, private data and role-specific interfaces. The exact privacy model is evaluated for the selected platform.