Namechain L2 and ENS burning / re-claiming burn address owned names

Hi everyone.
Namechain ENS L2 is coming up which makes me wonder about implementing a new mechanism related to burned domains - aka domain reclaiming from burn address owned ENS domains.

People burn domains for a variety of reasons - I’ve seen people extending and burning domains to prevent others from using certain names. My company name got nuked for some reason and is extended for multiple years preventing me from securing an onchain identity for it - just one example out of many.

When a name expires and gets re-registered, the token is burned, re-minted, and transferred to the new owner - but what about domains that are deliberately burned by the user while still having years left on the lease?
Would it be possible for burn address owned domains to be burned and re-minted before the lease expires? Basically getting a mechanism that allows re-claiming them?

As an example: Let’s say you are visa and own visa.eth because you’re moving into the web3 space - before mastercard/americanexpress figure out they want to get into web3, you could purchase their names, maxx out the lease period and send the names to burn address - giving your competitors a major disadvantage and preventing them from using their identity within web3. I guess you could still do it just by holding the name, but some people deliberately grab names just to extend them and burn them to make them unusable. Which is imho malicious, and burned names should be able to be reclaimed - but I’m biased since someone nuked my name this way while adding years to the expiry - and I don’t necessarily want to rebrand or use a longer name variation lol.

Anyway, I was wondering if it would it be possible to implement a mechanism where burned domains (burn address owned with a remaining lease) can be reclaimed for the regular registration costs - while either zeroeing the remaining lease on them or adding it to the re-minted wrapper?

Since ENS is moving to L2, I assume it could be possible to implement something like that? Not really sure since I’m not a dev, but I’m basically thinking of a mechanism that allows names owned by the burn address to be burned by the ENS L2 contract and newly registered before the lease expires - preferably while still maintaining the time that was left on the lease of the burned name. Since the previous owner didn’t like their ENS and burned it - why should it be removed out of the circulation for the remaining time of the lease instead of being able to be reclaimed and used by whoever desires to own that particular name?

Is this even possible? Any thoughts on this re-claim mechanism?

2 Likes

Could you share an example? I’d like to review the transaction history.

Burned names with active leases create a griefing vector that could be exploited to slow adoption.

Has Labs considered mitigating this in ENSv2, or is it a design problem the developer community could scope and address?

1 Like

wired.eth - owned by 0x000000000000000000000000000000000000dEaD
Expiry - October 17, 2125

depositcontract.eth - expires January 1, 2150

As of now 0x000000000000000000000000000000000000dead owns 953 names - at least according to vision.
I went to the burn address profile and sorted by expiring date.

1 Like

Besides people griefing and burning names of competitors while max extending to prevent registration for a hundred years - there’s also groups like publicburn. Their goal was to crowdfund name extensions and burn “offensive” names. As of now they seem to be inactive, but they did this thing multiple times in the past.

For some reason, this included lebanoncentralbank

If the vision number is accurate, then there are currently ~1000 names affected and locked for up to 127 years. Someone with enough capital can basically prevent their competitors from ever getting a usable web3 name.
As an example: besides wired.eth being locked for 100 years, someone could also go for 0xwired / web3wired / wiredweb3 / thewired / etc and basically nuke every usuable web3 name of their competitor. One could stay up to date on new startups in a certain niche and auto-register and auto-burn every single one.

/edit
Not sure if the issue is solvable for any of the currently affected names (?) - but I assume that on ENSv2 it could be?

Any ENSv2 name that is owned by burn address while having an ongoing lease could trigger a reclaim function and become available to re-register while either zeroeing the remaining lease - or giving the person registering whatever lease time it still had left while only costing the regular registry costs - a bonus for reclaiming names someone maliciously burned.
Either way, burned names that someone doesn’t want to use anymore should immediately go back to the pool of names available to be registered.

Again, I’m not a dev so I’m not sure how much can be done here. I was mainly wondering about re-claim functionality since my company name got burned and locked out - and then I saw that there was about a thousand names like that. I assume that an option for names to be reclaimed IF they’re burn address owned is theoretically possible to be added to ENSv2 wrappers? I also assume it’s probably not possible on already affected v1 names?

1 Like

that would violate the constitution of ENS

ENS governance will not enact any change that infringes on the rights of ENS users to retain names they own, or unfairly discriminate against name owners’ ability to extend, transfer, or otherwise use their names.

so any owner of name owner can do anything they see fit with it

1 Like

They technically don’t own the name since it’s burn address owned - IMHO they forfeit their ownership of the name as soon as they decided to maliciously burn it.
The issue is that names like that are locked for whatever lease period was still on them. And that prevents people from getting the names that should be available since nobody actually owns them anymore.
And before you say “but that what’s the previous owner intended” - well, they don’t own that name anymore, do they? Not your keys not your crypto and… not your ENS because you burned it :joy_cat:

