Fully decentralized, zero-backend git hosting and collaboration, built directly on Dash Platform.
Dash Forge is a suite of tools that together provide a GitHub-class experience — repositories, pushes/clones, branches, issues, pull requests, releases, CI hooks — with no servers anywhere. Dash Platform is the sole source of truth (refs, manifests, collaboration docs, token-based access control); pack data lives on Platform by default, or on cheaper hash-verified backends (IPFS / S3 / HTTPS / mirror git hosts) for fee reduction. Original design brief: ../INIT.md; reconciliation notes: docs/init-reconciliation.md.
| Component | What it is |
|---|---|
| forge protocol | Data contracts: one global registry + a per-repo contract template with WRITE/MAINTAIN token ACLs enforced at consensus. |
| git-remote-dash | Git remote helper (Rust). git clone dash://alice/project and git push just work. jj-compatible. |
| dg | gh-replacement CLI (Rust, same workspace): repos, issues, PRs, releases, collaborator token management, cost audit, repack. |
| forge web | Static SPA (TypeScript, wasm SDK, in-browser repo materialization) deployable to IPFS — full GitHub-replacement browsing and review UX. |
| forge relay | Stateless, interchangeable Rust daemon bridging Platform events to GitHub-shaped webhooks (CI/notifications). Trust = availability only. |
| forge import | One-command GitHub migration (code, issues, PRs, releases) with cost gating and author claim flow. |
- Platform constraints & research findings — verified limits/fees that shape the design.
- INIT.md reconciliation — what was adopted from the original brief; constraint-forced deviations, flagged for review.
- System architecture — components, contract topology, token ACL, storage backends, data flows, economics.
- Data contracts design — registry + repo-template schemas, token costs, indices.
- PRDs:
- Economics & fee minimization — compression pipeline, deposit-vs-burn cost model, repack/refund GC.
- Style guide — visual system + engineering conventions.
- Implementation plan — Phase 0 de-risk gate → mainnet protocol → CLI+relay → web+import → hardening.
- E2E & production test plan — testnet identities/funds via bridge.thepasta.org + faucet.thepasta.org; mainnet smoke.
- Spike results & Design Freeze #1 — the 9 de-risking spikes (GO verdict).
- Design Freeze #2 (as-built) — what implementation established: deviations, discoveries, final decisions.
- Mainnet runbook — the rehearsed (not-yet-executed) mainnet deployment procedure.
Built and testnet-complete. All components are implemented, live-tested against Dash Platform testnet, and independently code-reviewed. The web app is live at https://pastapastapasta.github.io/dash-forge/. See EXECUTION.md for the build log, design-freeze-2.md for as-built decisions, and mainnet-runbook.md for the (rehearsed, not-yet-executed) mainnet deployment.
Proven end-to-end on testnet: git clone dash://… / git push byte-identical round-trip; frozen-collaborator push rejected at consensus; third-party "no trust in any server" verification; browser app rendering live proof-verified data with the trust panel; CLI↔web parity via 66 shared conformance vectors.
Components (all under this repo): forge-contracts · forge-core (Rust lib) · git-remote-dash · dg (CLI) · forge-relay · forge-import · forge-web. Verification: e2e/cli/ (CLI suite) + forge-web/e2e/ (Playwright).
../INIT.md— original design path & PRDs (authoritative product intent).../platform— Dash Platform monorepo (source of all cited limits/fees).../yappr— reference zero-backend Platform app (SDK/auth/write patterns to reuse).../mainnet-bridge/../platform-identity-faucet— bridge.thepasta.org and faucet.thepasta.org sources (identity/funding for users and e2e tests).