Canonical source: https://git.communitycoins.org/Communitycoins.Rooty/README/_edit/main//README.md
Mirrors (GitLab/GitHub) may be read-only and may lag behind.

🌐 CommunityCoins — Developer Navigation Hub

Welcome to git.communitycoins.org, the development hub for all CommunityCoins and Rooty software.

CommunityCoins/Rooty is a Federated Initiative of community coin teams. That means that it is created and maintained by groups of friends that work together to make something amazing happen: We put the power of Bitcoin in the hands of everybody in their own country and region. For people that Bitcoin would otherwise never reach.

This communitycoin hub/library operates on Forgejo, an open source Gitea fork. It serves to maintain and collect multiple projects that are releated to Communitycoins. Gitea itself has a specific organisation that should be uderstood for comfortable navigation. We explain it in CONTRIBUTING. We encourage each team that considers itself as a Communitycoins team to contribute to this library but at least to mirror this hub/library as a means toward federation.

👉 A community coin is a true cryptocurrency, that has its own globally accessable blockchain but with a local bias, community and identity.

This page provides a single-entry overview of all organisations, repositories, project boards, and development areas related to Communitycoins.

---

🧭 Main Areas (Organisations /org)

🔹 Rooty (Identity & Vision)

Since the mission of every community coin is to serve a much larger community beyond the team and early adopters, we consider ourselves grassroots initiatives. For this reason, we’ve chosen the name ROOTY as a project identity—or rather, as a badge of honor for Communitycoins.

Why Communitycoins Exists?

Global financial systems optimise for scale, efficiency, and abstraction. Local communities optimise for resilience, trust, and continuity. These two logics are not the same. CommunityCoins start from a simple observation:

Resilient systems are diverse systems.
Economic diversity — including local denominations, local governance, and local decision-making — is not a weakness. It is a prerequisite for sustainability.

CommunityCoins do not attempt to compete with global systems, such as Bitcoin or Fiat. They exists alongside them, where communities choose to organise value on their own terms.

Why Rooty Exists?

Since rooty is an alliance, it is:

• a shared framework, not a single currency
• a coordination layer, not a central authority
• a practice of decentralisation, not a marketing concept
• Each participating community coin remains autonomous, defines its own values and governance and operates its own infrastructure

Through endorsements Rooty provides:

• shared principles
• shared tooling where useful
• shared visibility

Rooty Current Main Utilities
➡ README introduction, documents, governance, narrative & branding
➡ Ring-Of-Trust-service, SPV alternative for communitycoins
➡ bitcoinjs-lib.3.3.2-pos, Javascript bitcoin utility functions
➡ cc-electrum-monitor, find available and responsive electrum servers
➡ cc-index, collection of communitycoin identities
➡ communitycoins.org-website Main website sources
➡ visuals, graphic identity

🔹 Communitycoins Core data

Central repository of Core blockchain and environmental data
➡ ecoincore
➡ https://ecoincore.com

🔹 Rings Of Trust / blockchain exposure

Corewallet daemons, Indexers, Electrum servers, API layers, monitoring, ...

In this organisation core-wallet-daemons are collected, enhanced with an SPV-service, to expose individual communitycoin blockchains to mobile wallets. The wallet sources are not mirrors of their original but forks of their status by the end of 2025. They will be patched to follow the Ubuntu two-yearly update cycle, starting with ubuntu 24. Finally they will be merged with the Ring-of-Trust source into a docker-image to provide a reproducible, self-contained runtime.

While not a fully static binary, this offers stronger practical portability and reproducibility by freezing the entire execution environment rather than relying on host OS libraries. Tags + releases are maintained in Forgejo as truth and the builds will be pushed elsewhere later.

➡ Rings-Of-Trust

🔹 Light client / Communitycoins Multicoin Wallet

➡ Communitycoins-wallet PWA (Progressive Web App)
➡ Communitycoins Moonshine fork

➡ Communitycoins-wallet Prototype

---

📌 Master Project Boards (Cross-Organisation Planning)

⭐ CommunityCoins Master Board

High-level governance & roadmap across ALL organisations
➡ Communitycoins Overall Coordination

📍 Release Roadmap

Coordinates multi-repo release planning
➡ Deplyment schedule of SPV services for all communitycoins

💬 Communications & Outreach Board

Public-facing progress & announcement planning
➡ Communitycoins master texts

---

🧑‍💻 Developer Onboarding

1. Join the organisation

Admins can add new developers via organisation settings. Anybody can join, create branches and submit issues.

2. Fork or mirror a repository

Each repo allows development workflows based on:

• branches
• pull requests
• CI via Forgejo Actions

3. Follow project boards

Global planning goes via the Master Board described above.
Project-specific tasks live in the organisation boards.

4. Coding Guidelines

• Open a PR/issue early
• Use feature branches
• CI must pass before merge
• Read CONTRIBUTING

---

⚙️ Technical Infrastructure

Forgejo instance and external mirrors (Gitlab / Github)

• https://git.communitycoins.org — self-hosted, decentralised
• https://gitlab.com/c4319 — Orginal collection

CI (Forgejo Actions)

Workflows defined in ...: