Skip to content
LF-Decentralized-Trust-labsPublic

About

CBWeb3 — cross-border payments with CBDC settlement (PvP/HTLC and AMM scenarios). An LF Decentralized Trust lab.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

8 stars

Watchers

1 watching

Forks

CBWeb3

License Toolbox CI

CBWeb3 is an IDB Lab project that seeks to enable a regional test-network (Test Net) for Latin America and the Caribbean that will allow for the issuance of tCeBM (tokenized Central Bank Money) and the tokenization of financial assets, with a focus on cross-regional interoperability between central banks and financial institutions.

The Test Net will build upon the technological capabilities and infrastructure of IDB Lab's initiative LNet — the Alliance for the Development of the Blockchain Ecosystem in Latin America and the Caribbean.


How it works

CBWeb3 connects domestic central bank networks through a shared transnational hub, enabling three types of transactions:

CBWeb3 Transaction Types

Transaction Description
Domestic issuance & redemption A central bank issues or redeems tCeBM within its own network
Enhanced Correspondent Banking Two parties settle a cross-border payment atomically using Hash Time-Lock Contracts (HTLC)
Automated Market Maker (AMM) Commercial banks exchange currencies through a shared liquidity pool on the transnational hub

Enhanced Correspondent Banking (PvP with HTLC)

The primary settlement flow — a bilateral Payment-versus-Payment using HTLC across two domestic networks:

Enhanced Correspondent Banking flow

  1. Commercial Bank A proposes an FX agreement to Correspondent Bank D
  2. Correspondent Bank D accepts the agreement
  3. Central Bank A issues tCeBM-A to Commercial Bank A
  4. Central Bank B issues tCeBM-B to Commercial Bank B
  5. HTLC locks tCeBM-A on Network A
  6. tCeBM-A is transferred to Correspondent Bank C
  7. tCeBM-B is transferred to Commercial Bank A — settlement complete

Automated Market Maker (AMM)

A hub-based liquidity pool for multi-currency exchange:

AMM flow

Commercial banks bridge tCeBM to the transnational network, where an AMM contract determines exchange rates algorithmically and executes swaps atomically.


Architecture

The platform uses a Hub & Spoke topology: each country operates a domestic Besu network (Spoke), connected through a shared transnational settlement layer (Hub) via Hyperledger Cacti.

CBWeb3 System Component Architecture

Layer Key components
Frontend Treasury Portal, NOC Portal, Supervisor Portal, Governance Portal, Bank Integration Portal
API REST Gateway (OpenAPI 3.0.3)
Microservices Policy Engine, Identity Service, Privacy Service, Time Service, Observability Hub
Blockchain Hyperledger Besu (QBFT consensus, gasless), Hyperledger Paladin (ZK-SNARKs privacy via Zeto tokens), Cacti (cross-chain relay)
Smart contracts HTLC, LP/AMM Pool, FX Oracle, Atomicity Coordinator

What's in this repository

This repository is the coordination hub for the CBWeb3 DPG Working Group. It contains documentation, governance artifacts, and the Toolbox — a shared integration kit for implementers and contributors.

cbweb3/
├── Toolbox/              Integration kit: contracts, mocks, test vectors,
│                         conformance tests, sandbox tutorials
├── docs/                 DPG assessment, research papers, technical blueprint,
│                         published documentation site
├── CONTRIBUTING.md       Governance model, roles, decision-making process
├── MAINTAINERS.md        Who maintains what
├── SECURITY.md           How to report a vulnerability
├── AGENTS.md             Conventions for AI coding tools
├── CHANGELOG.md          Notable changes
└── README.md             This file

The full CBWeb3 platform (microservices, smart contracts, frontend portals) is developed by AguilaHub / GoLedger under contract with IDB Lab, delivered as milestones D1–D7. This repository documents the interfaces and provides tooling for the community to build on top of that platform.

The Toolbox

The Toolbox is a curated set of integration-ready artifacts that help implementers build, test, and validate CBWeb3-compatible systems:

Artifact What it provides Status
Interface contracts OpenAPI 3.0.3 specs mirroring API Gateway v2.3.0: auth/ shared (8 paths), pvp/ Scenario A (28 paths), amm/ Scenario B (52 paths) — 88 paths / 99 operations Available
Reference mocks Canonical request/response fixtures for both settlement flows (59 fixtures across auth/, pvp/, amm/) Available
Test vectors Deterministic input/output fixtures (140 vectors in 9 files) Available
Conformance tests Executable compliance checks against a mock or a live gateway (91 test methods) Available
Sandbox & tutorials Quick-start guides, mock server setup, and three step-by-step tutorials (Scenario A, conformance, Scenario B) Available

