-
Notifications
You must be signed in to change notification settings - Fork 47
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
account+rpc: allow expiration update for existing accounts #185
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.
Cool, this will just work with the existing ModifyAccount
call on the auctioneer
?
Not many comments, great PR 👍
We no longer need to track if the account expiry needs to be watched or not as the watcher now supports updating existing unfulfilled expiry requests.
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.
Latest version looking pretty good, my comment re allowing while pending batch still stands
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.
LGTM 🍀
This is an intermediate state where an account has met its expiration while having a pending update waiting for confirmation. The introduction of this state was necessary as the existing StateExpired state was not sufficient to handle all edge cases regarding account renewals. Now that this state exists, we can be sure renewals cannot happen until the account is both confirmed, unspent, and expired.
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.
Great work, LGTM ✅
Replaced by #199. |
This PR allows traders to update their account expiration after it has been created through the RPC/CLI interface. It also serves as groundwork for when we eventually allow automatic account renewals through batch participation. As a result of this functionality, a default of 30 days has been set going forward for all new accounts created, and can be overwritten if necessary.
Fixes #8.
Fixes #39.
Fixes #160.