acl:execute-scheduled
Execute an operation through an AccessManager, consuming its schedule when the operation was delayed.
⚗️ Experimental — available at next.evmcrispr.com.
Supports runtime fields inside smart blocks. Use explicit @helper! expressions or captured outputs; other fields are evaluated at build time.
Syntax
Section titled “Syntax”acl:execute-scheduled <manager> <target> <signature> [...params]Arguments
Section titled “Arguments”| Name | Type | Evaluation | Description |
|---|---|---|---|
manager | address | Runtime in smart blocks | AccessManager address |
target | address | Runtime in smart blocks | Managed contract address |
signature | write-abi | Build time | Function to call on the target |
[...params] | any | Runtime in smart blocks | Arguments matching the signature types |
Options
Section titled “Options”| Name | Type | Evaluation | Description |
|---|---|---|---|
--value | number | Runtime in smart blocks | ETH to send with the call (in wei) |
Examples
Section titled “Examples”load acl
set $manager 0xc0dbDcA66a0636236fAbe1B3C16B1bD4C84bB1E1set $token 0x9C58BAcC331c9aa871AFD802DB6379a98e80CEdb
acl:execute-scheduled $manager $token "setDuration(uint256)" 1y- Also works for calls that need no delay: the AccessManager relays the call directly when the caller has immediate permission.
- Consumes the schedule created by acl:schedule when one exists.
See Also
Section titled “See Also”- acl:schedule — schedule the operation first
- @acl:canCall — check if a delay applies