The Ethereum Reach connector generates a contract that manages one instance of the DApp’s execution. It is guaranteed to use exactly one word of on-chain state, while each piece of consensus state appears as a transaction argument.
Non-network tokens are compiled to ERC-20 fungible tokens.
Token type refers to the address of the ERC-20 contract.
Token minting launches a fresh ERC-20 contract based on the OpenZeppelin ERC-20 implementation, which stores additional metadata and allows the creator to burn tokens and destroy the token if there is no supply (i.e. it has all been burned).
During compilation, the connector produces one intermediate output: "input.export.sol", containing the Solidity code implementing the contract.
A few details of Ethereum leak through to Reach. The node that a given participant is connected to does not instantly know that its blocks are correct and may revert past transactions after it reaches consensus with the rest of the network. This means that Reach applications must not make externally observable effects until after such consensus is reached.
Backends must respect the following environment variables: