Annotations for standardized smart contracts
There are several classes of standardized smart contracts - e.g. ERC20, ERC721, ERC777. While there are variations in their implementation, there are a lot of common properties you would expect to hold across implementations. To avoid manually copying and pasting the same properties for each implementation, in Scribble 0.6.1 we added contract-level macros. A macro consists of 2 parts: 1. A macro definition - a .yaml file describing the target contract and the properties that the macro should insert
2. A #macro <name>(<var1>, <var2>...); annotation on the target contract, that instantiates all the properties from the corresponding .yaml file. Lets explore this with ERC20 as an example.

Example: The ERC20 macro

Lets try to define some common properties for a class of ERC20 tokens. All ERC20 tokens must for example define a transferFrom and totalSupply functions, and many implementations will have a internal map from addresses to balances. We may want to check several properties of such tokens. For example:
  • when transferFrom(from, to, amount) is called, the balance of the sender decreases by amount, and the balance of the receiver increases by amount
  • the return value of totalSupply is always equal to the sum of the balances
  • No function changes the total supply of the tokens (assuming we are only talking about non-deflationary tokens)

Macro Definitions

Here is how we can define a new macro in an yaml file, that checks the above properties when instantiated:
balances: mapping (address => uint256)
- msg: "The token has a fixed supply (only set in constructor)."
prop: "#if_updated msg.sig == bytes4(0x00000000);"
- msg: "Result is equal to sum of balances"
prop: "#if_succeeds $result == unchecked_sum(balances);"
transferFrom(from, to, amount):
- msg: "The sender looses amount"
prop: "#if_succeeds from != to ==> old(balances[from]) - amount == balances[from];"
- msg: "The receiver receives amount"
prop: "#if_succeeds from != to ==> old(balances[to]) + amount == balances[to];"
There are several things to unpack here:
  1. 1.
    On line 1 we give the name of the macro. This will be how we will refer to this macro when instantiating it.
  2. 2.
    In the variables section (lines 2-3) we list the variables that we expect the target contract to have. Note that in the actual contract the variables can have different names! We will see how this renaming happens in the next section
  3. 3.
    In the properties section, we have a list of "annotation targets" and for each target the list of annotations that must be applied to this target. An annotation target can be a function signature, state variable name, or <contract> which applies to the whole contract.
  4. 4.
    Each annotation has two fields - msg: is the human readable label that should be applied to the property and prop: is the actual scribble annotation.
So for example the below fragment of the yaml definition, specifies that scribble should find the function totalSupply() in the target contract, and insert #if_succeeds {:msg "Result is equal to sum of balances" $result == unchecked_sum(balances); right above it:
- msg: "Result is equal to sum of balances"
prop: "#if_succeeds $result == unchecked_sum(balances);"

Macro Invocations

Lets look at how you apply a macro, and what happens in more detail. In the below example we apply the macro defined in the previous section to the MyToken contract.
/// #macro erc20(_balances);
contract MyToken {
mapping(address=>uint256) _balances;
function totalSupply() public view (returns uint256) { ... };
function transferFrom(address sender, address reciver, uint256 value) public returns (bool) { ... }
The macro invocation is done with the #macro erc20(_balances) annotation in the docstring above the target contract. The macro invocation gives the macro name (erc20) and it lists the actual names of all variables required in the variables section of the macro definition.
In the variables section of the erc20 macro definition we mentioned a balances variable. Some properties declared in the erc20 macro definition also talk about a balances variable. However MyToken doesn't have a balances state variable - instead it has a state variable named _balances. By specifying erc20(_balances) in the macro invocation, we are telling scribble to replace all occurances of balances in the macro definition with _balances. Additionally note that the arguments of transferFrom in the definition are named from , to and amount. On the other hand in MyToken these same arguments are named sender, receiver and value. Scribble will automatically rename the function arguments of function properties when instrumenting the contract.
So after the macro is instantiated, the above contract will be annotated as follows:
contract MyToken {
/// #if_updated {:msg "The token has a fixed supply (only set in constructor)."} msg.sig == bytes4(0x00000000);
mapping(address=>uint256) _balances;
/// #if_succeeds {:msg "Result is equal to sum of balances"} $result == unchecked_sum(_balances);
function totalSupply() public view (returns uint256) { ... };
/// #if_succeeds {:msg "The sender looses amount"} from != to ==> old(balances[from]) - amount == balances[from];
/// #if_succeeds {:msg "The receiver receives amount"} from != to ==> old(balances[to]) + amount == balances[to];
function transferFrom(address sender, address reciver, uint256 value) public returns (bool) { ... }

Macro Locations

Scribble looks for macros recursively in the "macros" directory. You can specify the macros directory using the --macro-path command line options. As of Scribble v0.6.3 we also ship a small standard library of macros which is searched in addition to the explicit --macro-path location. The standard macro library is located under SCRIBBLE_INSTALL_PATH/stdlib where SCRIBBLE_INSTALL_PATH is the location where npm has installed the eth-scribble package.