-
-
Notifications
You must be signed in to change notification settings - Fork 37
Open
Description
First what I want to say to you is that I am not a network/cybersecurity engineer so I can be wrong somewhere.
I looked a bit deeper into how actually that thing works.
And some of my concerns are shown below.
- This is a really hard task to do, implementing all those hard algorithms that betanet expects the developer to make. For example even something as simple as routing through the nodes (basically core of the project) may take many, many hours to implement.
- While there are enthusiasts who will make their projects on that new "global web" in sign of protest - the amount of nodes in the very beginning will be miserable which means the speed will be pathetic, and most people would not use apps that use betanet. (Which as mentioned should be unnoticeable, but idk how we will achieve that at the beginning)
So what are your guys thoughts on that? Will this be the real "new net" or just another hype drop that will fail time pressure test? Share your thoughts in the comments please!
Heliodex
Activity
eemmmmg commentedon Aug 12, 2025
If by net you mean Internet, then no, it is nowhere close to that, as it just uses the existing Internet in its entirety. It is just a shittier version of I2P (for example) as the mixnet routing in Betanet is "optional" and with some "ecash" token for "staking" (staking is just whoever has the most money decides the rules). It is really closer to an alternative/reimagining of HTTP/S
Queen12s commentedon Aug 12, 2025
this is worse than https to be honest
NeKon69 commentedon Aug 12, 2025
Isn't it like independent? I thought the only thing it relies on is physical infrastructure
eemmmmg commentedon Aug 12, 2025
The physical infrastructure, all being connected (and communicating with TCP/IP), IS the Internet.
This is literally, at best, a shitty alternative to I2P, and at worst just an alternative to HTTP/S; you could make an argument for being a replacement for the World Wide Web, but certainly not the Internet.
thivisthiv commentedon Aug 12, 2025
I saw the video for this new "internet" pitch, I think K0 is confusing World Wide Web with the Internet, Both are different things.
Queen12s commentedon Aug 12, 2025
its even slower than tor bcz it calculates 5 hashes for like nothing and all of that gets enecrpyted on top like wtf?
thivisthiv commentedon Aug 12, 2025
I think this project is nice, but it seems confusing to me. (I don't want to say this project is bad because I don't know if it's a bad project tbh)
thivisthiv commentedon Aug 12, 2025
I think Betaweb would be a better name for this project to avoid confusion. (Just a suggestion) EDIT: I don't know networking much so take this with a grain of salt.
Queen12s commentedon Aug 12, 2025
shitweb would be better
NeKon69 commentedon Aug 12, 2025
Yes that's what I meant.
Me too! (cause it confused me too)
thivisthiv commentedon Aug 13, 2025
People say the spec sheet is AI which it makes sense how, also I found it weird there's no prototype of Betanet. All there is a spec sheet and it's mostly made by AI allegedly. This is weird.
Heliodex commentedon Aug 13, 2025
From only a quick read of the spec, it's pretty dense and incorporates a lot of really complex concepts like the governance system and HTX. This would make any implementation pretty complicated or overly difficult as there's no small subset or baseline to start at and grow from. On the other hand, how many different capabilities it provides gives it immediate strong use cases once implementations are available.
For me, looking at the technologies list (Good crypto, SCION, QUIC + MASQUE, libp2p, Nym mixnodes, Handshake + FVM + EVM consensus, strong anti-concentration measures, Cashu payments enforcing WoT, minimal linkability), it's awesome. This is pretty much a dream protocol and I'd love to see it succeed.
I have enough skills in some areas to start on or contribute work to a Betanet implementation, though I don't think I'd be able to get to a working state with the currently available information. Therefore, I'd like to see clearer explanations by the developers/spec writers on why specific technologies were chosen and which features of each it uses – this would help implementors greatly with picking certain client libraries, as many of the systems listed have varying support across languages and implementations.
thivisthiv commentedon Aug 13, 2025
Yeah that's fair Heliodex
thivisthiv commentedon Aug 13, 2025
I don't think I will look into this project any further tbh.
thivisthiv commentedon Aug 13, 2025
It feels like K0 (or other person in the team or related to the team) used AI for the spec sheet, then is telling other developers to do the work for him. That's what I think but I may be not right ofc.
cousdev commentedon Aug 13, 2025
In the "Explaining Betanet" video, at timestamp 1:15, K0 said that "the internet was started by a team at CERN", which isn't true, the World Wide Web was started by CERN. It is an understandable mix-up, but if you're promising to deliver a replacement to https, it is a bad look.
At timestamp 4:22, K0 also said that TOR has 3 to 4 times the latency of Betanet. But Betanet is a specification, so how can you even begin to compare Betanet to TOR? I also doubt that Betanet will ever have the anonymity that TOR provides.
eemmmmg commentedon Aug 13, 2025
That's probably just what ChatGPT told him.
NeKon69 commentedon Aug 13, 2025
Maybe he meant expected latency? They might've taken some guesses on that project scale
NeKon69 commentedon Aug 13, 2025
What am I pressing so I am closing it over and over