Expand the Solidity verifier (Barretenberg) compatibility section in docs to cover Top 10 EVMs and how to contribute compatibility tests

[Savio-Sou]

Problem

We know Barretenberg, Noir's default proving backend loaded, generates Solidity verifiers for programs that are deployable on Ethereum.

It is however not directly clear with the same applies to other EVMs which might miss certain precompiles or specific EVM features.

Happy Case

Expand the current list we have in the Noir docs to cover:

1. ✅ and ❌ for the top 10 EVMs measured by TVL (reference: DefiLlama)
2. Guide on how to test compatibility for other EVMs
3. List known EVM precompiles and features required for a EVM to be "Noir-ready" (simply cover gaps discovered when testing (1) is a win)
4. Encourage community to submit PRs for updating / add EVMs to the list

Project Impact

Nice-to-have

Impact Context

Great reference for:

• Developers interested in deploying Noir applications on non-Ethereum EVMs
• EVM development teams interested in supporting Noir / ZK applications

Workaround

None

Workaround Description

No response

Additional Context

No response

Would you like to submit a PR for this Issue?

None

Support Needs

No response

[TomAFrench]

I'd recommend just linking off to https://www.evmdiff.com/features?feature=precompiles and just telling people it needs to support ec_add, ec_mul, ec_pairing. This avoids us from having to explicitly enumerate every single EVM network which wants a shoutout in our docs or gatekeeping this along with the inevitable arguments about which networks are deserving (i.e. if it's notable enough for inclusion in noir docs then it should be notable enough for evm.diff)

[critesjosh]

@Savio-Sou I added Tom's suggestion in the linked above PR. I see that evm diff doesnt cover the top 10 EVM chains by TVL, but do you think this is sufficient? Or do you still think we should cover the rest of the list in the description?

[Savio-Sou]

Thanks for the suggestion @TomAFrench!

@critesjosh that's a great starting step 👍 with 4 of the top 10 EVMs by TVL not covered by EVM Diff (as of this time), it is worthwhile still to test them imo for wider reach and better neutrality in the marketing to follow.
(Assuming this is not a huge resource drag on our end, e.g. 2 man-days max; let me know if I'm underestimating the effort.)

[critesjosh]

you're right, it shouldn't be a big effort. it's just a lower priority so we haven't gotten around to it yet

[jzaki]

Once we have the subset to test, these come in handy for chainids and rpc providers. Faucets still likely a manual process though :/

[signorecello]

• BSC ✅ Contract
• Blast L2 ✅ Contract
• Avalanche C-Chain ✅ Contract
• Polygon zkEVM ❌ Contract
• Mode ✅ Contract
• Merlin ❌ Contract
• Linea ✅ Contract
• Moonbeam ✅ Contract (tested because it's a parachain on Polkadot)

[critesjosh]

• BSC ✅ TX

This just looks like a contract creation tx. Don't you need to send a tx that calls verify on that contract to fully test it?

[signorecello]

It's a view function so you can't see it on the block explorer. I'm working on making noir-starter easier to "attach" to a deployed contract though