Ownership and governance¶
DPG Standard, indicator 3 — Clear ownership.
Who owns the work¶
CBWeb3 is an IDB Lab project, hosted as a lab of LF Decentralized Trust (LFDT, a
Linux Foundation project). Copyright in the software and documentation is held
collectively by the contributors, stated in the repository as
Copyright 2025-2026 The CBWeb3 Authors in
NOTICE,
and licensed to everyone under Apache-2.0.
There is no separate proprietary owner, no dual-licensed edition and no
contributor licence agreement that assigns rights to a company. Contributions are
accepted under the Developer Certificate of Origin: every commit carries a
Signed-off-by line by which the author certifies they have the right to submit the work
under the project's licence. The canonical repository is
LF-Decentralized-Trust-labs/cbweb3;
anything published elsewhere is a copy.
Individual contributors retain copyright in their own contributions. Where a component
was developed under contract, copyright in that work vests with the contracting
institution and is contributed to the project under the same Apache-2.0 terms. This is
visible in the repository rather than hidden: the platform subtree carries
Copyright 2026 LACNet Networks in
platform/LICENSE,
because LACNet Networks commissioned and holds copyright in that work and contributed it
here under Apache-2.0. Two copyright holders in one repository is the normal shape of a
collaborative open-source project; the licence granted to everyone downstream is the same
Apache-2.0 in both cases. The provenance of every line is traceable in the Git history,
which was preserved commit by commit when the platform was imported.
Trademarks. No trademark is registered for "CBWeb3" at present. Use of any Linux Foundation or LF Decentralized Trust mark is governed by the Linux Foundation trademark usage policy.
Who decides¶
Ownership of the code is collective; authority over the project is exercised by the
DPG Working Group, whose rules are public in
CONTRIBUTING.md.
| Role | Held by | Authority |
|---|---|---|
| Maintainer Core | LNet technical lead and LFDT approvers | Merge pull requests, enforce the workflow |
| Cochairs | Nominees of CEMLA and FLAR | Facilitate meetings, curate the backlog |
| Contributors | Any individual or organisation | File issues, submit and review pull requests |
Decisions are consensus-first. If consensus is not reached within five business days,
a vote is triggered: quorum is 50% + 1 of contributors with a merged pull request in the
previous 15 days, one vote per GitHub handle, simple majority, tallied publicly by the
vote bot on the issue. The current holders of each role are listed in
MAINTAINERS.md,
which is itself changed only by pull request approved by the existing Maintainer Core.
Deliberation happens in the open: bi-weekly technical syncs on the LFDT Zoom calendar,
GitHub issues and
discussions, and the
#cbweb3 channel on the LFDT Discord.
Institutional roles¶
| Organisation | Role |
|---|---|
| IDB Lab | Project sponsor |
| LNet | Infrastructure and technical coordination |
| CEMLA | Regional monetary advisory, working group co-chair |
| FLAR | Regional financial advisory, working group co-chair |
| LACChain | Blockchain infrastructure (operated by LACNet) |
| LF Decentralized Trust | Neutral open-source host and governance |
Sponsorship does not confer control. No sponsoring or advisory institution holds a veto over the technical direction of the project outside the working-group process described above.