HIDRANET AND HIDRAVPN DEV REPORT, OCTOBER 27 Repository: github.com/NeurexBK/HidraNet Highlight of the day: HidraVPN has a second exit, in the Netherlands The network now has two exits, in two countries and with two different providers, plus the entry. We set up the new server, published the official node list signed with it, and connected through the Netherlands for real. All of this is still testing: HidraVPN is not launched. Commits of the day 9d0f90f (PR 26) The Netherlands exit joins the official node list, signed offline. Along with it, we updated two libraries our automated audit flagged. 4 files, 23 lines added, 11 removed. github.com/NeurexBK/HidraNet… 1471bbf (PR 27) The guide for independent entry operators, and the node installer now takes the node's country and internal address range right at install time. 6 files, 449 lines added, 10 removed. github.com/NeurexBK/HidraNet… What we tested today 1. Buying passes with HNET inside the browser Our new developer's first piece of work passed its acceptance test on a real Windows PC, with a real payment on the Solana network. The payment was credited to the account, a repeated confirmation did not credit twice, the passes arrived and the VPN connected with them. We have already sent the developer the changes to tidy up the purchase screen, which go in before we merge the code. 2. Connecting through the Netherlands We connected through the new exit and checked it with a public leak test: IPv4 and IPv6 with a Dutch address, WebRTC clean and no leaks. Websites saw only the exit, never the PC. 3. Automated tests On GitHub, every check green on both PRs: Linux, Windows, the end to end test of who can see what, the anonymity checks and the dependency audit. The node installer got new tests for the country and the address range, with 48 checks passing. Where we moved forward A guide for operators We published the guide for anyone who wants to run a HidraVPN entry. It explains, with no fine print, what an entry does and does not do, what it costs, what the operator gets, and the setup step by step. The operator gets their name on their node and in the official list, a place among the Founding Operators on the site, 100 passes a month, their node monitored, stickers and a T shirt after three months and, for a company, its name as a network partner. Nothing financial. During the preview, independent operators run entries only, every candidate is checked first, and each operator can run at most two nodes. That way the network grows without anyone being able to fill the list alone. Network monitoring, in final review We are finishing an automated hourly check of the whole network: every node in the list, the signatures of the list and of the release manifest, the pass issuer and whether passes are on sale, and the expiry dates two weeks ahead. Any problem becomes an email alert, and the alert closes itself when the problem is gone. It runs outside our servers, so it keeps working even if one of them goes down. It has 72 automated tests and is going through an independent review before it goes into main. Next days Operator recruitment opens as soon as the monitoring is live. The guide promises that we tell an operator when their node goes down, and we only promise what already works. What is still left 1. Put the monitoring live and open recruitment for entry operators. 2. Merge buying passes with HNET in the browser, with the developer's changes. 3. Sign and publish HidraVPN 0.1.1. 4. Code signing for the Windows programs. 5. The new browser release with the VPN page, which is the launch.

👀👀👀

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.

Heads-up before we move anything: we're transferring 0.5% of supply (about 4.79M HNET) from the team wallet to our @fomo account. @fomo requires it to give the HidraNet profile a team tag. The tokens stay there untouched and won't be sold. Addresses below.