One example given in EIP-4804 is web3://vitalikblog.eth:5/
. Does this example require the EIP in this post?
The resolving part will depend on this EIP. However, after discussing with EIP editors on EIP-4804, we agree to defer the detailed resolving part to another EIP (i.e., for ENS, EIP-6821).
2 Likes
Instead of web3
for the key name, what about something like contentscript
or contentcontract
to go with the already existing contenthash
from ERC-1577?
1 Like
Looks like a good idea. Let me check with others in the circle
1 Like
Thanks for the comment. After discussing with other community members, we agree to replace the web3
text record with contentcontract
. The EIP is also updated accordingly. Pleaes check.
1 Like