Ethereum

personal_sign#

The sign method calculates an Ethereum specific signature with:sign(keccak256("\x19Ethereum Signed Message:\n" + len(message) + message))).

By adding a prefix to the message makes the calculated signature recognizable as an Ethereum specific signature. This prevents misuse where a malicious DApp can sign arbitrary data (e.g. transaction) and use the signature to impersonate the victim.

Note See ecRecover to verify the signature.

Parameters#

message, account

1. DATA, N Bytes - message to sign.
2. DATA, 20 Bytes - address.

Returns#

DATA: Signature

Example#

// Request{  "id": 1,  "jsonrpc": "2.0",  "method": "personal_sign",  "params":["0xdeadbeaf","0x9b2055d370f73ec7d8a03e965129118dc8f5bf83"],}// Result{  "id": 1,  "jsonrpc": "2.0",  "result": "0xa3f20717a250c2b0b729b7e5becbff67fdaef7e0699da4de7ca5895b02a170a12d887fd3b17bfdce3481f10bea41f45ba9f709d39ce8325427b57afcfc994cee1b"}

eth_sign#

The sign method calculates an Ethereum specific signature with: sign(keccak256("\x19Ethereum Signed Message:\n" + len(message) + message))).

By adding a prefix to the message makes the calculated signature recognizable as an Ethereum specific signature. This prevents misuse where a malicious DApp can sign arbitrary data (e.g. transaction) and use the signature to impersonate the victim.

Note the address to sign with must be unlocked.

Parameters#

account, message

1. DATA, 20 Bytes - address.
2. DATA, N Bytes - message to sign.

Returns#

DATA: Signature

Example#

// Request{  "id": 1,  "jsonrpc": "2.0",  "method": "eth_sign",  "params": ["0x9b2055d370f73ec7d8a03e965129118dc8f5bf83", "0xdeadbeaf"],}// Result{  "id": 1,  "jsonrpc": "2.0",  "result": "0xa3f20717a250c2b0b729b7e5becbff67fdaef7e0699da4de7ca5895b02a170a12d887fd3b17bfdce3481f10bea41f45ba9f709d39ce8325427b57afcfc994cee1b"}

An example how to use solidity ecrecover to verify the signature calculated with eth_sign can be found here. The contract is deployed on the testnet Ropsten and Rinkeby.

eth_signTypedData#

Calculates an Ethereum-specific signature in the form of keccak256("\x19Ethereum Signed Message:\n" + len(message) + message))

By adding a prefix to the message makes the calculated signature recognizable as an Ethereum specific signature. This prevents misuse where a malicious DApp can sign arbitrary data (e.g. transaction) and use the signature to impersonate the victim.

Note the address to sign with must be unlocked.

Parameters#

account, message

1. DATA, 20 Bytes - address.
2. DATA, N Bytes - message to sign containing type information, a domain separator, and data

Example Parameters#

[  "0xCD2a3d9F938E13CD947Ec05AbC7FE734Df8DD826",  {    types: {      EIP712Domain: [        {          name: "name",          type: "string",        },        {          name: "version",          type: "string",        },        {          name: "chainId",          type: "uint256",        },        {          name: "verifyingContract",          type: "address",        },      ],      Person: [        {          name: "name",          type: "string",        },        {          name: "wallet",          type: "address",        },      ],      Mail: [        {          name: "from",          type: "Person",        },        {          name: "to",          type: "Person",        },        {          name: "contents",          type: "string",        },      ],    },    primaryType: "Mail",    domain: {      name: "Ether Mail",      version: "1",      chainId: 1,      verifyingContract: "0xCcCCccccCCCCcCCCCCCcCcCccCcCCCcCcccccccC",    },    message: {      from: {        name: "Cow",        wallet: "0xCD2a3d9F938E13CD947Ec05AbC7FE734Df8DD826",      },      to: {        name: "Bob",        wallet: "0xbBbBBBBbbBBBbbbBbbBbbbbBBbBbbbbBbBbbBBbB",      },      contents: "Hello, Bob!",    },  },];

Returns#

DATA: Signature

Example#

