Changelog
0.6.0
- Scheduled calls can now specify a required gas amount. This takes place of
the
suggestedGas
api from 0.6.0
- Scheduled calls can now send value along with the transaction.
- Calls now protect against stack depth attacks. This is configurable via the
requiredStackDepth
option.
- Calls can now be scheduled as soon as 10 blocks in the future.
- Experimental implementation of market-based value for the
defaultPayment
scheduleCall
now has 31 different call signatures.
0.6.0
- Each scheduled call now exists as it’s own contract, referred to as a call
contract.
- Removal of the Caller Pool
- Introduction of the claim api for call.
- Call Portability. Scheduled calls can now be trustlessly imported into
future versions of the service.
0.5.0
- Each scheduled call now exists as it’s own contract, referred to as a call
contract.
- The authorization API has been removed. It is now possible for the contract
being called to look up
msg.sender
on the scheduling contract and find
out who scheduled the call.
- The account management API has been removed. Each call contract now manages
it’s own gas money, the remainder of which is given back to the scheduler
after the call is executed.
- All of the information that used to be stored about the call execution is now
placed in event logs (gasUsed, wasSuccessful, wasCalled, etc)
0.4.0
- Convert Alarm service to use library contracts for all functionality.
- CallerPool contract API is now integrated into the Alarm API
0.3.0
- Convert Alarm service to use Grove for tracking scheduled call ordering.
- Enable logging most notable Alarm service events.
- Two additional convenience functions for invoking
scheduleCall
with
gracePeriod and nonce as optional parameters.
0.2.0
- Fix for Issue 42. Make the free-for-all bond bonus restrict itself to the
correct set of callers.
- Re-enable the right tree rotation in favor of removing three
getLastX
function. This is related to the pi-million gas limit which is restricting
the code size of the contract.