Thanks @AvsA
We started performing data gathering exercises on targets for contract naming (which you can see here), incorporating some of the questions you highlight also makes sense.
Since the beginning of the year, the Enscribe team has been focused on building infrastructure to simplify contract naming for teams. This has been driven by a lack of adoption of ENS for naming contracts, which we believe presents a huge growth opportunity for the ENS protocol.
This is something we want to change, but if we can do it as a coordinated effort, it can increase reach. James’ proposal seeks to help by providing incentives in the form of ENS tokens for this activity.
We’d hope to see this unfold such that through contract naming season there will also be learnings about ways in which we can increase the surface area of primary contract naming through enhancements to the protocol, which is something we’ve been actively trying to do too as part of our work.