Understand if and how we want to support precompiled contracts

[manuelwedler]

This came in the Clear Signing working group. It would be helpful for auditors to be able to fetch ABI for such contracts. See this example on Etherscan:
https://seiscan.io/address/0x0000000000000000000000000000000000001007#code

These don't return bytecode via eth_getCode. However, they have a callable ABI. Etherscan just shows a Solidity interface as source for these contracts. We might be able to do something similar.

I think it could be a server level feature outside of lib-sourcify. These are such few contracts that it would even be fine to hardcode these in some json file or something IMO.

[marcocastignoli]

I think we can add support to these kind of contracts, and I think for now we can verify them manually (calling the contract to see if the interface is actually correct).

I really like the idea of storing these contracts in a separate place (not our database). I think that a list of these contracts stored in JSON files is a good idea.