-
Notifications
You must be signed in to change notification settings - Fork 91
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
Feature/metadata #461
base: develop
Are you sure you want to change the base?
Feature/metadata #461
Conversation
contracts/tests/recipientRegistry.ts
Outdated
registry.connect(requester).removeRecipient(recipientId) | ||
registry | ||
.connect(challenger) | ||
.removeRecipient(recipientId, { value: baseDeposit }) | ||
).to.be.revertedWith('Ownable: caller is not the owner') |
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.
@daodesigner, should these test failure fixes be moved to a different PR since it's not related to this PR and it might be easier for code review? I only found out about this because I added UniversalRecipientRegistry
and added similar test cases based on OptimisticRecipientRegistry
which also failed.
subgraph mapping for UniversalRecipientRegistry
e9af49f
to
a78a430
Compare
Allow recipient registry owner to add recipients for simple recipient registry type
Add email form for recipient registration
This PR integrates with the metadata registry, introduced changes
This PR closes #446, #450, #451, #458
An instance of the web app is deployed here: https://green-pine-7692.on.fleek.co/#/
FundingRoundFactory on rinkeby-arbitrum:
https://testnet.arbiscan.io/address/0x638cb73818cc3477679a996a8c37d1b23acf8974#readContract