For decades, DNS has been the internet’s central directory — but it’s centralized, traceable, and easily censored.
LHDNS (Ledger-based Hashed Decentralized Naming System) proposes a new architecture for anonymous, verifiable, decentralized name resolution, eliminating single points of control and global traceability.
⚙️ Technical Summary
- Ledger-backed ephemeral entries instead of static zones
- Cryptographic integrity: Ed25519 + SHA-256 + XChaCha20-Poly1305
- Privacy mechanisms: onion routing, cover traffic, multipath relays
- Sybil resistance: staking, slashing, and adaptive PoW
- Interoperability: DNS ↔ LHDNS gateways and stub resolvers
Each of these components is modular — nodes can enable privacy layers or staking mechanisms independently.
📂 Documentation
- 📘 Whitepaper (PDF)
- 🔍 Extended Technical Report (Annex A)
- 📑 Appendices A–D (Modules, Glossary, Threat Models)
💬 Contributing
LHDNS is open-source (Apache 2.0).
We welcome developers, cryptographers, and network researchers to:
- Review and discuss architectural modules
- Implement SDKs or prototype nodes
- Help define interoperability layers
If you’re passionate about decentralized infrastructure, we’d love your thoughts or code reviews.
See CONTRIBUTING.md for contribution details.
“Freedom begins when information flows without permission.”
— LHDNS Whitepaper, v1.0
Ahmad Hemmati, twincodesworld.com
💬 Join the Discussion on Hacker News
The LHDNS project has just been featured on Hacker News:
👉 Show HN: LHDNS — A Ledger-based, Privacy-Preserving Decentralized Naming System
Feedback, critique, and collaboration ideas are welcome — your insights can help shape a more private, decentralized internet.
Top comments (0)