ukrainian.eth was burned due to the war conflict - although that one has less than 1y left to become available again. But someone could keep extending it, so it would forever become unattainable because some random decided they want to prevent people from owning that name.
And anyone could keep extending it, even people who previously never owned it could do that to prevent others. So a name related to a conflict like the above ENS, could be forever griefed out of grudge.

elon.eth was burned by an elon hater and is locked for 9 years - and it can still be extended by anyone wishing to keep that name locked out forever.

It’s one thing to not infringe on the rights of ENS users and the names they ACTUALLY own - I fully agree with that sentiment btw.
But it’s a totally different thing to make burned names reclaimable, since they aren’t owned by anyone and were burned - thus forfeiting ownership of the name to the burn address / nobody.

That imho means that the person who had it and burned it doesn’t own the name and forfeit the rights of the name the moment they burned it. And those burned names shouldn’t be locked up for whatever duration they have on their lease, they should be able to return to the pool of claimable domains.

Let’s say someone yoink’d SpikeWatanabe.eth, burned it and kept extending the lease while it’s in the burn address. It’s not owned by anyone per se, but it’s permanently removed from the pool of claimable domains as long as they keep extending it.
Even when I try not to be biased due to being affected by this exact scenario, and even if reclaiming wouldn’t be possible for domains currently locked out like this - I still think that burned domains are forfeited by the previous owner and need to be able to be reclaimed before the lease runs out. And that should be an addition to ENSv2 on namechain. Any name sent to / owned by the burn address should trigger a reclaim function and allow it to be registered again.

There are names like that with over 100 years on the lease, which means that they will still be locked out even after the initial owner isn’t around anymore. So not only are they locked out after the previous owner forfeit them, they will still be locked out long after the person is dead. And if anyone down the road decides they dislike elon.eth or ukrainian.eth - they can still keep extending the names.
Does " ENS governance will not enact any change that infringes on the rights of ENS users to retain names they own" apply here in your opinion? Because imho it doesn’t. Burned names have no owner and need to be able to be reclaimed.

/edit
Obviously adding that functionality might mean some people will just bypass it - instead of extending and burning they would just extend and keep it in their wallet. Everything can be gamed, and the reclaiming functionality could be gamed as well by doing just that. It’s not a perfect solution, but it’s definitely a needed addition and it should be considered for ENSv2.

Alternatively burn address owned domains could have a trigger that prevents extending the lease on them / or zeroes the lease to a minimal timeframe - for example a month. Or maybe it just immediately adds them to the premium curve before they become claimable again. Either way, something needs to be done. Right now it’s a thousand names - but as adoption grows and web3 becomes more important - this will become a bigger issue with people griefing the names of competitors / people they don’t like.

1 Like

that opens pandora box of ENS being able to redact registered names, which are advertised as immutable and guaranteed to be immutable by constitution

No it doesn’t? How does that enable redacting registered names? How does that impact actual ENS domain holders?

The reclaim function should only be triggered in case the name:
a) Is burn address owned - aka someone forfeit ownership of the name by burning it while it still has an active lease.

b) the name has a running lease, which is effectively locking it up in the burn address and preventing it from being newly registered even though it’s not owned by anyone. (As seen with names maliciously locked for 100+ years)

c) burn address owned domains could have a trigger that prevents extending the lease on them and keeping them in the burn address limbo / extending the timeframe they are locked out from being able to be registered - as it’s the case with some domains.

It only impacts names that are locked out in the burn address - which is the case with some names being locked out for years, decades, and even CENTURIES.
This would NOT impact any actual ENS name owners!

for starters how do you define burn address? and who is going to decide that it is a burn address or not? because your so called burn address can be anything without private key, it just so happened that historically people were sending them specifically to 0x000…000 address, but in practice it can be anything, so what give you right to decide to remove ownership for any address for that matter

and secondly who is going to decide which names should be removed circulation

thirdly, from what I understand its not possible technically, unless fork entire protocol which is not happening

Spike is right. Doing this clearly runs counter to the intent of the person who owned the name, compromise’s ENS integrity, and is a clear violation of the ENS constitution. Aside from which, there are practical issues identifying whether an address is a ‘burn’ address or not - and if this were implemented users could simply burn names by sending them to addresses that cannot be proven to be burn addresses.

1 Like

Tell me, what address do burned wrappers get sent to? What address does every service use to burn things on ETH? What address did a ~1000 ENS domains end up at to be “burned” and removed from circulation? I think the consensus is pretty clear on that, no?

As I said above, even with the re-claim option - people could bypass the reclaim option at 0x0000dead by just extending names in their own wallets. Could also send it to any random wallet and lose the keys to it. It’s not the consensus burn address, but would work the same and would bypass the reclaim. That would bypass the reclaim option anyway, but reclaim functionality would largely mitigate the issue of griefing names.

