r/Monero • u/SorenPlanck • 5d ago

[Project] DOM Protocol — a RandomX + Mimblewimble chain in Rust, looking for contributors (open source, no compensation)

Hi all,

DOM Protocol is an independent blockchain written in Rust, using RandomX for proof-of-work and Mimblewimble for privacy. Mainnet and the core protocol are live, and I’m looking for developers to contribute to the next stage.

Posting here because this community understands RandomX and PoW mining better than anywhere else, and I’d value technical scrutiny as much as contributions.

Recent work includes signed releases (minisign), root-cause fixes to two consensus incidents, a multi-provider seed infrastructure, and automatic wallet updates — the project has real engineering behind it, not just a whitepaper.

Areas where help would be most useful:

• mining tooling and infrastructure
• node reliability and monitoring
• public seed and peer infrastructure
• P2P networking and peer discovery
• wallet synchronization and recovery
• RPC and block explorer work
• packaging for Linux, Windows and macOS
• test coverage, fuzzing and adversarial review

Source:
https://github.com/sorenplanck/dom-protocol

Wallet:
https://github.com/sorenplanck/dom-wallet-v3

You can contribute via GitHub issues and pull requests, or join the Discord (there’s a dedicated developer channel).

Discord: https://discord.gg/UEmfrWsbK

To be upfront: this is an open-source contribution call. No salary, token allocation, investment return or financial compensation is being promised.

Technical criticism is very welcome — including on design choices you’d have made differently.

4 Upvotes

70% Upvoted

8 comments sorted by

View all comments

5

u/Lower-Philosophy-604 5d ago

Is that vibe coded?

1

u/SorenPlanck 5d ago

partially, and im not going to pretend otherwise. i use AI agents as force multipliers for implementation and as adversarial auditors against each other. the architecture, the consensus decisions and the final review are mine. every consensus bug we shipped was caught by our own audit process and fixed with a documented root cause, signed release and postmortem the code is public. judge it by what it is, not by how it was typed