A place for talking about the Ethereum Virtual Machine on Farcaster.

Kicking around some ideas for a contract ABI well-known location. For example, we might provide the Storage Registry ABI from farcaster.xyz at 

/.well-known/contracts/eip155:10:0x00000000fcce7f938e7ae6d3c335bd6a1a7c593d

Are there any existing standards or specs for something like this?

I'm eth newbie..just learning
(working on @farcaster)

terminally.online

Interesting! I wonder if it makes sense to do something like what sourcify.dev does with their layout (and maybe IPFS?), that way a domain can choose to pin a set of contract metadata and serve it off a well-known prefix?

I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs. gregskril.com

You can store ABI for an ENS name which points to a smart contract!

Data Engineer by day, Ethereum advocate by night

Could potentially be a standard: it's useful to associate known domains with their canonical contract ABIs.

Are you thinking this for Farcaster ABIs only? Or as a repository of well-known contracts across DeFi (Aaves Pool contract, oracles, etc)