Scheduled calls can be considered either authorized or unauthorized.

An authorized call is one for which either scheduledBy == targetAddress or for which the scheduledBy address has been granted explicit authorization by targetAddress to schedule calls.

An unauthorized call is one for which scheduledBy != targetAddress and the scheduledBy address has not been granted authorization to schedule calls.


Any address can still schedule calls towards any other address. The authorization status only effects which address the calls originate from, not whether they will be executed.

Differentiating calls

When the Alarm service executes calls, they will come from one of two addresses depending on whether the call is considered authorized or unauthorized. These addresses will sometimes be referred to as relays, as they relay the actually function call for the Alarm service, allowing the callee to differentiate between authorized and unauthorized calls.


A call’s authorization state is determined at the time of execution.

authorized calls will orignate from the address returned by the authorizedAddress function.

  • Solidity Function Signature: authorizedAddress() returns (address)
  • ABI Signature: 0x5539d400

unauthorized calls will orignate from the address returned by the unauthorizedAddress function.

  • Solidity Function Signature: unauthorizedAddress() returns (address)
  • ABI Signature: 0x94d2b21b

Checking authorization status

When a function is called on a contract, it can check whether or not it is authorized by checking which of the two relay addresses matches msg.sender.

To do this, our contract needs to be at least partially aware of the Alarm ABI function signatures which can be done easily with an abstract contract.

Consider the idea of a contract which holds onto funds until a specified future block at which point it suicides sending all of the funds to the trustee.

contract AlarmAPI {
    function authorizedAddress() returns (address);
    function unauthorizedAddress() returns (address);
contract TrustFund {
    address trustee = 0x...;
    address _alarm = 0x...;
    function releaseFunds() public {
        AlarmAPI alarm = AlarmAPI(_alarm);
        if (msg.sender == alarm.authorizedAddress()) {

In the above example, the TrustFund.releaseFunds function checks whether the incoming call is from the authorized alarm address before suiciding and releasing the funds.


It should be noted that the above example would require authorization to have been setup by the TrustFund contract via some mechanism like a contract constructor.

Managing Authorization

It is the sole responsibility of the contract to manage address authorizations, as the functions surrounding authorization use msg.sender as the contractAddress value.

Granting Authorization

Authorization is granted with the addAuthorization function.

  • Solidity Function Signature: addAuthorization(address schedulerAddress)
  • ABI Signature: 0x35b28153

This function adds the schedulerAddress address to the authorized addresses for msg.sender.

Here is how a solidity contract could grant access to it’s creator.

contract Example {
    address alarm = 0x....;
    function Example() {"addAuthorization(address)")), msg.sender);

Upon creation, the Example contract adds it’s creator as an authorized scheduler with the alarm service.

Checking Access

You can check whether an address has authorization to schedule calls for a given address with the checkAuthorization function.

  • Solidity Function Signature: checkAuthorization(address schedulerAddress, address contractAddress) returns (bool)
  • ABI Signature: 0x685c234a

Removing Authorization

A contract can remove authorization from a given address using the removeAuthorization function.

  • Solidity Function Signature: removeAuthorization(address schedulerAddress)
  • ABI Signature: 0x94f3f81d
contract MemberRoster {
    address alarm = 0x....;
    mapping (address => bool) members;
    function removeMember(address memberAddress) {
        members[memberAddress] = false;"removeAuthorization(address)")), memberAddress);

In the example above we are looking at part of a contract that manages the membership for an organization of some sort. Upon removing a member from the organization, the MemberRoster contract also removes their authorization status for scheduled calls.