An experiment in funding open source with crypto
Some random crypto community folks created a Solana token for Desloppify. We didn't launch it, didn't ask for it, and don't control it. But they gave us ~7% of the supply plus the creator fees — roughly $7k at the time. So we're going to put it to good use.
The goal: build a flywheel where funds improve and market Desloppify, which grows the community, which grows the token, which creates more funds. 100% of everything goes back into the open source ecosystem. This isn't a profit play. It's an experiment.
Our goal is to build two reinforcing loops that both improve Desloppify and fund the open source ecosystem.
100% of token creator fees go toward bounties, challenges, and improvements that make Desloppify better. Better tool = more users = more attention = token demand grows = more fees. Repeat.
If the token hits $10M market cap, we begin selling off the 7% allocation. Every cent funds open source projects — AI credits, compute, infrastructure. All accounted for with invoices. Growth feeds funding feeds more growth.
Aside from using some resources to run these programs, I will not profit from this in any way. This is an experiment. It might not work. But if it does and we can fund something good from crypto — that'd be pretty cool, right?
We challenged people to find something genuinely poorly engineered in Desloppify's ~91k line, almost entirely AI-built codebase. We got 262 submissions and almost 50 that both Claude and GPT agreed were poorly engineered. We used these to improve both our process and our codebase.
Winner: @agustif
Found a circular dependency where base/ imported upward into
intelligence/, violating the project's own architecture contract.
$1,000 paid in SOL
Desloppify is an agent harness that refactors and improves code quality. We're reasonably confident it generally improves codebases — but we want to surface the cases where it genuinely makes something worse.
If Desloppify refactors your codebase and makes a demonstrably stupid decision — an abstraction that degrades readability, a change that introduces fragility, a refactor that makes the code harder to maintain — share your evidence and you could claim $1,000.
Requirements
Codebase must be 10k+ lines. Run with Claude 4.5/Sonnet 4.6 or GPT-5.3/5.4. Share your logs and code evidence. One submission per person. Deadline: March 21st 23:59:59 UTC.
$1,000 in SOL to the winner
6mjs2797K62H8vXWUkYikdkNiP3zsfmybC9Zq6z4pump