dedalo

Turn code merges into sustainable open-source funding.

Open source runs on work that nobody is paid for. Dedalo closes that gap inside the workflow that already exists: a merge into main is what earns, and the payout is computed from git history rather than typed into a dashboard.

git merges  ──▶  attribution  ──▶  payout plan  ──▶  settlement
(source of      (integer          (content-        (on-chain,
 truth)          weights)          addressed)       or simulated)

Everything up to settlement is pure and offline. The same repository and the same dedalo.toml produce the same plan id on any machine, so a plan whose id changed is a plan someone tampered with — and anyone can recompute a round and check the numbers.

What that buys a project

• Merge-to-Earn — merged code earns transparent, crypto-native rewards for whoever wrote it, co-authors included.
• Autonomous treasuries — a share of every round stays with the project, so its budget grows with its activity.
• Self-funding network — a protocol fee flows to the network's own collective. It is funded by the flow it enables, not by grants.
• CI/CD native — it runs in your pipeline. No third-party dashboard, no invoices.

→ dedalo-org.github.io · 📖 the handbook · 📦 docs.rs/dedalo

• dedalo — the protocol: attribution, payout plans, the hash-chained ledger, the claim contract, and the CLI and GitHub Action that drive them. Rust. Handbook · API reference.
• dedalo-nvim — attribution where the code is: who earns from the lines in front of you, and who wrote code the round would not pay. Lua.
• discussions — questions, ideas and announcements for the organisation.

On-chain settlement is not live. The vault's rules are pure Rust with a test per way it refuses, and the deployable that wraps them is unaudited and undeployed; Dedalo holds no signing key and never signs. See how funds move.

Read CONTRIBUTING.md for how work lands here, each repository's own guide for its build and test loop, and the handbook's development chapter for the three gates that catch people out. Questions belong in discussions; bugs with a reproduction belong in the issues of the repository they affect.

Security issues go through a private advisory on the repository concerned, never a public issue and never a discussion — see SECURITY.md.

→ opencollective.com/dedalo

Open Collective, because a project whose subject is transparent funding should be transparently funded: the ledger is public, and where the money went is a page anyone can read rather than a claim.

This is also where the protocol fee is designed to flow. Every round a project settles routes fees.protocol_bps — 2.5% by default — to this collective, which is what is meant by the network funding itself rather than depending on grants. Nothing flows there yet: on-chain settlement is not live.

Sponsoring is not the way to be paid by Dedalo. That is contributing — merged code is what earns, and it is the whole point.