A naming standard for contracts proposed by Nick.eth. 

Every smart contract has its own address, making it possible to name smart contracts using ENS; however, looking up an ENS address currently requires a minimum of two calls. With ENS Contract Discovery as proposed by Nick.eth, 

[https://discuss.ens.domains/t/introducing-a-pseudo-namespace-for-ens-contract-discovery/10016](https://discuss.ens.domains/t/introducing-a-pseudo-namespace-for-ens-contract-discovery/10016)

it is possible to create a contract registry that requires only a single call to look up contract addresses. I propose to develop this idea using _contract.eth, wherein anyone can register subnames, e.g., bandits._contract.eth. It is also possible to use sub-subnames, e.g., 1.bandits._contract.eth, or 1.10knft.bandits._contract.eth.


 



ENS Contract Discovery

Projects eligible for the Ecosystem small grants rounds are those that build on or improve the ENS Ecosystem.

Applicable projects are meaningfully building, creating content, or improving the ENS ecosystem. An example is ENSfairy.xyz, an ENS name-gifting tool that adds explicit functionality to the ENS ecosystem.