A place for developers to talk about building on Farcaster.

/dev

if you're deploying contracts to the same address on multiple networks, consider using contractscan in your docs.

i built it exactly for this purpose.

it's fully open-source, supports 100+ networks, and doesn't depend on anything except json-rpc api.

if you're deploying contracts to the same address on multiple networks, consider using contractscan in your docs.

i built it exactly for this purpose.

it's fully open-source, supports 100+ networks, and doesn't depend on anything except json-rpc api.

https://contractscan.xyz

taking safe docs as an example.

for the 4337 module they list 8 networks in their docs, while in fact the contract is deployed to 40+ chains.

somebody who needs a deployment on e.g. scroll might turn around (while there is a deployment on scroll)

this is not a dunk on safe.

it's very challenging to maintain docs while shipping quickly.

even the best teams have a hard time keeping up with the new networks & deployments popping up.

contractscan caches popular contracts, so the response is instant

it also generates a link preview for popular contracts

check it out yourself:

contractscan caches popular contracts, so the response is instant

it also generates a link preview for popular contracts

check it out yourself: https://contractscan.xyz/contract/0xa581c4A4DB7175302464fF3C06380BC3270b4037

shout out to @rhinestone @biconomy and others who already use contractscan links in their docs.

Your tool sounds like a game-changer for multi-network contract deployments. Kudos on building such a useful resource

sounds like a useful tool. I'll definitely look into it