Dimension scores are derived from public data and fields; weighted into the composite. Reference only.
Credit Commons is a “recursive mutual-credit accounting” protocol designed to let independent organizations record exchanges on ledgers they control, while using nested ledgers to settle between different communities, business barter networks, or complementary currency systems. It explicitly does not use a blockchain model. Instead, each group self-hosts its own ledger, and ledger synchronization is verified through a hashchain formed by transaction jumps.
From a developer-tooling perspective, it provides an OpenAPI specification, a GPL reference implementation, and REST interfaces. The code is split across repositories such as cc-node, cc-lib, cc-server, and cc-client, and is managed with PHP composer. The reference implementation is based on PHP/MySQL, making it relatively easy to read and modify. The protocol supports custom accounting units, transaction workflows, credit limits, conversion rates, and risk management for each ledger, making it applicable to LETS, time banks, commercial barter, and complementary currency networks.
The reference implementation is marked as GPL, giving it a fairly open posture. Self-hosting is central to the design: each group can run and manage its own ledger, and in theory any software can implement the protocol and become a node. In terms of ecosystem, the documentation mentions long-running use of shared ledgers by networks such as Community Forge, CES, and CES Australia, as well as a complementary currency network of around 20K users using the reference implementation for transactions between local systems. This suggests it is not merely a theoretical project.
The website does not provide SaaS pricing, subscription plans, or payment methods. At the protocol level, nodes may charge fees for routed transactions or membership, but those fees are denominated in mutual credit rather than cash and are intended to cover governance and administration costs. The current reference implementation is explicitly described as a proof of concept and “does not claim to meet the usual security standards of financial software.” It is also seeking funding for a rewrite, so enterprise support, SLAs, and security/compliance capabilities should not be assumed.
Its strengths are a clear protocol concept, documentation that includes a white paper/FAQ/OpenAPI, and a strong emphasis on ledger autonomy and cross-network interconnection. Its weaknesses are limited engineering maturity, a relatively traditional PHP/MySQL stack, conservative security claims, and the need for each organization to handle governance and trade-balance issues itself. It is best suited to technical maintainers of complementary currencies, community economies, time banks, and business barter networks, as well as developers researching non-monetary settlement protocols. It is not a good fit for teams that need plug-and-play payments, fiat clearing and settlement, or financial-grade compliance.
The documentation does not provide information on access, payments, or localization for mainland China, so availability should be considered unknown. For deployment in China, organizations would likely need to self-host nodes and evaluate legal, tax, accounting, and network-reachability issues themselves. Comparable alternatives or adjacent directions include Ripple Interledger, conventional bank payment protocols, Holochain-style frameworks, or commercial barter platforms.
⚠ This review is compiled from public sources and does not constitute a purchase recommendation. Verify all facts on the vendor's official site. Verify on creditcommons.org official site.
creditcommons.org is an United Kingdom Crypto provider. TG4G tracks its product information, an overall rating of 7.0/10, and a China-accessibility score of Workable. Click "Visit Official Site" to reach creditcommons.org directly.