feat(recurring): add 0.2.0 admit and revoke cycle helpers - #1766
feat(recurring): add 0.2.0 admit and revoke cycle helpers#1766LeoSlrRf wants to merge 2 commits into
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Greptile SummaryThe PR adds calldata encoders and signer-based transaction helpers for admitting and revoking cycles through ERC20 Recurring Payment Proxy v0.2.0.
Confidence Score: 5/5The PR appears safe to merge because no blocking failure remains. No blocking failure remains. Important Files Changed
Reviews (2): Last reviewed commit: "test(recurring): use derived schedule ke..." | Re-trigger Greptile |
There was a problem hiding this comment.
Approved.
These helpers correctly expose the new admission and revocation calls without adding client-side authority: the contract still enforces the relayer role, and callers supply the contract-derived schedule key rather than treating scheduleId as the key.

Add
admitCyclesandrevokeCyclessupport for ERC20 Recurring Payment Proxy v0.2.0Exposes two new relayer-role functions from the
0.2.0recurring payment proxy contract:admitCycles/encodeAdmitCycles— allows a relayer to admit specific cycles (identified by a bitmask) so that a subscriber can self-trigger them.revokeCycles/encodeRevokeCycles— allows a relayer to revoke previously admitted cycles without affecting relayer-initiated triggers.Both functions accept a
scheduleKeyand amask(BigNumberish), and theencode*variants produce calldata without requiring a deployed proxy address. The async variants resolve the proxy address from the known deployment on the target network and throw if none is found.