-
Notifications
You must be signed in to change notification settings - Fork 3
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
Budget modules base #75
Conversation
b5493e0
to
60f4e3a
Compare
error AlreadyExecutedForPeriod(uint256 allowanceId, uint256 paymentId, uint40 nextExecutionTime); | ||
|
||
// Protected so only spenders from the parent allowance to the one recurring payments can spend can add payments | ||
function addPayment(uint256 allowanceId, address to, uint256 amount) |
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 a function to batch-create payments (like executeMultiPayments
for executing multiple payments) would be useful as well.
* UpgradeableModuleProxyFactory: register * FirmBase, UpgradeableModuleProxyFactory: events to enable indexing * UpgradeableModuleProxyFactory: test upgrades and tighten types everywhere * UpgradeableModuleProxyFactory: test registry * UpgradeableModuleProxyFactory: more tests
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.
Noticed this event—unsure if this inconsistency is anywhere else in our contracts, but it's probably something to look at soon :)
* fix(events): make event naming consistent * chore: revert zodiac-related changes
Even though originally in this branch, RecurringPayments has been moved into a separate PR #86 as this one already has several big things and should be merged ASAP
TODO: