Knowing which website registered a .eth name would be useful, like knowing how many registrations were done via ensfairy.xyz.
We can leverage the existing contract and create a social convention to get visibility into the platform source.
secret parameter is random data that obscures the name before the final step of the registration process is complete.
It is 32 bytes of entropy and the ens manager app on app.ens.domains generates it by calling the following:
We can adopt a social convention that generates the secret from a combination of taking the first 10 characters of sha256(‘platform_name’) and combines it with the appropriate number of random bytes.
This way the first 10 char of the secret would be the platform name. So for example if the above was registered via ensfairy the secret would be:
The bold part is the first 10 characters of sha256(‘ensfairy’)
With this we can attribute registrations using the first 10 chars of the secret.
Can’t anyone use someone else’s platform name?
Yep 100%, I don’t see this as an issue.
Given that economic value could accrue to the top platforms there would be an incentive for the major players to play ball.
Feedback is appreciated.