1) What are #ENS fuses?
With the name wrapper incoming I'm sure you've heard the word flying around. But what actually are fuses, who are they for, and why should you care?
With the name wrapper incoming I'm sure you've heard the word flying around. But what actually are fuses, who are they for, and why should you care?
2) The best way to frame fuses is through trustlessness. As you know, trustlessness is hugely important to ENS and what sets us apart from some of our largest competitors. ENS cannot change or retake your name, ever. It's not possible. How is that?
3) All ENS names are subnames of the name eth. My name, domico.eth, is the domico subname of eth. But eth isn't controlled by a human, so I don't need to trust that someone won't rug my name. Hence, a trustless name.
4) This is true because ENS handed the keys of eth over to a public contract, removing their own access. But at the moment this can only be done with root names like eth. If you own a subname of domico.eth, you would still have to trust me not to rug your name.
5) Enter fuses. Fuses can be thought of as gates that, when open, allow name owners (aka parents) to do specific things, such as control the subname. So why is this important?
6) This matters because fuses can be burnt. This is a permanent change that closes the gate, and removes the owners ability to access it ever again. This is very similar to ENS handing over the keys of eth.
7) There is a key set of fuses called permissions, which I will focus on here. One if these is the 'parent cannot control' permission (PCC), which exists on every name.
8) In our example, if you own sub.domico.eth, you are trusting that I won't change your name. With name wrapper I can now revoke (aka burn) PCC, which revokes my ability to ever again change your name.
9) You will no longer need to trust me, like I don't need to trust ENS. Your name is now yours, and it's trustless. We call this an emancipated name.
10) This is an important step towards making a trustless ecosystem of subnames. With this you will be able to verify the sovereignty of your names, or create sovereign subnames for your audience.
11) To support this, V3 of the ENS app will show you what each name and its parent can or cannot do, which will be under the Permissions tab when viewing a name.
12) I have focussed very specifically on permission fuses here, but there are many more things that you can do with them. The Name Wrapper is also much bigger than just fuses, so I encourage you to do some more research github.com/ensdomains/ens…
• • •
Missing some Tweet in this thread? You can try to
force a refresh
