🚀 **The VeilRoot Browser is coming.** 😉 A privacy-first browser built to natively understand double-dotted VNS domains like: **`welcome..net`** No manual onion addresses. No separate Tor configuration. No centralized DNS dependency. The VeilRoot Browser is being built to resolve VNS names through the VeilRoot network and transparently route the resulting hidden services through Tor, while keeping the VNS address visible in the browser. This is more than a browser skin — it’s the first step toward a web where decentralized names and privacy-preserving services work together natively. 🔐 VNS 🧅 Tor 🌐 Nostr ⚡ VeilRoot Soon: browse the VeilRoot network using names, not addresses. #VeilRoot #VNS #Nostr #Tor #Privacy #DecentralizedWeb #Web3

Why is #VeilRoot exciting when there are already projects like Unstoppable Domains? Because we’re not just trying to give you another fancy domain name. Think about today’s internet: You type a name → DNS finds an address → you connect to a server. The problem is that the naming layer is mostly controlled by centralized infrastructure. Projects like Unstoppable Domains take an important step by putting names on a blockchain. That’s useful — but VeilRoot is taking the idea further. With VeilRoot, a name can become more than an identity. It can become a "verified way to find and connect to a service". For example: `welcome..net` can point to a service without relying on traditional DNS. The VeilRoot network can verify: 🔐 Who controls the name 🧾 What was actually registered on-chain 🌳 That the service information is cryptographically linked to that registration ✍️ That the service information was signed by the legitimate owner 🌐 And it can use decentralized infrastructure such as Nostr and Tor to actually reach the service So instead of: “This is a blockchain domain.” the goal is closer to: “This name is a verifiable doorway to a service.” And that opens up a much bigger possibility. 😊 Imagine a future where you don't need to know an IP address, don't need traditional DNS, and don't need to trust some centralized directory just to discover where a service lives. You simply enter: [ name..extension ] …and #VeilRoot figures out the rest, while the cryptographic proofs stay underneath. That's the part we're building toward. Not another domain-name marketplace. A different way for services to exist on the Internet. 👀

VeilRoot end-to-end resolution now works. 🥳 [welcome..net] is now registered on the VeilRoot VNS blockchain as a double-dotted domain, its authenticated service descriptor is published via Nostr, and the dedicated VNS Browser loads the site over Tor while keeping [welcome..net] in the address bar. No ordinary DNS. No ICANN namespace. No clearnet fallback. 😉 In the screenshot: the first VNS double-dotted domain resolving a webpage hosted on a .onion address. 😁 The dedicated VNS Browser is still in private development, but the full path now works: VNS double-dotted name → authenticated VeilRoot resolution → Nostr service descriptor → Tor onion service → page loaded as welcome..net #VeilRoot #VNS #Nostr #Tor #privacy #decentralizedweb

🚀 VeilRoot latest release is out (v0.26.2.2) A major core hardening update is now deployed across the VeilRoot network. This release strengthens the foundations of **VNS + Nostr** with: 🔐 Full Nostr **BIP340 signature verification** 🆔 **NIP-01 event ID verification** 🔑 Strict registrant-key authentication 🌐 Multi-relay VNS service descriptor validation 💓 Cryptographically validated VNS heartbeats 🌳 Registration transaction **Merkle-proof verification** ⚔️ Protection against conflicting service descriptors 🛡️ Additional Merkle proof bounds and malformed-input protections 🗄️ Legacy VNS database compatibility preserved The complete VNS flow has been tested successfully: **registration → heartbeat → descriptor publication → domain resolution** The VNS/Nostr test suite is passing **7/7**. This release is an important step toward the next stage of VeilRoot development, with the **VeilRoot Browser** coming next. 🔗 GitHub:

GitHub

Release VeilRoot v0.26.2.2 · ailerov/VeilRoot

VeilRoot Core — VNS/Nostr Protocol Hardening This release completes a major hardening pass over the VeilRoot Naming Service (VNS), Nostr service ...

#VeilRoot #VNS #Nostr #Privacy #Decentralization #Monero

#VeilRoot it's a bigger deal than people realize. With traditional DNS, when you update a record, you wait. Sometimes hours. Sometimes days. It propagates through a hierarchy of caching servers, each with its own TTL (Time to Live) settings. You're essentially waiting for the entire internet to forget the old record and learn the new one. It's slow, unpredictable, and you have zero control over it. With VeilRoot, there is no propagation delay. No hierarchy. No caching layers. The blockchain is the source of truth. The domain record exists on-chain and is immediately visible to anyone querying it directly. No waiting for nameservers to sync. No "48-72 hours" nonsense. If you update your domain's associated relays or service descriptors through Nostr, that change is available the moment the event is published. The resolver queries the blockchain, then the relay, and gets the freshest data right then. That's the beauty of cutting out the middlemen. Traditional DNS has you waiting on a global network of caching servers. VeilRoot has you waiting on nothing. It also means no central authority can pull the plug on your domain through some back-channel request. There's no registrar to call. No upstream provider to pressure. Your domain lives as long as your relays keep proving it's alive. Privacy, speed, control. That's the package. #DNS #privacy #domain

v0.26.2.1 is out — a hotfix for the chain-sync crash that snuck into the previous release. If you hit a sync failure after upgrading to .2.0, this should get you moving again.

GitHub

Release VeilRoot v0.26.2.1 · ailerov/VeilRoot

VeilRoot v0.26.2.1 Release Notes This patch fixes critical issues discovered after the v0.26.2.0 release, specifically around VNS domain transactio...

#VeilRoot #VNS #Nostr #privacy #decentralization #opensource #Monero