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
withdrawMultiple, darknodeBalances #45
Conversation
await linkedList.insertBefore(NODE1, NULL).should.not.be.rejected; | ||
await linkedList.remove(NULL).should.not.be.rejected; | ||
await linkedList.insertBefore(NODE1, NULL); | ||
await linkedList.remove(NULL); |
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.
Why are the non-rejection assertions removed?
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.
Are they useful? It throws anyway, and it still doesn't give the line number.
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.
What's the motivation for removing them? I feel like the test is much clearer if there is an assertion.
Description
This PR adds two functions to the Darknode Payments contract:
withdrawMultiple
anddarknodeBalances
.Motivation
withdrawMultiple
: This allows users to withdraw multiple tokens with a single transaction.darknodeBalances
: This allows retriving darknode reward balances without having to know about the store.