-
Notifications
You must be signed in to change notification settings - Fork 0
Safe integration for mintHypercert() #37
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
Conversation
The Merkle trees had slight differences in their generic type. All functions in the allowlist utils return the generic parameter [string, bigint]
Since it's only used in one place we can inline.
One of the test cases experiences temporal coupling with the getConnected() method. I tried to move the method call down to where it is used and that broke the test.
Without this patch the caller is only able to mint a Hypercert with their connected browser wallet.
Coverage Report
File Coverage
|
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.
Looks good to me. The interface is a bit less explicit then the one used in the marketplace which is fine, but we'd probably want to get that consistent at some point 👍
Yep, good point. We should harmonise this at some point. @bitbeckers and I decided on the quicker implementation to get this shipped sooner rather than later. Otherwise I would've spent some time to clean up the function, split it out probably using a strategy pattern to have a clean separation between the EOA and multisig cases. At any rate, |
🎉 This PR is included in version 2.6.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This PR adds Safe support for minting a new Hypercert.
The way to switch the SDK over to propose a transaction to the Safe app is to add
safeAddress
to theoverrides
object.You can see a Safe transaction created by the SDK here.