scopelift / cove-backend Goto Github PK

Currently there's no way to verify Huff contracts, as Etherscan and other explorers doesn't support Huff language yet. It would be very useful for the Huff community if Cove provides this functionality.

I'm happy to jump in and try to implement it, if its desirable to have this feature.

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.

I just attempted to verify https://arbiscan.io/address/0x7b1247f443359d1447cf25e73380bc9b99f2628f#code
which was deployed in https://arbiscan.io/tx/0x33d08314c113d1778c2da6759c4be43eb18109103d53bb632f1d7a5c41d1bc6d
from this source code but hit "No matching contracts found"

Using the following test data:

• repo: https://github.com/ScopeLift/optimizoors-perpetual-protocol
• commit: 4a5ab700bf2dfa9b8e95c5f1de6baaacfd00dcd2
• address: 0xbf2870611603b2f02b8616e0fe65c60f7657a0f4
• chains: Optimism 0x3de2ecd811ffc00e9d256e39a458e3f5a2e6cb4205e39677570fcd11c7f29a54

The only difference between the found and expected creation code is that the expected code has appended constructor arguments. This is expected, but this causes the verification match to change from Full to Partial, but that should only be affected by metadata hash