-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve usage code #21
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGreatTM
test/Verify.t.sol
Outdated
contract VerifyTest is Test { | ||
uint256[2] public pubKey; | ||
|
||
function setUp() public { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
recommend CREATE2-deploying P256Verifier in setUp()
two advantages:
- test reliability: tests run offline, dont rely on
fork-url
/ the public base-goerli endpoint flakes sometimes - sanity checks that the hardcoded
VERIFIER
address and create2-deployedP256Verifier
address match
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems running CREATE2 in tests generates a different address. Worth investigating in more detail but I suspect it's a Foundry bug as we discussed. Maybe we should just pull this out into its own issue for future?
re public base-goerli endpoint flakes: I've been using a different RPC (locally and in this PR) which hasn't flaked for me since I switched
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved to #22. Merging as-is.
0f661cd
to
6674f37
Compare
No description provided.