Grundlæggerne af Namebase har kritiseret sociale medier og centraliserede domæneforvaltningssystemer. Lad os se, hvad deres egen initiativ indebærer, og hvorfor det ikke falder i alles smag.
/ Unsplash /
Hvad skete der
Kampagnen for en alternativ implementering af navnerum har været aktivt fremmet siden sidste år. For nylig blev der udgivet med udførlige forklaringer af kritiske vurderinger, forslag til global decentralisering, nødvendige krav til projektet og dets potentielle muligheder.
Vi har analyseret artiklen og diskussionen omkring den på relevante platforme. Her deler vi vores vigtigste fund, supplerende materialer og meninger om emnet.
Hvad kritiserer de for
På der er henvisninger til problemet med overdreven centralisering fra "teknologimonopolers", nationale og internationale organisationers side — fra til sociale medier.
Grundlæggerne af Namebase sætter spørgsmålstegn ved, hvordan rettigheder til ytringsfrihed og ejerskab af digitale aktiver som profiler, brugernavne og domænenavne implementeres under sådanne strukturer (og endda ved staters) kontrol. I deres præsentationer — nævner de ofte Hvilke forslag fremlægges
af entusiaster inden for dette emne for at bevæge sig væk fra de mange komplikationer mod et universelt, bæredygtigt og decentraliseret navnerum, kræves der:
Ifølge At sikre decentraliseringen af det nye system.
- At bevare kun de afgørende funktionaliteter.
- At sikre lav ressourceforbrug og trustless-tilgængelighed.
- At opretholde kompatibilitet med den overordnede netværksinfrastruktur.
- At muliggøre opdatering på protokolniveau.
- Det første og andet krav kan realiseres med en dedikeret
PoW-blockchain Handshake ).Таким образом разработчики планируют исключить риски дестабилизации системы из-за действий стейкхолдеров или каких-либо внешних факторов.
If you ask them, designing based on existing blockchains will not achieve the desired effect in the long run, which is a decisive factor for uninterrupted operation and updates (the fifth requirement) of such high-level 'IT standards'.
In response to the third requirement, the developers propose to store namespace data in so-called , designed specifically for solving this task. They serve as an alternative to in Ethereum, but with nodes of 32 (leaf/sibling nodes) and 76 bytes (internal nodes), and the PoW weight here does not exceed a kilobyte even with tens of millions of 'leaves'.
Thus, the team attempts to optimize the time and resources required for name resolution. In addition, they have introduced a 'lightweight' on C – it only deals with DNS tasks.
/ Unsplash /
Speaking of compatibility (the fourth point), according to the founders, the project aims to expand the capabilities of existing IT standards rather than replace them. The developers are confident that 'users on the network should have more opportunities to maintain control and ensure that a particular name belongs to them', and continue the development of their product (basic information about it — , , ).
What are they criticized for
On Hacker News, a link was provided to a , based on Handshake, and . But there were also those who expressed , that the vendor is simply trying to become yet another registrar operating names in a slightly updated format. The independence of such projects was also put into question, to data on the distribution of mining pools.
At some point, the discussion went off track – one of the site residents even the thought of a similar 'revival' of the -ecosystem, which could become a decentralized response to the monopolized social media market. But here, as in the situation with Handshake, everything hinges on the issue of monetization and the degree of elegance in resolving it. As is known, DNS projects have been attempted , but this process did not go as smoothly as their founders would have liked.
Currently, Handshake and Namebase have several alternatives – from Unstoppable Domains () to Ethereum Name Service (). Vil de kunne konkurrere med de eksisterende metoder til domænestyring og blive udbredte, vil tiden vise.
P.S. Yderligere læsning på vores Habr-blog — .
Kilde: habr.com
