This discussion happened in October and Iāve updated the doc with some feedback that happened to it.
Iāve formally proposed the EIP on this PR:
What does this allows, in a short version:
Provides an on-chain data of which apps and websites are bing used for the new names being registered
Also allows that app data to be even further figure which of these new users came from specific social media campaigns, online influencers, newsletters, marketing programs etc, so we can measure who and what is being responsible for these new names
Sets the initial paths for a future revenue sharing/referral program which rewards those apps or influencers for their work.
Whatās next?
This will not result in a vote. The next step is simply:
Lobbying apps to adopt the standard by adding their own source parameter
Lobbying them into also adding a referral to memory to add the extra data parameter
Help build apps to visualize these and in the future fund referral programs to reward these contributions
Before lobbying to other apps, we should start off adding it into ENS manager site and that will give us the ratio of the third party name registration. I spoke to the front end team, and they will add a ticket after their v3 release. We probably better starting off with some sort of id repo like slips/slip-0044.md at master Ā· satoshilabs/slips Ā· GitHub then shift to on chain contract when we implement some sort of rev share
Nice seeing this resurface! As Slobo mentioned, Iāve implemented a similar idea into a few apps but with a different (worse ) hashing method, so Iāll get those updated shortly. Iāll also start thinking about the best way to track this in a dashboard.
It uses sort.xyz (an API-first version of Dune) to query the first 10 characters of the secret in register and registerWithConfig transactions from the official Registrar contract. Hereās the query.
Sort usually only keeps 7 days of transaction history, but the founder was nice enough to whitelist the Registrar contract so that it will keep all future transactions (starting an hour ago). This is why youāll see all rows having a count of 1 right now on the website.
Only a platform code is not enough IMO. I think it is better if it combined with a platform code derived from its DNS and a web3 identity code derived from ENS, like:
ENS is web3 native and it could easily receive referral fee in tokens. Also, in the future, maybe we could let the owner of the ENS claim their referral fees rather than distributing these fees through a web2-method.
My initial instinct is that not all registrations are coming/will come from DNS frontends (take @wolframās example above of predomain.eth.limo which we know can also be accessed from other IPFS gateways), so IMO that wouldnāt be the best primary referral code.
yes, it does make sense. But I think there would a possibility that we hardly distinguish the real referrer if someone used someone elseās referral code to scam.
Hey
I implemented the platform source for ENS Vision on Nov 3rd, using the draft specification.
We have been using the first 6 bytes of the namehash of āens.visionā (799faa801b1e) since then.
I can update it to match the current spec.
Iām just wondering why itās not showing up on the Flock Watcher.
Note that we are sending internal transactions from our Bulk Registration Contract to the Registrar Controller.
Iām looking into this now. Itās probably due to the Bulk Registration contract. So in a typical transaction youād register multiple names buy calling the registrar contract multiple times. But we are using Sort.xyz to extract all the calls and it does not take in consideration internal calls to the ens registrar. In fact neither does etherscan: I can see that your transaction does contains the string 799faa801b1e but because itās not verified I canāt even understand what it does.
@gregskril would you know how to extract data from internal calls to the ENS registrar so we can add direct contract to contract calls to the watcher?
Answering my own question: turns out that wasnāt any registrar but a user that was registering a batch of āgpt-emoji.ethā domains which reused the secret. I also cleaned up some other usages of secret reuse (not showing any count < 10) and updated the site to reflect that:
So right now the only registrar it shows is ens-fairy. ENS Vision uses it but I canāt query the internal transactions yet, so we might have uncovered an issue with the standard if we canāt measure calls made from other contracts.