-
Notifications
You must be signed in to change notification settings - Fork 203
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
SemaphoreViem implemented #364
Conversation
…re/release Yarn patch to change `changelogithub` output
…re/bump-version New NPM scripts to bump versions and publish NPM packages
…erifier-hardhat add hardhat task to deploy SemaphoreVerifier.sol
feat(identity): prepend hex strings with 0x
feat(identity): use sha512 to extract more entropy from message
This new package allows devs to fetch on-chain data by using a Semaphore subgraph or the Ethers library. BREAKING CHANGE: The code of the old `@semaphore-protocol/subgraph` package has been moved to the `@semaphore-protocol/data` package. re semaphore-protocol#256
Worse, I forgot to write the test. I'll go write one soon. |
Hey @inaridiy! Don't worry, take your time. Thank you so much. |
@vplasencia Accomplished! I have confirmed a successful build and test! |
* @param network Chain object of viem. | ||
* @param options Viem options. | ||
*/ | ||
constructor(network: Chain = sepolia, options: ViemOptions = {}) { |
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.
It would be nice for devs to have a way to pass a valid chain without installing vite
separately and importing viem/chains
. The type here can be similar to EthersNetwork
(i.e. strings), and the constructor could then use the right chain object based on that string. It would also be more consistent with SemaphoreEthers
.
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.
I think the current implementation is better here, given its affinity with the Viem ecosystem.
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.
Makes sense. Do you think it makes sense to export those chains' objects in this package too?
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.
It certainly makes sense, and I find it a very nice contrast to SemaphoreEthers.
Thanks for the review. I will fix it now. |
I have made some corrections and added some comments |
Great, it looks like there's a small error in the API test. |
Hey @inaridiy, after releasing Semaphore V4 many conflicts have come out. It may make sense to open another clean PR. Do you still want to work on this? |
@cedoor Thank you for the follow-up. I apologize for my long inactivity on this PR. Given the conflicts with Semaphore V4 and my inability to dedicate proper time, I agree it's best to close this PR. |
Hi @inaridiy, thanks for your quick reply and the work you've done here. I'll close this PR but a gitPOAP will still be awarded to you :) |
@inaridiy @gitpoap-bot |
Congrats, @inaridiy ! You've earned a GitPOAP for your contribution! GitPOAP: 2023 Semaphore Contributor: Head to gitpoap.io & connect your GitHub account to mint! Learn more about GitPOAPs here. |
Description
SemaphoreViem is implemented.
Related Issue
Closes #343
Does this introduce a breaking change?
Other information