From 9535cf42316a9da3264d9a2500da40372094100a Mon Sep 17 00:00:00 2001 From: Ricardo Guilherme Schmidt Date: Thu, 9 Jan 2020 00:57:14 -0200 Subject: [PATCH] codespell --- EIPS/eip-1077.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-1077.md b/EIPS/eip-1077.md index 72f72c20..d63e7f39 100644 --- a/EIPS/eip-1077.md +++ b/EIPS/eip-1077.md @@ -83,7 +83,7 @@ In order to be compliant, the transaction **MUST** request to sign a "messageHas The fields **MUST** be constructed as this method: -The first and second fields are to make it [EIP-191] compliant. Starting a transaction with `byte(0x19)` ensure the signed data from being a [valid ethereum transaction](https://github.com/ethereum/wiki/wiki/RLP). The second argument is a version control byte. The third being the validator address (the account contract address) accoring to version 0 of [EIP-191]. The remaining arguments being the application specific data for the gas relay: chainID as per [EIP-1344], execution nonce, execution data, agreed gas Price, gas limit of gas relayed call, gas token to pay back and gas relayer authorized to receive reward. +The first and second fields are to make it [EIP-191] compliant. Starting a transaction with `byte(0x19)` ensure the signed data from being a [valid ethereum transaction](https://github.com/ethereum/wiki/wiki/RLP). The second argument is a version control byte. The third being the validator address (the account contract address) according to version 0 of [EIP-191]. The remaining arguments being the application specific data for the gas relay: chainID as per [EIP-1344], execution nonce, execution data, agreed gas Price, gas limit of gas relayed call, gas token to pay back and gas relayer authorized to receive reward. The [EIP-191] message must be constructed as following: ```solidity