// Request{  "id": 1,  "jsonrpc": "2.0",  "method": "eth_signTypedData",  "params": ["0x9b2055d370f73ec7d8a03e965129118dc8f5bf83", {see above}],}'// Result{  "id": 1,  "jsonrpc": "2.0",  "result": "0x4355c47d63924e8a72e509b65029052eb6c299d53a04e167c5775fd466751c9d07299936d304c153f6443dfa05f40ff007d72911b6f72307f996231605b915621c"}

eth_sendTransaction#

Creates new message call transaction or a contract creation, if the data field contains code.

Parameters#

1. Object - The transaction object
2. from: DATA, 20 Bytes - The address the transaction is send from.
3. to: DATA, 20 Bytes - (optional when creating new contract) The address the transaction is directed to.
4. data: DATA - The compiled code of a contract OR the hash of the invoked method signature and encoded parameters. For details see Ethereum Contract ABI
5. gas: QUANTITY - (optional, default: 90000) Integer of the gas provided for the transaction execution. It will return unused gas.
6. gasPrice: QUANTITY - (optional, default: To-Be-Determined) Integer of the gasPrice used for each paid gas
7. value: QUANTITY - (optional) Integer of the value sent with this transaction
8. nonce: QUANTITY - (optional) Integer of a nonce. This allows to overwrite your own pending transactions that use the same nonce.

Example Parameters#

[  {    from: "0xb60e8dd61c5d32be8058bb8eb970870f07233155",    to: "0xBDE1EAE59cE082505bB73fedBa56252b1b9C60Ce",    data: "0x",    gasPrice: "0x029104e28c",    gas: "0x5208",    value: "0x00",  },];

Returns#

DATA, 32 Bytes - the transaction hash, or the zero hash if the transaction is not yet available.

Use eth_getTransactionReceipt to get the contract address, after the transaction was mined, when you created a contract.

Example#

// Request{  "id": 1,  "jsonrpc": "2.0",  "method": "eth_sendTransaction",  "params":[{see above}],}// Result{  "id": 1,  "jsonrpc": "2.0",  "result": "0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331"}

eth_signTransaction#

Signs a transaction that can be submitted to the network at a later time using with eth_sendRawTransaction

Parameters#

1. Object - The transaction object
2. from: DATA, 20 Bytes - The address the transaction is send from.
3. to: DATA, 20 Bytes - (optional when creating new contract) The address the transaction is directed to.
4. data: DATA - The compiled code of a contract OR the hash of the invoked method signature and encoded parameters. For details see Ethereum Contract ABI
5. gas: QUANTITY - (optional, default: 90000) Integer of the gas provided for the transaction execution. It will return unused gas.
6. gasPrice: QUANTITY - (optional, default: To-Be-Determined) Integer of the gasPrice used for each paid gas
7. value: QUANTITY - (optional) Integer of the value sent with this transaction
8. nonce: QUANTITY - (optional) Integer of a nonce. This allows to overwrite your own pending transactions that use the same nonce.

Example Parameters#

[  {    from: "0xb60e8dd61c5d32be8058bb8eb970870f07233155",    to: "0xd46e8dd67c5d32be8058bb8eb970870f07244567",    data: "0xd46e8dd67c5d32be8d46e8dd67c5d32be8058bb8eb970870f072445675058bb8eb970870f072445675",    gas: "0x76c0", // 30400    gasPrice: "0x9184e72a000", // 10000000000000    value: "0x9184e72a", // 2441406250    nonce: "0x117", // 279  },];

Returns#

DATA - the signed transaction data

Example#

// Request{  "id": 1,  "jsonrpc": "2.0",  "method": "eth_signTransaction",  "params":[{see above}],}// Result{  "id": 1,  "jsonrpc": "2.0",  "result": "0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331"}

eth_sendRawTransaction#

Creates new message call transaction or a contract creation for signed transactions.

Parameters#

1. DATA, the signed transaction data.

Returns#

DATA, 32 Bytes - the transaction hash, or the zero hash if the transaction is not yet available.

Use eth_getTransactionReceipt to get the contract address, after the transaction was mined, when you created a contract.

Example#

// Request{  "id": 1,  "jsonrpc": "2.0",  "method": "eth_sendRawTransaction",  "params":[    "0xd46e8dd67c5d32be8d46e8dd67c5d32be8058bb8eb970870f072445675058bb8eb970870f07244567"  ],}// Result{  "id": 1,  "jsonrpc": "2.0",  "result": "0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331"}