Either way, there is a clear consensus on what address people use to remove things from their wallets to “burn” them. This effectively forfeits ownership of the asset. This is also the case for ENS names.
But while other assets are permanently stuck in the burn address, ENS names can be re-registered once the lease ends.
The issue is that burned names often have a lease on them, especially when burned maliciously and timelocked to prevent others from registering them - thus permanently locking them out of circulation even though nobody owns them.
As already said, there are around ~1000 names like that - with some being stuck for over 100 years. A CENTURY! That’s more than a lifetime some names will get locked out for. And in my lifetime the number of names affected will probably grow beyond the ~1000 names it affects today.

Right now it affects like a ~1000 names, over time that number will grow. We’ve seen it during the war (names like “ukrainian.eth” being burned) and we’ve seen it with initiatives like publicburn (removing names they personally deem offensive). We’ve seen it with Elon being lock-burned because someone personally dislikes him lmao
I’ve seen it with my company name for some reason.
All of those names were maliciously burned. It’s worse than squatting, because a squatter will at least want to sell the names they own. But those people just don’t want to own a certain name, and want to prevent others from owning it as well. And there is a clear consensus where those names end up at - an address widely known as the burn address.

Burned names with active leases create a griefing vector that could be exploited to slow adoption. And this will happen over time. But it could be mitigated on v2 namechain. At least for the consensus burn address - people who still want to, would probably bypass it by just holding those names.
But anyone who would burn it in the way everyone burns things - would just make the name re-claimable again.

Both the reclaim trigger as well as lease extend prevention for burn address owned names are beneficial for ENS.

And btw saying things like:

ENS governance will not enact any change that infringes on the rights of ENS users to retain names they own, or unfairly discriminate against name owners’ ability to extend, transfer, or otherwise use their names.

Is also not really true. To bypass someone burn-locking my company name I grabbed a malformed / case sensitive version of it. And while I can see owning it on Vision for example, I cannot edit it on ENS. Nor can I add records to it. Same with a display image.
OS and ENS manager just show a hash, but that name is basically useless and cannot be edited nor used in any beneficial way / a way that ENS names are being normally used.
This could have let me use the capitalized version of my company name which someone maliciously burned to prevent from having my onchain brand - aka competitor acting maliciously - but ENS prevents me from using that :)))

I guess you’re gonna say it’s a different thing because “we added name normalization for a reason and prevent name editing for a reason”.
(Sure, you can justify anything if you try hard enough - but it still prevents users from using the names they own and want to use.)

But guess what? Adding a re-claim functionality for burn address owned names also has a reason - reclaiming forfeited names people abandoned and maliciously time locked. Some of which were timelocked for a goddamn century.

ENSv2 could have some features that prevent time locking domains in a burn address. Like making them reclaimable when burn address owned and having a remaining lease, zeroeing the lease when burned, preventing name extension when burn address owned. Not adding that functionality is certainly a weird choice, and “not wanting to impact owners” is not a good argument given the fact the ownership of those names was forfeited by sending them to an address widely known as the BURN ADDRESS where you send assets that you don’t want to own.

Saying that it’s to not “impose on the will of the owner” when those people aren’t owning those names because they forfeited the ownership to the burn address, while at the same time imposing the will re: malformed case sensitive names that people actually own - is kind of hypocritical. Because if an actual owner of a name, actually wants to use a name - they should be able to. Instead they get an unusable namehash that cannot be edited and is unusable.
Kind of hypocritical, but whatever. I’m definitely biased because of my company name being burned and not even being able to use the case sensitive version of it - but even BEYOND that - ENSv2 should have that functionality, otherwise name griefing will become a bigger and bigger issue over time as adoption grows.

Global conflicts making people burn names, company competition name burns, malicious burning over petty things once someone forgets to extend a name, social justice name burning like public burn, etc - this will become a bigger and bigger issue. And while it cannot be fully prevented (see above re: time-locking names outside of burn address) - it can certainly be mitigated just via the functionality mentioned above - reclaim, lease zeroeing, extension prevention on burn address owned names.

If you can’t see this becoming an issue over time then you’re not thinking in the right timeframe. Once blockchain adoption is truly mainstream, and I really mean mainstream, you have no idea how awful it will become. One example being existing companies preventing every single emerging competitor from owning a usable brandname. And that’s just one example.

You cannot consider just the first-order consequences of a proposed action - you have to think about how people will change their behaviour in reaction to it.

If your goal is to burn something, and someone changes the rules so the old burn address no longer ensures something is actually burned, you’ll pick a different address. Most likely one that can’t be proven to be a burn address, so the things you intended to burn, stay burned.

More generally, we should not be trying to deliberately circumvent a user’s intentions when it comes to assets they own. Doing so would set a terrible precedent, and as I’ve already outlined, be trivial to bypass for anyone who really wants to burn a name.

1 Like

depositcontract.eth owner was set to the burn address on purpose so that it’s records can never be changed. depositcontract.eth.limo/ takes you to the official Ethereum staking launchpad and also points to the staking deposit contract.

4 Likes