Community Backlog

The Toolbox Backlog tracks modules and tools that the community is invited to develop:

Issue Module Category
#28 CCIP Integration Adapter Interoperability
#29 Fabric-X Corridor Kit Interoperability
#30 Paladin Privacy Conformance Suite Privacy & Compliance
#31 Policy-as-Code Starter Pack Privacy & Compliance
#32 Gasless Anti-Spam Controller Ops & Reliability
#33 Observability Pack (NOC-in-a-box) Ops & Reliability
#34 Secure Dev & Supply Chain Templates Security
#35 Permissioning / Allowlisting Module Security
#36 Community-built SDK Interoperability

Getting started

Run the PvP tutorial (15 min) — Execute a full cross-border settlement against a mock server:

Toolbox/sandbox/tutorials/01-pvp-settlement-mock.md

Validate an implementation — Run conformance tests against your own API:

Toolbox/sandbox/tutorials/02-validate-implementation.md

Contribute to the backlog — Pick an issue from the Toolbox Backlog and follow the contribution guide.

Explore the research — Read the DPG assessment, the Privacy vs Confidentiality analysis, or the governance, privacy, and interoperability research papers in docs/research-papers/.


CBWeb3 as a DPG

CBWeb3 is a candidate Digital Public Good. The public evidence for each of the nine indicators of the DPG Standard is published as part of this repository:

Indicator Evidence
Relevance to the SDGs SDG alignment — targets 10.c, 8.10, 9.1, 17.6/17.16
Approved open licence Apache-2.0 (LICENSE, NOTICE), SPDX headers enforced in CI
Clear ownership Ownership and governance
Platform independence Platform independence — no mandatory proprietary dependency
Documentation Documentation map
Extracting data Data export — Ethereum JSON-RPC, OpenAPI/JSON, SQL
Privacy and applicable laws Privacy notice
Standards and best practices Open standards
Do no harm by design Do no harm

Start at the DPG Standard compliance overview. The earlier gap assessment that set this work in motion is kept for the record.

The DPG Working Group stewards design decisions, accepts community RFCs and pull requests, and publishes materials so that any competent team can deploy, operate and extend the system.


Governance

CBWeb3 is governed by a DPG Working Group (DPG WG) with open participation:

Role Who Responsibilities
Maintainer Core LNet technical lead + LFDT approvers Merge PRs, enforce workflow
Cochair CEMLA / FLAR nominees Facilitate meetings, curate backlog
Contributor Any individual or organization File issues, submit PRs, review code

Decisions follow a consensus-first model with a GitVote fallback (50%+1 quorum, simple majority).

See the full participation guidelines for details on roles, voting, and the decision-making process, and MAINTAINERS.md for who currently holds each role.

Join us


Partners

Organization Role
IDB Lab Project sponsor
LNet Infrastructure and technical coordination
CEMLA Regional monetary advisory, WG co-chair
FLAR Regional financial advisory, WG co-chair
LACChain Blockchain infrastructure (LACNet)
LFDT Open-source governance (Linux Foundation)
AguilaHub / GoLedger Core platform development (D1–D7)

Security

Found a vulnerability? Do not open a public issue. Report it through GitHub private vulnerability reporting. See SECURITY.md for scope, response targets, and the coordinated disclosure policy.


License

Apache-2.0 — see NOTICE for attribution.

Contributions require a DCO sign-off (git commit -s). If you used AI assistance, disclose it with an Assisted-by: trailer — see AGENTS.md.


Glossary

Term Definition
tCeBM Tokenized Central Bank Money — digital representation of central bank currency on a blockchain
PvP Payment-versus-Payment — simultaneous exchange of two currencies to eliminate settlement risk
HTLC Hash Time-Lock Contract — smart contract that enables atomic swaps using cryptographic hash locks and time limits
AMM Automated Market Maker — algorithm that provides liquidity and determines exchange rates via a mathematical formula
DPG Digital Public Good — open-source software that contributes to the UN Sustainable Development Goals
Spoke A domestic blockchain network operated by a single country's central bank
Hub The shared transnational settlement network connecting all Spokes
CEMLA Center for Latin American Monetary Studies
FLAR Latin American Reserve Fund
LNet Alliance for the Development of the Blockchain Ecosystem in Latin America and the Caribbean
LFDT Linux Foundation Decentralized Trust (formerly Hyperledger Foundation)

About

CBWeb3 — cross-border payments with CBDC settlement (PvP/HTLC and AMM scenarios). An LF Decentralized Trust lab.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

8 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages