Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.keystoneos.xyz/llms.txt

Use this file to discover all available pages before exploring further.

KeyStone coordinates bilateral atomic settlement between institutions on different platforms and chains using on-chain smart contracts.

​
The settlement lifecycle

Every settlement follows this pattern:
  1. Instruct - Both counterparties submit instructions via the API. KeyStone matches them and creates a settlement on-chain.
  2. Comply - KeyStone screens parties off-chain (LSEG, CipherOwl) and attests results to the ComplianceRegistry on-chain.
  3. Deposit - Parties deposit their assets directly to the escrow contract. KeyStone is not involved.
  4. Execute - The escrow detects all deposits complete, notifies the coordinator, and the coordinator calls executeSettlement with recipient addresses (revealed only at execution time). Fully autonomous.
  5. Finalize - Assets are delivered to counterparties. Both platforms receive confirmation via webhooks.
After compliance clears, the contracts are autonomous. KeyStone’s only remaining role is monitoring events and dispatching webhooks - a convenience, not a requirement.

​
Building blocks

Settlements

The core transaction object, created on-chain via the SettlementCoordinator.

Templates

Reusable workflow definitions that control the state machine.

State Machine

Contract-enforced transitions with compliance and deposit gates.

Parties and Legs

Who is involved and what obligations they have.

Compliance

Off-chain screening, on-chain attestation, contract-enforced gate.

Cross-Platform

Bilateral instruction matching across platforms.

Tokenised Repo

Two linked DvP settlements for repurchase agreements.