Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
213 lines (147 sloc) 15.1 KB
eip title author discussions-to status type category created requires
1077
Executable Signed Messages refunded by the contract
Alex Van de Sande <avsa@ethereum.org>, Ricardo Guilherme Schmidt (@3esmit)
Draft
Standards Track
ERC
2018-05-04
725, 191

Simple Summary

Allowing users to sign messages to show intent of execution, but allowing a third party relayer to execute them is an emerging pattern being used in many projects. Standardizing a common format for them, as well as a way in which the user allows the transaction to be paid in tokens, gives app developers a lot of flexibility and can become the main way in which app users interact with the Blockchain.

Abstract

User pain points:

  • users don't want to think about ether
  • users don't want to think about backing up private keys or seed phrases
  • users want to be able to pay for transactions using what they already have on the system, be apple pay, xbox points or even a credit card
  • Users don’t want to sign a new transaction at every move
  • Users don’t want to download apps/extensions (at least on the desktop) to connect to their apps

App developer pain points:

  • Many apps use their own token and would prefer to use those as the main accounting
  • Apps want to be able to have apps in multiple platforms without having to share private keys between devices or have to spend transaction costs moving funds between them
  • Token developers want to be able for their users to be able to move funds and pay fees in the token
  • While the system provides fees and incentives for miners, there are no inherent business model for wallet developers (or other apps that initiate many transactions)

Using signed messages, specially combined with an identity contract that holds funds, and multiple disposable ether-less keys that can sign on its behalf, solves many of these pain points.

Implementation

The signed messages require the following fields:

  • To: the target contract the transaction will be executed upon
  • From: the account that will be executed on behalf of
  • Value: the amount in ether to be sent
  • Data: the bytecode to be executed
  • Nonce: a nonce or a timestamp
  • GasToken: a token in which the gas will be paid (leave 0 for ether)
  • Gasprice: the gas price (paid in the selected token)
  • GasLimit: the maximum gas to be paid

Signing the message

In order to be compliant, the transaction MUST request to sign a messageHash that is a concatenation of multiple fields, plus one final field extraData that can be left blank but is added for forward compatibility.

The fields MUST be concatenated in this order:

keccak256(
    byte(0x19),
    byte(0),
    from,
    to,
    value,
    dataHash,
    nonce,
    gasPrice,
    gasLimit,
    gasToken,
    callPrefix,
    operationType,
    extraHash
);

The first and second fields are to make it ERC191 compliant. Starting a transaction with byte(0x19) ensure the signed data from being a valid ethereum transaction. The second argument is a version control byte.

The from field will always be the contract executing the code (address(this)), and the callPrefix is the 4 byte standard prefix of the function to be called in the from contract. This guarantees that a signed message can be only executed in a single instance.

operationType type will define what sort of operation will be executed (in assembly): 0 for a standard call, 1 for a DelegateCall and 0 for a create opcode. These can be extended in the future.

Backwards and forwards capability:

Not all executable signed messages contracts will have the same requirements, therefore some fields are optional. Fields byte(0x19), byte(0), from, to, value, dataHash are obligatory while nonce, gasPrice, gasLimit, gasToken, callPrefix, operationType are optional, but must be hashed in this order.

Regardless of which fields you use, in your contract you must accept an extraHash that is always hashed at the end. This is done to increase future compatibility of the standard: solidity's keccak treats keccak(a, b, c, d, e, f) as identical to keccak(a, b, concat(c, d, e, f). therefore by adding an extra field in the end that can be ignored by your contract, you allow it to be compatible with the same standard as other message standards that use it to sign it.

Multiple signatures

If multiple signatures are required, then all signed messageHashes should then be ordered by account and sent to the receiving contract which then will execute the following actions:

keep track of nonces:

Nonces work similarly to normal ethereum transactions: a transaction can only be executed if it matches the last nonce + 1, and once a transaction has occurred, the lastNonce will be updated to the current one. This prevents transactions to be executed out of order or more than once.

Contracts should accept transactions without nonce (nonce = 0). The contract then must keep the full hash of the transaction to prevent it from being replayed. This option allows contracts to have more flexibilities as you can sign a transaction that can be executed out of order or not at all, but it uses more memory for each transaction. It can be used, for instance, for transactions that the user wants to schedule in the future but cannot know its future nonce, or transactions that are made for state channel contracts that are not guaranteed to be executed or are only executed when there's some dispute.

execute transaction

The contract must then verify the signatures of the accounts and check if the public keys match accounts that are authorized to do what they intend to do: depending on the contract implementation, some contracts might require multiple key signatures, other might have specific actions few accounts are authorized to do.

If an identity, then, the contract should implement ERC725 identity management levels: a key must be at least an action key to have authorization to demand any call to external contracts, and a management key to demand calls to the contract itself.

If the signing accounts are authorized to do so, the contract must execute the requested action. If the current contract is the same as from field, then if can simply execute the actions by calling _to.call.value(_value)(_data).

How the contract interprets the intended action depends on its purpose. For instance a token contract can decide to implement it in a way that interprets all actions as token transfers, and uses the value to mean token value and bytecode as the data to pass to the recipient contract

Gas accounting and refund

The implementing contract must keep track of the gas spent. One way to do it is to first call gasLeft() at the beginning of the function and then after executing the desired action and compare the difference.

