Alright, I’m back from my time off, which was very much needed after 4 years of work. I’m sorry this wasn’t taken care of before I left, self care took a priority. Apparently this is my problem since I brought it up in the first place.
Let’s get a few things clear before I give an update on the state of things.
These tokens were given to the Status Organization for the early contributions and integrations with ENS. Period. So I would appreciate the hyperbole in this thread about theft and greed to stop. Looking at you @6ft7dontball. A case can very easily be made that the rightful owners are the developers of of the feature, and if the ENS team felt that subdomains were the rightful owners they would have included them in the original airdrop. Chill, you’ll get your ENS because WE AS STATUS feel that they should go to you and others like you for your early use of the feature. Has any other large ENS subdomain holder done this?
I’ve also heard that this is just an easy thing to do and complaints that it hasn’t been done yet. While I agree that there should have been more work from us at Status to get this finished, it certainly isn’t easy. If it were so easy, why haven’t any of you who are sitting around waiting done anything? It’s easy? Right? I’m looking at you @cyy_ok. Chill, you’ll get your ENS.
This situation was thrusted upon us on top of the tremendous amount of work we are trying to do. I’m sorry if things take longer than expected, but rest assured we aren’t all sitting on ass. We’re all working to put out software that respects your rights and privacy. Situations like this take our attention away from that work, and we do it BECAUSE WE THINK OUR PRINCIPLES MATTER and you deserve to own these tokens.
I will admit there should have been more movement from the organization during my vacation to do something here, as well as from me before leaving. I was playing with burnout and stress so it got dropped, no one picked it up because it isn’t clear who this type of stuff falls upon. We’ll work to fix that within the organization.
Ok, here’s the update on current situation.
Work on the contracts has been underway, you can track that progress at this Github repo. I’ve been told tests are underway and the client-side application to the contracts is close to being ready to be tested. As this isn’t isn’t a small amount of value, I would like to take some time to test to make sure it works as intended and these funds aren’t stolen because of a simple bug.
I drafted everything and submitted it internally for corrections and additions. It seemed it was agreed upon but was never submitted to a vote. I’ll re-read it today and get it going so we have a vote. Funny enough, the vote seems more like a formality anyway as it seems that everyone agrees this is the way to go, or doesn’t want to spend time thinking about it but me and a few other folks. The only movement I’ve seen is people complaining it hasn’t happened yet outside of the contract work done by @gravityblast.
I’ll post a snapshot vote link in here later today as I finally have a window of non-meetings since I started back at work this month.
You can tell I’m not pleased with the current state of this situation, yet I’ll continue to work to get this done and distributed to you all, even though IT HAS NOTHING TO DO WITH MY JOB.
Chill, you’ll get your ENS tokens.