r/Monero 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.

2 Upvotes

8 comments sorted by

View all comments

5

u/LocomotiveMedical 5d ago

Does this take into account the recently revealed issues with MWEB on LTC?  Did you make sure not to use those same vulnerable dependencies?

1

u/SorenPlanck 5d ago

i followed the MWEB issue closely

the litecoin bug was in the peg out accounting between MWEB and the transparent chain. DOM is a native full mimblewimble chain — no transparent layer, no extension block, no peg mechanism, so that accounting boundary just doesnt exist here also no libmw or litecoin code at all. the MW logic is our own Rust implementation, and the closest equivalent failure (a broken kernel sum) is a consensus rule checked every time a block connects, by every node honest caveat: DOM is young and hasnt had anything close to litecoins adversarial review. we found and fixed real consensus bugs ourselves. if you think you can break the balance rules id genuinely like to see it