We'd love Celo to be fully compatible with Foundry out of the box 🙌 |
---|
@douglasqian kindly pointed us to Github discussion in the Foundry repo discussing how to add non-Ethereum precompiles to Foundry: Decode non-Ethereum precompiles when tracing #1078.
According to @mattsse, they main ask would be a list of all address and function signature pairs (e.g. <name>(<inputs>)<outputs>
):
It would help if you could prepare them as address + signature pairs, this would make it easier to integrate them in the codebase ~ Source: Github comment
- Foundry repo (official): foundry-rs/foundry
- Foundry docs: book.getfoundry.sh
- Celo Foundry repo (minimal): bowd/celo-foundry
We're compiling the required information to simplify the Foundry integration.
See sample of information below (to confirm this is suits the Foundry team).
Precompiles
Questions
getValidator
returns a 20 bytes address padded to 32 bytes, what's the correct type here?proofOfPossession
return a bool in 32 bytes format, what's the correct type?