The contract then will make a token transfer (or ether, if tokenAddress is nil) in the value of gasSpent * gasPrice to the msg.sender, that is the account that deployed the message. If there are not enough funds, or if the total surpasses gasLimit then the transaction MUST revert.

If the executed transaction fails internally, nonces should still be updated and gas needs to be paid.

Contracts are not obligated to support ether or any other token they don’t want and can be implemented to only accept refunds in a few tokens of their choice.

Deployers of transactions have no guarantees that the contract they are interacting with correctly implements the standard and they will be reimbursed for gas, so they should maintain their own white/blacklists of contracts to support, as well as keep track of which tokens and for which gasPrice they’re willing to deploy transactions.

Supported functions

executeSigned( address to, address from, uint256 value, bytes data, uint nonce, uint gasPrice, uint gasLimit, address gasToken, operationType, extraHash, bytes messageSignatures)

Executes the signed message. Execution usually means that a contract will execute a call to the to address, with value amount of ether and data as its data. But in some special cases, a token can decide instead to interpret it specifically as executing a transferAndCall(to,from,data) or the equivalent.

More than one signed transaction with the same parameter can be executed by this function at the same time, by passing all signatures in the messageSignatures field. That field will split the signature in multiple 72 character individual signatures and evaluate each one. This is used for cases in which one action might require the approval of multiple parties, in a single transaction.

gasEstimate( address to, address from, uint256 value, bytes data, uint nonce, uint gasPrice, uint gasLimit, address gasToken, operationType, extraHash bytes messageSignatures) returns ( bool canExecute, uint gasCost) A read only function that checks if the transaction will be executable and how much gas it’s expected to cost.

lastNonce() public returns (uint nonce) lastTimestamp() public returns (uint nonce)

Both are simple read only functions that return the last used Nonce and last used timestamp.

requiredSignatures(uint type) returns (uint)

A function which returns the amount of signatures that are required for a given type of action (types being 1 = Management and 2 = Action).

event ExecutedSigned(bytes32 signHash, uint nonce, bool success);

Whenever a new transaction is executed it must emit an event with the signHash, nonce and either the transaction was successfully executed or not. Apps that are waiting for a transaction to be executed should subscribe to the identity and watch this event to see if their transaction was successful. If a different signHash is executed with an equal or higher nonce, it means that your transaction has been replaced.

Implementation

One initial implementation of such a contract can be found at the Identity Gas Relay at the Status repository

Similar implementations

The idea of using signed messages as executable intent has been around for a while and many other projects are taking similar approaches, which makes it a great candidate for a standard that guarantees interoperability:

Swarm city uses a similar proposition for etherless transactions, called Gas Station Service, but it's a different approach. Instead of using signed messages, a traditional ethereum transaction is signed on an etherless account, the transaction is then sent to a service that immediately sends the exact amount of ether required and then publishes the transaction.

Areas for improvements

This ERC inherits all it's permission systems from ERC720 Identity, which has very basic levels of authorization (can call contract itself, can make external calls, cannot make any calls) and a simple generic multisig. Ideally we need a more comprehensive standard for authorizations, that enables, for instance, that a single key can only make calls to a specific contract, or specific functions. Also, the amount of signatures required to do an action could be variable, maybe a single key could have a limit on how much value it can spend in a single day, requiring more signatures to move higher amounts (how to properly measure the value of a token or NFT transfer is another matter entirely).

Usage examples

This scheme opens up a great deal of possibilities on interaction as well as different experiments on business models:

  • Apps can create individual identities contract for their users which holds the actual funds and then create a different private key for each device they log into. Other apps can use the same identity and just ask to add permissioned public keys to manage the device, so that if one individual key is lost, no ether is lost.
  • An app can create its own token and only charge their users in its internal currency for any ethereum transaction. The currency units can be rounded so it looks more similar to to actual amount of transactions: a standard transaction always costs 1 token, a very complex transaction costs exactly 2, etc. Since the app is the issuer of the transactions, they can do their own Sybil verifications and give a free amount of currency units to new users to get them started.
  • A game company creates games with a traditional monthly subscription, either by credit card or platform-specific microtransactions. Private keys never leave the device and keep no ether and only the public accounts are sent to the company. The game then signs transactions on the device with gas price 0, sends them to the game company which checks who is an active subscriber and batches all transactions and pays the ether themselves. If the company goes bankrupt, the gamers themselves can set up similar subscription systems or just increase the gas price. End result is a ethereum based game in which gamers can play by spending apple, google or xbox credits.
  • A standard token is created that doesn’t require its users to have ether, and instead allows tokens to be transferred by paying in tokens. A wallet is created that signs messages and send them via whisper to the network, where other nodes can compete to download the available transactions, check the current gas price, and select those who are paying enough tokens to cover the cost. The result is a token that the end users never need to keep any ether and can pay fees in the token itself.
  • A DAO is created with a list of accounts of their employees. Employees never need to own ether, instead they sign messages, send them to whisper to a decentralized list of relayers which then deploy the transactions. The DAO contract then checks if the transaction is valid and sends ether to the deployers. Employees have an incentive not to use too many of the companies resources because they’re identifiable. The result is that the users of the DAO don't need to keep ether, and the contract ends up paying for it's own gas usage.

References

Copyright

Copyright and related rights waived via CC0.

You can’t perform that action at this time.