You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If this is intended to be a true public good, something that outlasts the developers and runs without "centralizing influences" (as it must if it is to avoid being captured given its inevitable success), please solve the issue of "distribution" before you build an infrastructure around sharing using old-fashioned Web 2.0 servers. Do this first or you'll never do it.
Please think about:
a) pinning the results of each verification to IPFS,
b) not using IPNS because once a smart contract is verified, it never needs to be verified again (IPNS assumes changing data which this data is not),
c) make updates to your "database" periodically and in a way that is reproducible (this ensures non-capturability),
d) make sure your solution costs as close to zero dollars per X period as you can -- this will make it a sustainable public good. This is easily accomplished using pinning on IPFS,
e) keep an updated (and periodic) manifest of every verified contract and publish the manifest to IPFS,
f) share the IPFS hash of the manifest (which now 32-bytes long and points to every verification) to a smart contract such as Unchained Index.
g) don't duplicate work already being done by the Sourcify project. Work together.
Just to be more pointed: do not build a web 2.0 API server. That's been done, probably better, and it's 100% captured (EtherScan) and therefore long-term useless. Build a true, permissionless, sustainable public good.
The text was updated successfully, but these errors were encountered:
If this is intended to be a true public good, something that outlasts the developers and runs without "centralizing influences" (as it must if it is to avoid being captured given its inevitable success), please solve the issue of "distribution" before you build an infrastructure around sharing using old-fashioned Web 2.0 servers. Do this first or you'll never do it.
Please think about:
a) pinning the results of each verification to IPFS,
b) not using IPNS because once a smart contract is verified, it never needs to be verified again (IPNS assumes changing data which this data is not),
c) make updates to your "database" periodically and in a way that is reproducible (this ensures non-capturability),
d) make sure your solution costs as close to zero dollars per X period as you can -- this will make it a sustainable public good. This is easily accomplished using pinning on IPFS,
e) keep an updated (and periodic) manifest of every verified contract and publish the manifest to IPFS,
f) share the IPFS hash of the manifest (which now 32-bytes long and points to every verification) to a smart contract such as Unchained Index.
g) don't duplicate work already being done by the Sourcify project. Work together.
Just to be more pointed: do not build a web 2.0 API server. That's been done, probably better, and it's 100% captured (EtherScan) and therefore long-term useless. Build a true, permissionless, sustainable public good.
The text was updated successfully, but these errors were encountered: