Rush Browser

Decentralized Browsing, Redefined. Native HNS & ENS Support. DANE Security. On-Chain IPFS & Redirects, No DNS Needed.

[Rush Browser @RushBrowser]

🧵Most people assume:

“If a Handshake name works in https://, that means it’s legit.”

But this is a misunderstanding of how the web works.

HTTPS was built inside the ICANN DNS world not for decentralized roots like Handshake.

Let’s break it down. 👇

[Rush Browser @RushBrowser]

@anewformofmusic 😍

[erwin.groen/ @OwnTheDot]

Handshake Australia would like to acknowledge the builders/creators/founders of this protocol in help by celebrating 6 years of the Handshake protocol running…

Also a massive thanks for the backers/supporters/namers in believing in its future!

From me and the team at hnsAU..

Happy 6th birthday 🎊
#hns #handshake $hns #web3 #digitalidentity #ownthedot

[Rush Browser @RushBrowser]

@HNS_token @rahulsutariya Yes it will be there.

[Godfather.tao @rahulsutariya]

RUSH + IPFS = Hassle-free Web Builder for $HNS TLD Owners

Build and go live in 1-2-3.

No need for NB or SS.
No nameserver changes.
A TXT record on-chain → your website is live.

Decentralized. Simple. Ownership-first.
Built for the $HNS - powered by @RushBrowser

[Rush Browser @RushBrowser]

@Mayaank_Roy 😔

[Rush Browser @RushBrowser]

Upcoming Release 2.3 – @RushBrowser

We may integrate the BOB wallet extension directly into Rush, since Chrome no longer supports it - bringing a full HNS wallet natively into the browser.

2.3 is currently in testing, and if all goes well, we may launch it asap.

[Rush Browser @RushBrowser]

If the Handshake wants long-term independence, collision-freedom, and native identity, then giving it its own protocol is the natural direction. 🤝

[Rush Browser @RushBrowser]

🧵Most people assume:

“If a Handshake name works in https://, that means it’s legit.”

But this is a misunderstanding of how the web works.

HTTPS was built inside the ICANN DNS world not for decentralized roots like Handshake.

Let’s break it down. 👇

[Rush Browser @RushBrowser]

hns:// gives Handshake what HTTPS never can:

Native verification

DANE trust without CAs

Zero name collision risk

Direct resolution without DNS hijacking

A protocol identity of its own

This is how Handshake becomes Handshake, not “alternative DNS inside ICANN’s rules.”

[Rush Browser @RushBrowser]

Donors, drop your Web3 domains below - whether they have an active redirect or are fully live sites.

We’ll be adding them all to the app! 🤝

[Rush Browser @RushBrowser]

@bankrolls_eth @namehunter_eth It’s meaningful because open-sourcing builds trust in Web3 and invites more devs to contribute, improve features, and add ENS/HNS integrations.

$2k is just a community signal. Plus, we promote all donors in-app and honor them on our official donors page.🤝

[Rush Browser @RushBrowser]

Thank you @namehunter_eth for the $100 donation toward our open-source goal and for supporting the ongoing development. 🤝

[Rush Browser @RushBrowser]

Rush 2.2 has a Home button (keeps reloading) bug and a Bookmarks (clear all) bug, and these issues affect overall smooth performance.

A fixed stable build drops in 1 hour - avoid downloading until then.

[Rush Browser @RushBrowser]

🙏 Support the project: https://t.co/TX9FcAQspU

Just $1,420 left until we can open-source Rush Browser.
And remember - at $200 donation, We’ll build your own custom 2.2 browser, white-labeled with your brand. 🤝

[Rush Browser @RushBrowser]

Rush Browser v2.2 is now live!
Please consider donating to support development →
https://t.co/N4GnjbNjWK

Only $1,420 left before we can open-source Rush!

💡 Donate $200+ and get your own custom browser based on v2.2 - your name, your logo, no Rush branding.

Fully yours!

[Rush Browser @RushBrowser]

⚡ Performance Boost

Rush 2.2 is faster - improved DNS handling, better DANE caching, quicker tab switching, and optimized internal pages.

🐞 Stability Fixes Everywhere

A large set of bug fixes and behavior improvements make this the most stable Rush version yet!