Repo Map
Tidecoin spans multiple repositories and local worktrees. Put changes where the owning code lives; do not mix node, docs, website, wallet, and library changes unless a coordinated feature truly requires it.
This page is an orientation map. Repository availability and maintainers can change, so verify ownership in GitHub before filing issues or opening PRs.
Core Repositories
| Repository or worktree | Purpose | Primary audience |
|---|---|---|
tidecoin | Core node, wallet, consensus, RPC, P2P, tests, release process | Node contributors, protocol reviewers, operators |
docs | Nextra documentation site | Users, operators, developers, integrators |
frontend-app | Marketing website / public site frontend | Website contributors |
tidecoin_website_content_plan | Website content planning source | Content maintainers |
rust-tidecoin | Rust transaction, script, and integration primitives | Rust integrators |
rust-yespower | Rust YespowerTIDE implementation | Miner/tooling developers |
tide-fn-dsa | Falcon/FN-DSA related Rust implementation | Crypto/library developers |
mobile-native | Mobile wallet code | Wallet developers |
extension | Browser extension wallet | Wallet and Web3 integration developers |
oldtidecoin | Legacy Tidecoin artifacts | Migration and historical reference |
tidecoin28x | Older node line / migration reference | Compatibility reviewers |
geoloop | Separate project tooling in the local tree | Do not assume docs ownership without checking |
Where Changes Belong
| Change | Put it in |
|---|---|
| Consensus, wallet RPC, P2P, AuxPoW, PQHD | tidecoin |
| User docs, protocol docs, integration docs | docs |
| Marketing copy, homepage, public site pages | frontend-app or website content plan |
| Rust transaction/library behavior | rust-tidecoin |
| Rust proof-of-work code | rust-yespower |
| Falcon/FN-DSA library work | tide-fn-dsa |
| Android/iOS wallet behavior | mobile-native |
| Browser extension behavior | extension |
| Legacy wallet or old-chain migration research | oldtidecoin, tidecoin28x, and docs |
Cross-Repo Rule
If a change touches more than one repository, write down the dependency order. For example:
- Core RPC behavior changes in
tidecoin. - Rust or wallet library support follows.
- Docs and website copy update after behavior is merged or release-bound.
Avoid documenting future behavior as live until the code and activation state are clear.
See also: Architecture, Build from Source, Contributing.
Last updated on