Skip to content

Understanding the use of precompiled contracts in tests #808

Answered by emo-eth
PaulRBerg asked this question in Q&A
Discussion options

You must be logged in to vote

Hey Paul,
For the latest approaches, make sure you’re taking a look at the 1.2 branch here: https://github.com/ProjectOpenSea/seaport/tree/1.2 (though read me and documentation still need to be updated). Most of the relevant stuff lives in foundry.toml and BaseConsiderationTest (and the GH actions test yaml config).

In the full CI workflow, we pre-compile the optimized byte code for the smart contracts and test against them using the test profile for the three you mentioned. It’s possible there are some places we are still normally deploying the code (SignatureVerifier is an interesting example, as the test contract inherits the signature verification logic directly).
However, the example…

Replies: 1 comment 4 replies

Comment options

You must be logged in to vote
4 replies
@PaulRBerg
Comment options

@PaulRBerg
Comment options

@emo-eth
Comment options

@PaulRBerg
Comment options

Answer selected by PaulRBerg
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants