Crypto Hunter

HIDRAVPN AND HIDRANET: DEV UPDATE - 29 out We closed the last stretch before the HidraVPN launch. HidraVPN 0.1.2 and HidraNet Browser 1.1.0 are ready, and they will be published together on launch day. Review before launch We reviewed the code of HidraVPN, the browser and the nodes from end to end. The nodes already run the improvements; those in HidraVPN and the browser arrive with the new versions, each covered by tests. HidraVPN 0.1.2 • The installer checks each release more strictly before it installs it. • A stricter kill switch, on Windows and Linux. • More privacy in private mode (two hops). In 0.1.2, passes are bought and topped up only while disconnected or in fast mode. Tip: get your passes before you connect in private mode. • More protections in the VPN service. The nodes The three official nodes, helsinki-1, amsterdam-1 and entrada-1, already run the new node code and passed real connection tests, in fast and in private mode. The pass issuer Tomorrow the pass issuer moves to a new server, with a short pause in pass purchases. The move fixes a problem that exists today: anyone connected in fast mode through one of the nodes cannot top up their passes. HidraNet Browser 1.1.0 • Packages rebuilt from scratch and checked file by file before they go out. • From launch day, the checksum list is signed, so you can check your download. • The browser now tells you when a new version is out, and that check also goes over Tor. 1.0.0 has no such notice: when 1.1.0 is out, download it from hidranet.org. • More security and privacy protections while you browse. • We dry-ran the build of the 1.1.0 packages and fixed what the dry run found in the scripts. On the site • A new HidraVPN page: hidranet.org/vpn • A code signing policy page, which the SignPath Foundation requires to sign HidraVPN's Windows programs. Signing is still being set up. • The homepage and the privacy policy were corrected to say what the product really does and what browsing uses. Next Switch the pass issuer tomorrow, then publish HidraVPN 0.1.2 together with HidraNet Browser 1.1.0. We are still looking for independent entry operators: with the entry and the exit in different hands, no one sees both ends of a connection. Contact: [email protected] Open source on GitHub: github.com/NeurexBK/HidraNet

Thanks to everyone who joined the Space today. A privacy project doesn't grow on ads. It grows on people who ask, push and check the work. That's exactly what you did today. HidraNet is yours too.

A note to the HidraNet community on today's Railway news. Short version: HidraNet does not use Railway. Nothing in our browser, our network or the $HNET token depends on it. Details below.

A VPN company sees who you are and where you go. In HidraNet, one relay knows you, another knows where you're going, and none knows both. One minute on how it works.

Our whitepaper had a line I didn't like writing: in our network, all 3 relays in a circuit could see your IP. Fixed it this week. Now you only talk to the first relay and go through it to the next, new key every hop. Wrote a test that breaks if that ever changes. Next release.