diff --git a/package.json b/package.json
index 4613add20b7..aeff400142b 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
{
"name": "ethereum-org-website",
- "version": "2.33.1",
+ "version": "2.34.0",
"description": "Website of ethereum.org",
"main": "index.js",
"repository": "git@github.com:ethereum/ethereum-org-website.git",
diff --git a/src/content/developers/docs/apis/json-rpc/index.md b/src/content/developers/docs/apis/json-rpc/index.md
index ae21c132e3f..3e4396913f0 100755
--- a/src/content/developers/docs/apis/json-rpc/index.md
+++ b/src/content/developers/docs/apis/json-rpc/index.md
@@ -7,2472 +7,11 @@ sidebar: true
In order for a software application to interact with the Ethereum blockchain (by reading blockchain data and/or sending transactions to the network), it must connect to an Ethereum node.
-For this purpose, every Ethereum client implements a [JSON-RPC specification](http://www.jsonrpc.org/specification), so there are a uniform set of [methods](/developers/docs/apis/json-rpc/#json-rpc-methods) that applications can rely on.
+For this purpose, every Ethereum client implements a [JSON-RPC specification](http://www.jsonrpc.org/specification), so there are a uniform set of methods that applications can rely on.
-## Prerequisites {#prerequisites}
+JSON-RPC is a stateless, light-weight remote procedure call (RPC) protocol. Primarily the specification defines several data structures and the rules around their processing. It is transport agnostic in that the concepts can be used within the same process, over sockets, over HTTP, or in many various message passing environments. It uses JSON (RFC 4627) as data format.
-You should be familiar with how JSON-RPC API endpoints can be used to fetch data. It will also be helpful to understand the [Ethereum stack](/developers/docs/ethereum-stack/) and [Ethereum clients](/developers/docs/nodes-and-clients/).
+## JSON-RPC resources {#json-rpc-resources}
-## Convenience Libraries {#convenience-libraries}
-
-While you may choose to interact directly with Ethereum clients via this JSON-RPC API, there are often easier options for dapp developers. Many [JavaScript](/developers/docs/apis/javascript/#available-libraries) and [backend](/developers/docs/apis/backend/#available-libraries) API libraries exist to provide wrappers on top of the JSON-RPC API. With these libraries, developers can write intuitive, one-line methods in the programming language of their choice to initialize JSON-RPC requests (under the hood) that interact with Ethereum.
-
-## JSON-RPC Endpoint {#json-rpc-endpoint}
-
-Ethereum clients each may utilize different programming languages when implementing the JSON-RPC specification. See individual client documentation for further details related to specific programming languages.
-
-## JSON-RPC Support {#json-rpc-support}
-
-| | cpp-ethereum | go-ethereum | py-ethereum | parity | hyperledger-besu |
-| -------------- | :----------: | :---------: | :---------: | :------: | :--------------: |
-| JSON-RPC 1.0 | ✓ | | | | |
-| JSON-RPC 2.0 | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Batch requests | ✓ | ✓ | ✓ | ✓ | ✓ |
-| HTTP | ✓ | ✓ | ✓ | ✓ | ✓ |
-| IPC | ✓ | ✓ | | ✓ | |
-| WS | | ✓ | | ✓ | ✓ |
-
-[View full list of Ethereum clients](/developers/docs/nodes-and-clients/#clients). We recommend checking the documentation of each client for the latest API support information.
-
-## Publish / Subscribe {#pub-sub}
-
-Publish / subscribe (pub/sub) is a method of using JSON-RPC notifications to subscribe to Ethereum events without needing to poll for them:
-
-- [Geth v1.4](https://geth.ethereum.org/docs/rpc/pubsub)
-
-- [Hyperledger Besu 1.3](https://besu.hyperledger.org/en/stable/HowTo/Interact/APIs/RPC-PubSub/)
-
-## HEX value encoding {#hex-value-encoding}
-
-At present there are two key datatypes that are passed over JSON: unformatted byte arrays and quantities. Both are passed with a hex encoding, however with different requirements to formatting:
-
-When encoding **QUANTITIES** (integers, numbers): encode as hex, prefix with "0x", the most compact representation (slight exception: zero should be represented as "0x0"). Examples:
-
-- 0x41 (65 in decimal)
-- 0x400 (1024 in decimal)
-- WRONG: 0x (should always have at least one digit - zero is "0x0")
-- WRONG: 0x0400 (no leading zeroes allowed)
-- WRONG: ff (must be prefixed 0x)
-
-When encoding **UNFORMATTED DATA** (byte arrays, account addresses, hashes, bytecode arrays): encode as hex, prefix with "0x", two hex digits per byte. Examples:
-
-- 0x41 (size 1, "A")
-- 0x004200 (size 3, "\0B\0")
-- 0x (size 0, "")
-- WRONG: 0xf0f0f (must be even number of digits)
-- WRONG: 004200 (must be prefixed 0x)
-
-Currently [aleth](https://github.com/ethereum/aleth), [go-ethereum](https://github.com/ethereum/go-ethereum), and [parity](https://github.com/paritytech/parity) provide JSON-RPC communication over http and IPC (unix socket Linux and OSX/named pipes on Windows). Version 1.4 of go-ethereum, version 1.6 of Parity and version 1.3 of Hyperledger Besu onwards have websocket support.
-
-## The default block parameter {#default-block-parameter}
-
-The following methods have an extra default block parameter:
-
-- [eth_getBalance](/developers/docs/apis/json-rpc/#eth_getbalance)
-- [eth_getCode](/developers/docs/apis/json-rpc/#eth_getcode)
-- [eth_getTransactionCount](/developers/docs/apis/json-rpc/#eth_gettransactioncount)
-- [eth_getStorageAt](/developers/docs/apis/json-rpc/#eth_getstorageat)
-- [eth_call](/developers/docs/apis/json-rpc/#eth_call)
-
-When requests are made that act on the state of Ethereum, the last default block parameter determines the height of the block.
-
-The following options are possible for the defaultBlock parameter:
-
-- `HEX String` - an integer block number
-- `String "earliest"` for the earliest/genesis block
-- `String "latest"` - for the latest mined block
-- `String "pending"` - for the pending state/transactions
-
-## Curl Examples Explained {#curl-examples-explained}
-
-The curl options below might return a response where the node complains about the content type, this is because the `--data` option sets the content type to `application/x-www-form-urlencoded`. If your node does complain, manually set the header by placing `-H "Content-Type: application/json"` at the start of the call.
-
-The examples also do not include the URL/IP & port combination which must be the last argument given to curl (e.x. `127.0.0.1:8545`)
-
-## Gossip, State, History {#gossip-state-history}
-
-A handful of core JSON-RPC methods require data from the Ethereum network, and fall neatly into three main categories: _Gossip, State, and History_. Use the links in these sections to jump to each method, or use the table of contents to explore the whole list of methods.
-
-### Gossip Methods {#gossip-methods}
-
-> These methods track the head of the chain. This is how transactions make their way around the network, find their way into blocks, and how clients find out about new blocks.
-
-- [eth_blockNumber](#eth_blocknumber)
-- [eth_sendRawTransaction](#eth_sendrawtransaction)
-
-### State Methods {#state_methods}
-
-> Methods that report the current state of all the data stored. The "state" is like one big shared piece of RAM, and includes account balances, contract data, and gas estimations.
-
-- [eth_getBalance](#eth_getbalance)
-- [eth_getStorageAt](#eth_getstorageat)
-- [eth_getTransactionCount](#eth_gettransactioncount)
-- [eth_getCode](#eth_getcode)
-- [eth_call](#eth_call)
-- [eth_estimateGas](#eth_estimategas)
-
-### History Methods {#history_methods}
-
-> Fetches historical records of every block back to genesis. This is like one large append-only file, and includes all block headers, block bodies, uncle blocks, and transaction receipts.
-
-- [eth_getBlockTransactionCountByHash](#eth_getblocktransactioncountbyhash)
-- [eth_getBlockTransactionCountByNumber](#eth_getblocktransactioncountbynumber)
-- [eth_getUncleCountByBlockHash](#eth_getunclecountbyblockhash)
-- [eth_getUncleCountByBlockNumber](#eth_getunclecountbyblocknumber)
-- [eth_getBlockByHash](#eth_getblockbyhash)
-- [eth_getBlockByNumber](#eth_getblockbynumber)
-- [eth_getTransactionByHash](#eth_gettransactionbyhash)
-- [eth_getTransactionByBlockHashAndIndex](#eth_gettransactionbyblockhashandindex)
-- [eth_getTransactionByBlockNumberAndIndex](#eth_gettransactionbyblocknumberandindex)
-- [eth_getTransactionReceipt](#eth_gettransactionreceipt)
-- [eth_getUncleByBlockHashAndIndex](#eth_getunclebyblockhashandindex)
-- [eth_getUncleByBlockNumberAndIndex](#eth_getunclebyblocknumberandindex)
-
-## JSON-RPC API Methods {#json-rpc-methods}
-
-### web3_clientVersion {#web3_clientversion}
-
-Returns the current client version.
-
-**Parameters**
-
-None
-
-**Returns**
-
-`String` - The current client version
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"web3_clientVersion","params":[],"id":67}'
-
-// Result
-{
- "id":67,
- "jsonrpc":"2.0",
- "result": "Mist/v0.9.3/darwin/go1.4.1"
-}
-```
-
-
-
-### web3_sha3 {#web3_sha3}
-
-Returns Keccak-256 (_not_ the standardized SHA3-256) of the given data.
-
-**Parameters**
-
-1. `DATA` - the data to convert into a SHA3 hash
-
-```js
-params: ["0x68656c6c6f20776f726c64"]
-```
-
-**Returns**
-
-`DATA` - The SHA3 result of the given string.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"web3_sha3","params":["0x68656c6c6f20776f726c64"],"id":64}'
-
-// Result
-{
- "id":64,
- "jsonrpc": "2.0",
- "result": "0x47173285a8d7341e5e972fc677286384f802f8ef42a5ec5f03bbfa254cb01fad"
-}
-```
-
-
-
-### net_version {#net_version}
-
-Returns the current network id.
-
-**Parameters**
-
-None
-
-**Returns**
-
-`String` - The current network id.
-
-- `"1"`: Ethereum Mainnet
-- `"2"`: Morden Testnet (deprecated)
-- `"3"`: Ropsten Testnet
-- `"4"`: Rinkeby Testnet
-- `"42"`: Kovan Testnet
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"net_version","params":[],"id":67}'
-
-// Result
-{
- "id":67,
- "jsonrpc": "2.0",
- "result": "3"
-}
-```
-
-
-
-### net_listening {#net_peercount}
-
-Returns `true` if client is actively listening for network connections.
-
-**Parameters**
-
-None
-
-**Returns**
-
-`Boolean` - `true` when listening, otherwise `false`.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"net_listening","params":[],"id":67}'
-
-// Result
-{
- "id":67,
- "jsonrpc":"2.0",
- "result":true
-}
-```
-
-
-
-### net_peerCount {#net_listening}
-
-Returns number of peers currently connected to the client.
-
-**Parameters**
-
-None
-
-**Returns**
-
-`QUANTITY` - integer of the number of connected peers.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"net_peerCount","params":[],"id":74}'
-
-// Result
-{
- "id":74,
- "jsonrpc": "2.0",
- "result": "0x2" // 2
-}
-```
-
-
-
-### eth_protocolVersion {#eth_protocolversion}
-
-Returns the current Ethereum protocol version.
-
-**Parameters**
-
-None
-
-**Returns**
-
-`String` - The current Ethereum protocol version
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_protocolVersion","params":[],"id":67}'
-
-// Result
-{
- "id":67,
- "jsonrpc": "2.0",
- "result": "54"
-}
-```
-
-
-
-### eth_syncing {#eth_syncing}
-
-Returns an object with data about the sync status or `false`.
-
-**Parameters**
-
-None
-
-**Returns**
-
-`Object|Boolean`, An object with sync status data or `FALSE`, when not syncing:
-
-- `startingBlock`: `QUANTITY` - The block at which the import started (will only be reset, after the sync reached his head)
-- `currentBlock`: `QUANTITY` - The current block, same as eth_blockNumber
-- `highestBlock`: `QUANTITY` - The estimated highest block
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": {
- startingBlock: '0x384',
- currentBlock: '0x386',
- highestBlock: '0x454'
- }
-}
-// Or when not syncing
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": false
-}
-```
-
-
-
-### eth_coinbase {#eth_coinbase}
-
-Returns the client coinbase address.
-
-**Parameters**
-
-None
-
-**Returns**
-
-`DATA`, 20 bytes - the current coinbase address.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_coinbase","params":[],"id":64}'
-
-// Result
-{
- "id":64,
- "jsonrpc": "2.0",
- "result": "0x407d73d8a49eeb85d32cf465507dd71d507100c1"
-}
-```
-
-
-
-### eth_mining {#eth_mining}
-
-Returns `true` if client is actively mining new blocks.
-
-**Parameters**
-
-None
-
-**Returns**
-
-`Boolean` - returns `true` of the client is mining, otherwise `false`.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_mining","params":[],"id":71}'
-
-// Result
-{
- "id":71,
- "jsonrpc": "2.0",
- "result": true
-}
-
-```
-
-
-
-### eth_hashrate {#eth_hashrate}
-
-Returns the number of hashes per second that the node is mining with.
-
-**Parameters**
-
-None
-
-**Returns**
-
-`QUANTITY` - number of hashes per second.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_hashrate","params":[],"id":71}'
-
-// Result
-{
- "id":71,
- "jsonrpc": "2.0",
- "result": "0x38a"
-}
-
-```
-
-
-
-### eth_gasPrice {#eth_gasprice}
-
-Returns the current price per gas in wei.
-
-**Parameters**
-
-None
-
-**Returns**
-
-`QUANTITY` - integer of the current gas price in wei.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_gasPrice","params":[],"id":73}'
-
-// Result
-{
- "id":73,
- "jsonrpc": "2.0",
- "result": "0x1dfd14000" // 8049999872 Wei
-}
-```
-
-
-
-### eth_accounts {#eth_accounts}
-
-Returns a list of addresses owned by client.
-
-**Parameters**
-
-None
-
-**Returns**
-
-`Array of DATA`, 20 Bytes - addresses owned by the client.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_accounts","params":[],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": ["0x407d73d8a49eeb85d32cf465507dd71d507100c1"]
-}
-```
-
-
-
-### eth_blockNumber {#eth_blocknumber}
-
-Returns the number of most recent block.
-
-**Parameters**
-
-None
-
-**Returns**
-
-`QUANTITY` - integer of the current block number the client is on.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":83}'
-
-// Result
-{
- "id":83,
- "jsonrpc": "2.0",
- "result": "0x4b7" // 1207
-}
-```
-
-
-
-### eth_getBalance {#eth_getbalance}
-
-Returns the balance of the account of given address.
-
-**Parameters**
-
-1. `DATA`, 20 Bytes - address to check for balance.
-2. `QUANTITY|TAG` - integer block number, or the string `"latest"`, `"earliest"` or `"pending"`, see the [default block parameter](/developers/docs/apis/json-rpc/#default-block-parameter)
-
-```js
-params: ["0x407d73d8a49eeb85d32cf465507dd71d507100c1", "latest"]
-```
-
-**Returns**
-
-`QUANTITY` - integer of the current balance in wei.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getBalance","params":["0x407d73d8a49eeb85d32cf465507dd71d507100c1", "latest"],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0x0234c8a3397aab58" // 158972490234375000
-}
-```
-
-
-
-### eth_getStorageAt {#eth_getstorageat}
-
-Returns the value from a storage position at a given address.
-
-**Parameters**
-
-1. `DATA`, 20 Bytes - address of the storage.
-2. `QUANTITY` - integer of the position in the storage.
-3. `QUANTITY|TAG` - integer block number, or the string `"latest"`, `"earliest"` or `"pending"`, see the [default block parameter](/developers/docs/apis/json-rpc/#default-block-parameter)
-
-**Returns**
-
-`DATA` - the value at this storage position.
-
-**Example**
-Calculating the correct position depends on the storage to retrieve. Consider the following contract deployed at `0x295a70b2de5e3953354a6a8344e616ed314d7251` by address `0x391694e7e0b0cce554cb130d723a9d27458f9298`.
-
-```
-contract Storage {
- uint pos0;
- mapping(address => uint) pos1;
-
- function Storage() {
- pos0 = 1234;
- pos1[msg.sender] = 5678;
- }
-}
-```
-
-Retrieving the value of pos0 is straight forward:
-
-```js
-curl -X POST --data '{"jsonrpc":"2.0", "method": "eth_getStorageAt", "params": ["0x295a70b2de5e3953354a6a8344e616ed314d7251", "0x0", "latest"], "id": 1}' localhost:8545
-
-{"jsonrpc":"2.0","id":1,"result":"0x00000000000000000000000000000000000000000000000000000000000004d2"}
-```
-
-Retrieving an element of the map is harder. The position of an element in the map is calculated with:
-
-```js
-keccack(LeftPad32(key, 0), LeftPad32(map position, 0))
-```
-
-This means to retrieve the storage on pos1["0x391694e7e0b0cce554cb130d723a9d27458f9298"] we need to calculate the position with:
-
-```js
-keccak(
- decodeHex(
- "000000000000000000000000391694e7e0b0cce554cb130d723a9d27458f9298" +
- "0000000000000000000000000000000000000000000000000000000000000001"
- )
-)
-```
-
-The geth console which comes with the web3 library can be used to make the calculation:
-
-```js
-> var key = "000000000000000000000000391694e7e0b0cce554cb130d723a9d27458f9298" + "0000000000000000000000000000000000000000000000000000000000000001"
-undefined
-> web3.sha3(key, {"encoding": "hex"})
-"0x6661e9d6d8b923d5bbaab1b96e1dd51ff6ea2a93520fdc9eb75d059238b8c5e9"
-```
-
-Now to fetch the storage:
-
-```js
-curl -X POST --data '{"jsonrpc":"2.0", "method": "eth_getStorageAt", "params": ["0x295a70b2de5e3953354a6a8344e616ed314d7251", "0x6661e9d6d8b923d5bbaab1b96e1dd51ff6ea2a93520fdc9eb75d059238b8c5e9", "latest"], "id": 1}' localhost:8545
-
-{"jsonrpc":"2.0","id":1,"result":"0x000000000000000000000000000000000000000000000000000000000000162e"}
-
-```
-
-
-
-### eth_getTransactionCount {#eth_gettransactioncount}
-
-Returns the number of transactions _sent_ from an address.
-
-**Parameters**
-
-1. `DATA`, 20 Bytes - address.
-2. `QUANTITY|TAG` - integer block number, or the string `"latest"`, `"earliest"` or `"pending"`, see the [default block parameter](/developers/docs/apis/json-rpc/#default-block-parameter)
-
-```js
-params: [
- "0x407d73d8a49eeb85d32cf465507dd71d507100c1",
- "latest", // state at the latest block
-]
-```
-
-**Returns**
-
-`QUANTITY` - integer of the number of transactions send from this address.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getTransactionCount","params":["0x407d73d8a49eeb85d32cf465507dd71d507100c1","latest"],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0x1" // 1
-}
-```
-
-
-
-### eth_getBlockTransactionCountByHash {#eth_getblocktransactioncountbyhash}
-
-Returns the number of transactions in a block from a block matching the given block hash.
-
-**Parameters**
-
-1. `DATA`, 32 Bytes - hash of a block
-
-```js
-params: ["0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238"]
-```
-
-**Returns**
-
-`QUANTITY` - integer of the number of transactions in this block.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getBlockTransactionCountByHash","params":["0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238"],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0xb" // 11
-}
-```
-
-
-
-### eth_getBlockTransactionCountByNumber {#eth_getblocktransactioncountbynumber}
-
-Returns the number of transactions in a block matching the given block number.
-
-**Parameters**
-
-1. `QUANTITY|TAG` - integer of a block number, or the string `"earliest"`, `"latest"` or `"pending"`, as in the [default block parameter](/developers/docs/apis/json-rpc/#default-block-parameter).
-
-```js
-params: [
- "0xe8", // 232
-]
-```
-
-**Returns**
-
-`QUANTITY` - integer of the number of transactions in this block.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getBlockTransactionCountByNumber","params":["0xe8"],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0xa" // 10
-}
-```
-
-
-
-### eth_getUncleCountByBlockHash {#eth_getunclecountbyblockhash}
-
-Returns the number of uncles in a block from a block matching the given block hash.
-
-**Parameters**
-
-1. `DATA`, 32 Bytes - hash of a block
-
-```js
-params: ["0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238"]
-```
-
-**Returns**
-
-`QUANTITY` - integer of the number of uncles in this block.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getUncleCountByBlockHash","params":["0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238"],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0x1" // 1
-}
-```
-
-
-
-### eth_getUncleCountByBlockNumber {#eth_getunclecountbyblocknumber}
-
-Returns the number of uncles in a block from a block matching the given block number.
-
-**Parameters**
-
-1. `QUANTITY|TAG` - integer of a block number, or the string "latest", "earliest" or "pending", see the [default block parameter](/developers/docs/apis/json-rpc/#default-block-parameter)
-
-```js
-params: [
- "0xe8", // 232
-]
-```
-
-**Returns**
-
-`QUANTITY` - integer of the number of uncles in this block.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getUncleCountByBlockNumber","params":["0xe8"],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0x1" // 1
-}
-```
-
-
-
-### eth_getCode {#eth_getcode}
-
-Returns code at a given address.
-
-**Parameters**
-
-1. `DATA`, 20 Bytes - address
-2. `QUANTITY|TAG` - integer block number, or the string `"latest"`, `"earliest"` or `"pending"`, see the [default block parameter](/developers/docs/apis/json-rpc/#default-block-parameter)
-
-```js
-params: [
- "0xa94f5374fce5edbc8e2a8697c15331677e6ebf0b",
- "0x2", // 2
-]
-```
-
-**Returns**
-
-`DATA` - the code from the given address.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getCode","params":["0xa94f5374fce5edbc8e2a8697c15331677e6ebf0b", "0x2"],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0x600160008035811a818181146012578301005b601b6001356025565b8060005260206000f25b600060078202905091905056"
-}
-```
-
-
-
-### eth_sign {#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 recognisable 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**
-
-1. `DATA`, 20 Bytes - address
-2. `DATA`, N Bytes - message to sign
-
-**Returns**
-
-`DATA`: Signature
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_sign","params":["0x9b2055d370f73ec7d8a03e965129118dc8f5bf83", "0xdeadbeaf"],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0xa3f20717a250c2b0b729b7e5becbff67fdaef7e0699da4de7ca5895b02a170a12d887fd3b17bfdce3481f10bea41f45ba9f709d39ce8325427b57afcfc994cee1b"
-}
-```
-
-
-
-### eth_signTransaction {#eth_signtransaction}
-
-Signs a transaction that can be submitted to the network at a later time using with [eth_sendRawTransaction](#eth_sendrawtransaction).
-
-**Parameters**
-
-1. `Object` - The transaction object
-
-- `from`: `DATA`, 20 Bytes - The address the transaction is sent from.
-- `to`: `DATA`, 20 Bytes - (optional when creating new contract) The address the transaction is directed to.
-- `gas`: `QUANTITY` - (optional, default: 90000) Integer of the gas provided for the transaction execution. It will return unused gas.
-- `gasPrice`: `QUANTITY` - (optional, default: To-Be-Determined) Integer of the gasPrice used for each paid gas, in Wei.
-- `value`: `QUANTITY` - (optional) Integer of the value sent with this transaction, in Wei.
-- `data`: `DATA` - The compiled code of a contract OR the hash of the invoked method signature and encoded parameters.
-- `nonce`: `QUANTITY` - (optional) Integer of a nonce. This allows to overwrite your own pending transactions that use the same nonce.
-
-**Returns**
-
-`DATA`, The signed transaction object.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"id": 1,"jsonrpc": "2.0","method": "eth_signTransaction","params": [{"data":"0xd46e8dd67c5d32be8d46e8dd67c5d32be8058bb8eb970870f072445675058bb8eb970870f072445675","from": "0xb60e8dd61c5d32be8058bb8eb970870f07233155","gas": "0x76c0","gasPrice": "0x9184e72a000","to": "0xd46e8dd67c5d32be8058bb8eb970870f07244567","value": "0x9184e72a"}]}'
-
-// Result
-{
- "id": 1,
- "jsonrpc": "2.0",
- "result": "0xa3f20717a250c2b0b729b7e5becbff67fdaef7e0699da4de7ca5895b02a170a12d887fd3b17bfdce3481f10bea41f45ba9f709d39ce8325427b57afcfc994cee1b"
-}
-```
-
-
-
-### eth_sendTransaction {#eth_sendtransaction}
-
-Creates new message call transaction or a contract creation, if the data field contains code.
-
-**Parameters**
-
-1. `Object` - The transaction object
-
-- `from`: `DATA`, 20 Bytes - The address the transaction is sent from.
-- `to`: `DATA`, 20 Bytes - (optional when creating new contract) The address the transaction is directed to.
-- `gas`: `QUANTITY` - (optional, default: 90000) Integer of the gas provided for the transaction execution. It will return unused gas.
-- `gasPrice`: `QUANTITY` - (optional, default: To-Be-Determined) Integer of the gasPrice used for each paid gas.
-- `value`: `QUANTITY` - (optional) Integer of the value sent with this transaction.
-- `data`: `DATA` - The compiled code of a contract OR the hash of the invoked method signature and encoded parameters.
-- `nonce`: `QUANTITY` - (optional) Integer of a nonce. This allows to overwrite your own pending transactions that use the same nonce.
-
-```js
-params: [
- {
- from: "0xb60e8dd61c5d32be8058bb8eb970870f07233155",
- to: "0xd46e8dd67c5d32be8058bb8eb970870f07244567",
- gas: "0x76c0", // 30400
- gasPrice: "0x9184e72a000", // 10000000000000
- value: "0x9184e72a", // 2441406250
- data:
- "0xd46e8dd67c5d32be8d46e8dd67c5d32be8058bb8eb970870f072445675058bb8eb970870f072445675",
- },
-]
-```
-
-**Returns**
-
-`DATA`, 32 Bytes - the transaction hash, or the zero hash if the transaction is not yet available.
-
-Use [eth_getTransactionReceipt](#eth_gettransactionreceipt) to get the contract address, after the transaction was mined, when you created a contract.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_sendTransaction","params":[{see above}],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331"
-}
-```
-
-
-
-### eth_sendRawTransaction {#eth_sendrawtransaction}
-
-Creates new message call transaction or a contract creation for signed transactions.
-
-**Parameters**
-
-1. `DATA`, The signed transaction data.
-
-```js
-params: [
- "0xd46e8dd67c5d32be8d46e8dd67c5d32be8058bb8eb970870f072445675058bb8eb970870f072445675",
-]
-```
-
-**Returns**
-
-`DATA`, 32 Bytes - the transaction hash, or the zero hash if the transaction is not yet available.
-
-Use [eth_getTransactionReceipt](#eth_gettransactionreceipt) to get the contract address, after the transaction was mined, when you created a contract.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_sendRawTransaction","params":[{see above}],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331"
-}
-```
-
-
-
-### eth_call {#eth_call}
-
-Executes a new message call immediately without creating a transaction on the block chain.
-
-**Parameters**
-
-1. `Object` - The transaction call object
-
-- `from`: `DATA`, 20 Bytes - (optional) The address the transaction is sent from.
-- `to`: `DATA`, 20 Bytes - The address the transaction is directed to.
-- `gas`: `QUANTITY` - (optional) Integer of the gas provided for the transaction execution. eth_call consumes zero gas, but this parameter may be needed by some executions.
-- `gasPrice`: `QUANTITY` - (optional) Integer of the gasPrice used for each paid gas
-- `value`: `QUANTITY` - (optional) Integer of the value sent with this transaction
-- `data`: `DATA` - (optional) Hash of the method signature and encoded parameters. For details see [Ethereum Contract ABI in the Solidity documentation](https://docs.soliditylang.org/en/latest/abi-spec.html)
-
-2. `QUANTITY|TAG` - integer block number, or the string `"latest"`, `"earliest"` or `"pending"`, see the [default block parameter](/developers/docs/apis/json-rpc/#default-block-parameter)
-
-**Returns**
-
-`DATA` - the return value of executed contract.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_call","params":[{see above}],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0x"
-}
-```
-
-
-
-### eth_estimateGas {#eth_estimategas}
-
-Generates and returns an estimate of how much gas is necessary to allow the transaction to complete. The transaction will not be added to the blockchain. Note that the estimate may be significantly more than the amount of gas actually used by the transaction, for a variety of reasons including EVM mechanics and node performance.
-
-**Parameters**
-
-See [eth_call](#eth_call) parameters, expect that all properties are optional. If no gas limit is specified geth uses the block gas limit from the pending block as an upper bound. As a result the returned estimate might not be enough to executed the call/transaction when the amount of gas is higher than the pending block gas limit.
-
-**Returns**
-
-`QUANTITY` - the amount of gas used.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_estimateGas","params":[{see above}],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0x5208" // 21000
-}
-```
-
-
-
-### eth_getBlockByHash {#eth_getblockbyhash}
-
-Returns information about a block by hash.
-
-**Parameters**
-
-1. `DATA`, 32 Bytes - Hash of a block.
-2. `Boolean` - If `true` it returns the full transaction objects, if `false` only the hashes of the transactions.
-
-```js
-params: [
- "0xdc0818cf78f21a8e70579cb46a43643f78291264dda342ae31049421c82d21ae",
- false,
-]
-```
-
-**Returns**
-
-`Object` - A block object, or `null` when no block was found:
-
-- `number`: `QUANTITY` - the block number. `null` when its pending block.
-- `hash`: `DATA`, 32 Bytes - hash of the block. `null` when its pending block.
-- `parentHash`: `DATA`, 32 Bytes - hash of the parent block.
-- `nonce`: `DATA`, 8 Bytes - hash of the generated proof-of-work. `null` when its pending block.
-- `sha3Uncles`: `DATA`, 32 Bytes - SHA3 of the uncles data in the block.
-- `logsBloom`: `DATA`, 256 Bytes - the bloom filter for the logs of the block. `null` when its pending block.
-- `transactionsRoot`: `DATA`, 32 Bytes - the root of the transaction trie of the block.
-- `stateRoot`: `DATA`, 32 Bytes - the root of the final state trie of the block.
-- `receiptsRoot`: `DATA`, 32 Bytes - the root of the receipts trie of the block.
-- `miner`: `DATA`, 20 Bytes - the address of the beneficiary to whom the mining rewards were given.
-- `difficulty`: `QUANTITY` - integer of the difficulty for this block.
-- `totalDifficulty`: `QUANTITY` - integer of the total difficulty of the chain until this block.
-- `extraData`: `DATA` - the "extra data" field of this block.
-- `size`: `QUANTITY` - integer the size of this block in bytes.
-- `gasLimit`: `QUANTITY` - the maximum gas allowed in this block.
-- `gasUsed`: `QUANTITY` - the total used gas by all transactions in this block.
-- `timestamp`: `QUANTITY` - the unix timestamp for when the block was collated.
-- `transactions`: `Array` - Array of transaction objects, or 32 Bytes transaction hashes depending on the last given parameter.
-- `uncles`: `Array` - Array of uncle hashes.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getBlockByHash","params":["0xdc0818cf78f21a8e70579cb46a43643f78291264dda342ae31049421c82d21ae", false],"id":1}'
-
-// Result
-{
-{
- "jsonrpc": "2.0",
- "id": 1,
- "result": {
- "difficulty": "0x4ea3f27bc",
- "extraData": "0x476574682f4c5649562f76312e302e302f6c696e75782f676f312e342e32",
- "gasLimit": "0x1388",
- "gasUsed": "0x0",
- "hash": "0xdc0818cf78f21a8e70579cb46a43643f78291264dda342ae31049421c82d21ae",
- "logsBloom": "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
- "miner": "0xbb7b8287f3f0a933474a79eae42cbca977791171",
- "mixHash": "0x4fffe9ae21f1c9e15207b1f472d5bbdd68c9595d461666602f2be20daf5e7843",
- "nonce": "0x689056015818adbe",
- "number": "0x1b4",
- "parentHash": "0xe99e022112df268087ea7eafaf4790497fd21dbeeb6bd7a1721df161a6657a54",
- "receiptsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
- "sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
- "size": "0x220",
- "stateRoot": "0xddc8b0234c2e0cad087c8b389aa7ef01f7d79b2570bccb77ce48648aa61c904d",
- "timestamp": "0x55ba467c",
- "totalDifficulty": "0x78ed983323d",
- "transactions": [
- ],
- "transactionsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
- "uncles": [
- ]
- }
-}
-```
-
-
-
-### eth_getBlockByNumber {#eth_getblockbynumber}
-
-Returns information about a block by block number.
-
-**Parameters**
-
-1. `QUANTITY|TAG` - integer of a block number, or the string `"earliest"`, `"latest"` or `"pending"`, as in the [default block parameter](/developers/docs/apis/json-rpc/#default-block-parameter).
-2. `Boolean` - If `true` it returns the full transaction objects, if `false` only the hashes of the transactions.
-
-```js
-params: [
- "0x1b4", // 436
- true,
-]
-```
-
-**Returns**
-
-See [eth_getBlockByHash](#eth_getblockbyhash)
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["0x1b4", true],"id":1}'
-```
-
-Result see [eth_getBlockByHash](#eth_getblockbyhash)
-
-
-
-### eth_getTransactionByHash {#eth_gettransactionbyhash}
-
-Returns the information about a transaction requested by transaction hash.
-
-**Parameters**
-
-1. `DATA`, 32 Bytes - hash of a transaction
-
-```js
-params: ["0x88df016429689c079f3b2f6ad39fa052532c56795b733da78a91ebe6a713944b"]
-```
-
-**Returns**
-
-`Object` - A transaction object, or `null` when no transaction was found:
-
-- `blockHash`: `DATA`, 32 Bytes - hash of the block where this transaction was in. `null` when its pending.
-- `blockNumber`: `QUANTITY` - block number where this transaction was in. `null` when its pending.
-- `from`: `DATA`, 20 Bytes - address of the sender.
-- `gas`: `QUANTITY` - gas provided by the sender.
-- `gasPrice`: `QUANTITY` - gas price provided by the sender in Wei.
-- `hash`: `DATA`, 32 Bytes - hash of the transaction.
-- `input`: `DATA` - the data send along with the transaction.
-- `nonce`: `QUANTITY` - the number of transactions made by the sender prior to this one.
-- `to`: `DATA`, 20 Bytes - address of the receiver. `null` when its a contract creation transaction.
-- `transactionIndex`: `QUANTITY` - integer of the transactions index position in the block. `null` when its pending.
-- `value`: `QUANTITY` - value transferred in Wei.
-- `v`: `QUANTITY` - ECDSA recovery id
-- `r`: `QUANTITY` - ECDSA signature r
-- `s`: `QUANTITY` - ECDSA signature s
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getTransactionByHash","params":["0x88df016429689c079f3b2f6ad39fa052532c56795b733da78a91ebe6a713944b"],"id":1}'
-
-// Result
-{
- "jsonrpc":"2.0",
- "id":1,
- "result":{
- "blockHash":"0x1d59ff54b1eb26b013ce3cb5fc9dab3705b415a67127a003c3e61eb445bb8df2",
- "blockNumber":"0x5daf3b", // 6139707
- "from":"0xa7d9ddbe1f17865597fbd27ec712455208b6b76d",
- "gas":"0xc350", // 50000
- "gasPrice":"0x4a817c800", // 20000000000
- "hash":"0x88df016429689c079f3b2f6ad39fa052532c56795b733da78a91ebe6a713944b",
- "input":"0x68656c6c6f21",
- "nonce":"0x15", // 21
- "to":"0xf02c1c8e6114b1dbe8937a39260b5b0a374432bb",
- "transactionIndex":"0x41", // 65
- "value":"0xf3dbb76162000", // 4290000000000000
- "v":"0x25", // 37
- "r":"0x1b5e176d927f8e9ab405058b2d2457392da3e20f328b16ddabcebc33eaac5fea",
- "s":"0x4ba69724e8f69de52f0125ad8b3c5c2cef33019bac3249e2c0a2192766d1721c"
- }
-}
-```
-
-
-
-### eth_getTransactionByBlockHashAndIndex {#eth_gettransactionbyblockhashandindex}
-
-Returns information about a transaction by block hash and transaction index position.
-
-**Parameters**
-
-1. `DATA`, 32 Bytes - hash of a block.
-2. `QUANTITY` - integer of the transaction index position.
-
-```js
-params: [
- "0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331",
- "0x0", // 0
-]
-```
-
-**Returns**
-
-See [eth_getTransactionByHash](#eth_gettransactionbyhash)
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getTransactionByBlockHashAndIndex","params":["0xc6ef2fc5426d6ad6fd9e2a26abeab0aa2411b7ab17f30a99d3cb96aed1d1055b", "0x0"],"id":1}'
-```
-
-Result see [eth_getTransactionByHash](#eth_gettransactionbyhash)
-
-
-
-### eth_getTransactionByBlockNumberAndIndex {#eth_gettransactionbyblocknumberandindex}
-
-Returns information about a transaction by block number and transaction index position.
-
-**Parameters**
-
-1. `QUANTITY|TAG` - a block number, or the string `"earliest"`, `"latest"` or `"pending"`, as in the [default block parameter](/developers/docs/apis/json-rpc/#default-block-parameter).
-2. `QUANTITY` - the transaction index position.
-
-```js
-params: [
- "0x29c", // 668
- "0x0", // 0
-]
-```
-
-**Returns**
-
-See [eth_getTransactionByHash](#eth_gettransactionbyhash)
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getTransactionByBlockNumberAndIndex","params":["0x29c", "0x0"],"id":1}'
-```
-
-Result see [eth_getTransactionByHash](#eth_gettransactionbyhash)
-
-
-
-### eth_getTransactionReceipt {#eth_gettransactionreceipt}
-
-Returns the receipt of a transaction by transaction hash.
-
-**Note** That the receipt is not available for pending transactions.
-
-**Parameters**
-
-1. `DATA`, 32 Bytes - hash of a transaction
-
-```js
-params: ["0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238"]
-```
-
-**Returns**
-
-`Object` - A transaction receipt object, or `null` when no receipt was found:
-
-- `transactionHash `: `DATA`, 32 Bytes - hash of the transaction.
-- `transactionIndex`: `QUANTITY` - integer of the transactions index position in the block.
-- `blockHash`: `DATA`, 32 Bytes - hash of the block where this transaction was in.
-- `blockNumber`: `QUANTITY` - block number where this transaction was in.
-- `from`: `DATA`, 20 Bytes - address of the sender.
-- `to`: `DATA`, 20 Bytes - address of the receiver. null when its a contract creation transaction.
-- `cumulativeGasUsed `: `QUANTITY ` - The total amount of gas used when this transaction was executed in the block.
-- `gasUsed `: `QUANTITY ` - The amount of gas used by this specific transaction alone.
-- `contractAddress `: `DATA`, 20 Bytes - The contract address created, if the transaction was a contract creation, otherwise `null`.
-- `logs`: `Array` - Array of log objects, which this transaction generated.
-- `logsBloom`: `DATA`, 256 Bytes - Bloom filter for light clients to quickly retrieve related logs.
-
-It also returns _either_ :
-
-- `root` : `DATA` 32 bytes of post-transaction stateroot (pre Byzantium)
-- `status`: `QUANTITY` either `1` (success) or `0` (failure)
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getTransactionReceipt","params":["0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238"],"id":1}'
-
-// Result
-{
-"id":1,
-"jsonrpc":"2.0",
-"result": {
- transactionHash: '0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238',
- transactionIndex: '0x1', // 1
- blockNumber: '0xb', // 11
- blockHash: '0xc6ef2fc5426d6ad6fd9e2a26abeab0aa2411b7ab17f30a99d3cb96aed1d1055b',
- cumulativeGasUsed: '0x33bc', // 13244
- gasUsed: '0x4dc', // 1244
- contractAddress: '0xb60e8dd61c5d32be8058bb8eb970870f07233155', // or null, if none was created
- logs: [{
- // logs as returned by getFilterLogs, etc.
- }, ...],
- logsBloom: "0x00...0", // 256 byte bloom filter
- status: '0x1'
- }
-}
-```
-
-
-
-### eth_getUncleByBlockHashAndIndex {#eth_getunclebyblockhashandindex}
-
-Returns information about a uncle of a block by hash and uncle index position.
-
-**Parameters**
-
-1. `DATA`, 32 Bytes - The hash of a block.
-2. `QUANTITY` - The uncle's index position.
-
-```js
-params: [
- "0xc6ef2fc5426d6ad6fd9e2a26abeab0aa2411b7ab17f30a99d3cb96aed1d1055b",
- "0x0", // 0
-]
-```
-
-**Returns**
-
-See [eth_getBlockByHash](#eth_getblockbyhash)
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getUncleByBlockHashAndIndex","params":["0xc6ef2fc5426d6ad6fd9e2a26abeab0aa2411b7ab17f30a99d3cb96aed1d1055b", "0x0"],"id":1}'
-```
-
-Result see [eth_getBlockByHash](#eth_getblockbyhash)
-
-**Note**: An uncle doesn't contain individual transactions.
-
-
-
-### eth_getUncleByBlockNumberAndIndex {#eth_getunclebyblocknumberandindex}
-
-Returns information about a uncle of a block by number and uncle index position.
-
-**Parameters**
-
-1. `QUANTITY|TAG` - a block number, or the string `"earliest"`, `"latest"` or `"pending"`, as in the [default block parameter](/developers/docs/apis/json-rpc/#default-block-parameter).
-2. `QUANTITY` - the uncle's index position.
-
-```js
-params: [
- "0x29c", // 668
- "0x0", // 0
-]
-```
-
-**Returns**
-
-See [eth_getBlockByHash](#eth_getblockbyhash)
-
-**Note**: An uncle doesn't contain individual transactions.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getUncleByBlockNumberAndIndex","params":["0x29c", "0x0"],"id":1}'
-```
-
-Result see [eth_getBlockByHash](#eth_getblockbyhash)
-
-
-
-### eth_getCompilers {#eth_getcompilers}
-
-Returns a list of available compilers in the client.
-
-**Parameters**
-
-None
-
-**Returns**
-
-`Array` - Array of available compilers.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getCompilers","params":[],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": ["solidity", "lll", "serpent"]
-}
-```
-
-
-
-### eth_compileSolidity {#eth_compilelll}
-
-Returns compiled solidity code.
-
-**Parameters**
-
-1. `String` - The source code.
-
-```js
-params: [
- "contract test { function multiply(uint a) returns(uint d) { return a * 7; } }",
-]
-```
-
-**Returns**
-
-`DATA` - The compiled source code.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_compileSolidity","params":["contract test { function multiply(uint a) returns(uint d) { return a * 7; } }"],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": {
- "code": "0x605880600c6000396000f3006000357c010000000000000000000000000000000000000000000000000000000090048063c6888fa114602e57005b603d6004803590602001506047565b8060005260206000f35b60006007820290506053565b91905056",
- "info": {
- "source": "contract test {\n function multiply(uint a) constant returns(uint d) {\n return a * 7;\n }\n}\n",
- "language": "Solidity",
- "languageVersion": "0",
- "compilerVersion": "0.9.19",
- "abiDefinition": [
- {
- "constant": true,
- "inputs": [
- {
- "name": "a",
- "type": "uint256"
- }
- ],
- "name": "multiply",
- "outputs": [
- {
- "name": "d",
- "type": "uint256"
- }
- ],
- "type": "function"
- }
- ],
- "userDoc": {
- "methods": {}
- },
- "developerDoc": {
- "methods": {}
- }
- }
-
-}
-```
-
-
-
-### eth_compileLLL {#eth_compilesolidity}
-
-Returns compiled LLL code.
-
-**Parameters**
-
-1. `String` - The source code.
-
-```js
-params: ["(returnlll (suicide (caller)))"]
-```
-
-**Returns**
-
-`DATA` - The compiled source code.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_compileLLL","params":["(returnlll (suicide (caller)))"],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0x603880600c6000396000f3006001600060e060020a600035048063c6888fa114601857005b6021600435602b565b8060005260206000f35b600081600702905091905056" // the compiled source code
-}
-```
-
-
-
-### eth_compileSerpent {#eth_compileserpent}
-
-Returns compiled serpent code.
-
-**Parameters**
-
-1. `String` - The source code.
-
-```js
-params: ["/* some serpent */"]
-```
-
-**Returns**
-
-`DATA` - The compiled source code.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_compileSerpent","params":["/* some serpent */"],"id":1}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0x603880600c6000396000f3006001600060e060020a600035048063c6888fa114601857005b6021600435602b565b8060005260206000f35b600081600702905091905056" // the compiled source code
-}
-```
-
-
-
-### eth_newFilter {#eth_newfilter}
-
-Creates a filter object, based on filter options, to notify when the state changes (logs).
-To check if the state has changed, call [eth_getFilterChanges](#eth_getfilterchanges).
-
-**A note on specifying topic filters:**
-Topics are order-dependent. A transaction with a log with topics [A, B] will be matched by the following topic filters:
-
-- `[]` "anything"
-- `[A]` "A in first position (and anything after)"
-- `[null, B]` "anything in first position AND B in second position (and anything after)"
-- `[A, B]` "A in first position AND B in second position (and anything after)"
-- `[[A, B], [A, B]]` "(A OR B) in first position AND (A OR B) in second position (and anything after)"
-
-**Parameters**
-
-1. `Object` - The filter options:
-
-- `fromBlock`: `QUANTITY|TAG` - (optional, default: `"latest"`) Integer block number, or `"latest"` for the last mined block or `"pending"`, `"earliest"` for not yet mined transactions.
-- `toBlock`: `QUANTITY|TAG` - (optional, default: `"latest"`) Integer block number, or `"latest"` for the last mined block or `"pending"`, `"earliest"` for not yet mined transactions.
-- `address`: `DATA|Array`, 20 Bytes - (optional) Contract address or a list of addresses from which logs should originate.
-- `topics`: `Array of DATA`, - (optional) Array of 32 Bytes `DATA` topics. Topics are order-dependent. Each topic can also be an array of DATA with "or" options.
-
-```js
-params: [
- {
- fromBlock: "0x1",
- toBlock: "0x2",
- address: "0x8888f1f195afa192cfee860698584c030f4c9db1",
- topics: [
- "0x000000000000000000000000a94f5374fce5edbc8e2a8697c15331677e6ebf0b",
- null,
- [
- "0x000000000000000000000000a94f5374fce5edbc8e2a8697c15331677e6ebf0b",
- "0x0000000000000000000000000aff3454fce5edbc8cca8697c15331677e6ebccc",
- ],
- ],
- },
-]
-```
-
-**Returns**
-
-`QUANTITY` - A filter id.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_newFilter","params":[{"topics":["0x12341234"]}],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0x1" // 1
-}
-```
-
-
-
-### eth_newBlockFilter {#eth_newblockfilter}
-
-Creates a filter in the node, to notify when a new block arrives.
-To check if the state has changed, call [eth_getFilterChanges](#eth_getfilterchanges).
-
-**Parameters**
-
-None
-
-**Returns**
-
-`QUANTITY` - A filter id.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_newBlockFilter","params":[],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0x1" // 1
-}
-```
-
-
-
-### eth_newPendingTransactionFilter {#eth_newpendingtransactionfilter}
-
-Creates a filter in the node, to notify when new pending transactions arrive.
-To check if the state has changed, call [eth_getFilterChanges](#eth_getfilterchanges).
-
-**Parameters**
-
-None
-
-**Returns**
-
-`QUANTITY` - A filter id.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_newPendingTransactionFilter","params":[],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0x1" // 1
-}
-```
-
-
-
-### eth_uninstallFilter {#eth_uninstallfilter}
-
-Uninstalls a filter with given id. Should always be called when watch is no longer needed.
-Additonally Filters timeout when they aren't requested with [eth_getFilterChanges](#eth_getfilterchanges) for a period of time.
-
-**Parameters**
-
-1. `QUANTITY` - The filter id.
-
-```js
-params: [
- "0xb", // 11
-]
-```
-
-**Returns**
-
-`Boolean` - `true` if the filter was successfully uninstalled, otherwise `false`.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_uninstallFilter","params":["0xb"],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": true
-}
-```
-
-
-
-### eth_getFilterChanges {#eth_getfilterchanges}
-
-Polling method for a filter, which returns an array of logs which occurred since last poll.
-
-**Parameters**
-
-1. `QUANTITY` - the filter id.
-
-```js
-params: [
- "0x16", // 22
-]
-```
-
-**Returns**
-
-`Array` - Array of log objects, or an empty array if nothing has changed since last poll.
-
-- For filters created with `eth_newBlockFilter` the return are block hashes (`DATA`, 32 Bytes), e.g. `["0x3454645634534..."]`.
-- For filters created with `eth_newPendingTransactionFilter ` the return are transaction hashes (`DATA`, 32 Bytes), e.g. `["0x6345343454645..."]`.
-- For filters created with `eth_newFilter` logs are objects with following params:
-
- - `removed`: `TAG` - `true` when the log was removed, due to a chain reorganization. `false` if its a valid log.
- - `logIndex`: `QUANTITY` - integer of the log index position in the block. `null` when its pending log.
- - `transactionIndex`: `QUANTITY` - integer of the transactions index position log was created from. `null` when its pending log.
- - `transactionHash`: `DATA`, 32 Bytes - hash of the transactions this log was created from. `null` when its pending log.
- - `blockHash`: `DATA`, 32 Bytes - hash of the block where this log was in. `null` when its pending. `null` when its pending log.
- - `blockNumber`: `QUANTITY` - the block number where this log was in. `null` when its pending. `null` when its pending log.
- - `address`: `DATA`, 20 Bytes - address from which this log originated.
- - `data`: `DATA` - contains one or more 32 Bytes non-indexed arguments of the log.
- - `topics`: `Array of DATA` - Array of 0 to 4 32 Bytes `DATA` of indexed log arguments. (In _solidity_: The first topic is the _hash_ of the signature of the event (e.g. `Deposit(address,bytes32,uint256)`), except you declared the event with the `anonymous` specifier.)
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getFilterChanges","params":["0x16"],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc":"2.0",
- "result": [{
- "logIndex": "0x1", // 1
- "blockNumber":"0x1b4", // 436
- "blockHash": "0x8216c5785ac562ff41e2dcfdf5785ac562ff41e2dcfdf829c5a142f1fccd7d",
- "transactionHash": "0xdf829c5a142f1fccd7d8216c5785ac562ff41e2dcfdf5785ac562ff41e2dcf",
- "transactionIndex": "0x0", // 0
- "address": "0x16c5785ac562ff41e2dcfdf829c5a142f1fccd7d",
- "data":"0x0000000000000000000000000000000000000000000000000000000000000000",
- "topics": ["0x59ebeb90bc63057b6515673c3ecf9438e5058bca0f92585014eced636878c9a5"]
- },{
- ...
- }]
-}
-```
-
-
-
-### eth_getFilterLogs {#eth_getfilterlogs}
-
-Returns an array of all logs matching filter with given id.
-
-**Parameters**
-
-1. `QUANTITY` - The filter id.
-
-```js
-params: [
- "0x16", // 22
-]
-```
-
-**Returns**
-
-See [eth_getFilterChanges](#eth_getfilterchanges)
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getFilterLogs","params":["0x16"],"id":74}'
-```
-
-Result see [eth_getFilterChanges](#eth_getfilterchanges)
-
-
-
-### eth_getLogs {#eth_getlogs}
-
-Returns an array of all logs matching a given filter object.
-
-**Parameters**
-
-1. `Object` - The filter options:
-
-- `fromBlock`: `QUANTITY|TAG` - (optional, default: `"latest"`) Integer block number, or `"latest"` for the last mined block or `"pending"`, `"earliest"` for not yet mined transactions.
-- `toBlock`: `QUANTITY|TAG` - (optional, default: `"latest"`) Integer block number, or `"latest"` for the last mined block or `"pending"`, `"earliest"` for not yet mined transactions.
-- `address`: `DATA|Array`, 20 Bytes - (optional) Contract address or a list of addresses from which logs should originate.
-- `topics`: `Array of DATA`, - (optional) Array of 32 Bytes `DATA` topics. Topics are order-dependent. Each topic can also be an array of DATA with "or" options.
-- `blockhash`: `DATA`, 32 Bytes - (optional, **future**) With the addition of EIP-234, `blockHash` will be a new filter option which restricts the logs returned to the single block with the 32-byte hash `blockHash`. Using `blockHash` is equivalent to `fromBlock` = `toBlock` = the block number with hash `blockHash`. If `blockHash` is present in in the filter criteria, then neither `fromBlock` nor `toBlock` are allowed.
-
-```js
-params: [
- {
- topics: [
- "0x000000000000000000000000a94f5374fce5edbc8e2a8697c15331677e6ebf0b",
- ],
- },
-]
-```
-
-**Returns**
-
-See [eth_getFilterChanges](#eth_getfilterchanges)
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getLogs","params":[{"topics":["0x000000000000000000000000a94f5374fce5edbc8e2a8697c15331677e6ebf0b"]}],"id":74}'
-```
-
-Result see [eth_getFilterChanges](#eth_getfilterchanges)
-
-
-
-### eth_getWork {#eth_getwork}
-
-Returns the hash of the current block, the seedHash, and the boundary condition to be met ("target").
-
-**Parameters**
-
-None
-
-**Returns**
-
-`Array` - Array with the following properties:
-
-1. `DATA`, 32 Bytes - current block header pow-hash
-2. `DATA`, 32 Bytes - the seed hash used for the DAG.
-3. `DATA`, 32 Bytes - the boundary condition ("target"), 2^256 / difficulty.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getWork","params":[],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc":"2.0",
- "result": [
- "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef",
- "0x5EED00000000000000000000000000005EED0000000000000000000000000000",
- "0xd1ff1c01710000000000000000000000d1ff1c01710000000000000000000000"
- ]
-}
-```
-
-
-
-### eth_submitWork {#eth_submitwork}
-
-Used for submitting a proof-of-work solution.
-
-**Parameters**
-
-1. `DATA`, 8 Bytes - The nonce found (64 bits)
-2. `DATA`, 32 Bytes - The header's pow-hash (256 bits)
-3. `DATA`, 32 Bytes - The mix digest (256 bits)
-
-```js
-params: [
- "0x0000000000000001",
- "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef",
- "0xD1FE5700000000000000000000000000D1FE5700000000000000000000000000",
-]
-```
-
-**Returns**
-
-`Boolean` - returns `true` if the provided solution is valid, otherwise `false`.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0", "method":"eth_submitWork", "params":["0x0000000000000001", "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef", "0xD1GE5700000000000000000000000000D1GE5700000000000000000000000000"],"id":73}'
-
-// Result
-{
- "id":73,
- "jsonrpc":"2.0",
- "result": true
-}
-```
-
-
-
-### eth_submitHashrate {#eth_submithashrate}
-
-Used for submitting mining hashrate.
-
-**Parameters**
-
-1. `Hashrate`, a hexadecimal string representation (32 bytes) of the hash rate
-2. `ID`, String - A random hexadecimal(32 bytes) ID identifying the client
-
-```js
-params: [
- "0x0000000000000000000000000000000000000000000000000000000000500000",
- "0x59daa26581d0acd1fce254fb7e85952f4c09d0915afd33d3886cd914bc7d283c",
-]
-```
-
-**Returns**
-
-`Boolean` - returns `true` if submitting went through successfully and `false` otherwise.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0", "method":"eth_submitHashrate", "params":["0x0000000000000000000000000000000000000000000000000000000000500000", "0x59daa26581d0acd1fce254fb7e85952f4c09d0915afd33d3886cd914bc7d283c"],"id":73}'
-
-// Result
-{
- "id":73,
- "jsonrpc":"2.0",
- "result": true
-}
-```
-
-
-
-### db_putString {#db_putstring}
-
-Stores a string in the local database.
-
-**Note** this function is deprecated and will be removed in the future.
-
-**Parameters**
-
-1. `String` - Database name.
-2. `String` - Key name.
-3. `String` - String to store.
-
-```js
-params: ["testDB", "myKey", "myString"]
-```
-
-**Returns**
-
-`Boolean` - returns `true` if the value was stored, otherwise `false`.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"db_putString","params":["testDB","myKey","myString"],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc":"2.0",
- "result": true
-}
-```
-
-
-
-### db_getString {#db_getstring}
-
-Returns string from the local database.
-
-**Note** this function is deprecated and will be removed in the future.
-
-**Parameters**
-
-1. `String` - Database name.
-2. `String` - Key name.
-
-```js
-params: ["testDB", "myKey"]
-```
-
-**Returns**
-
-`String` - The previously stored string.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"db_getString","params":["testDB","myKey"],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc":"2.0",
- "result": "myString"
-}
-```
-
-
-
-### db_putHex {#db_puthex}
-
-Stores binary data in the local database.
-
-**Note** this function is deprecated and will be removed in the future.
-
-**Parameters**
-
-1. `String` - Database name.
-2. `String` - Key name.
-3. `DATA` - The data to store.
-
-```js
-params: ["testDB", "myKey", "0x68656c6c6f20776f726c64"]
-```
-
-**Returns**
-
-`Boolean` - returns `true` if the value was stored, otherwise `false`.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"db_putHex","params":["testDB","myKey","0x68656c6c6f20776f726c64"],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc":"2.0",
- "result": true
-}
-```
-
-
-
-### db_getHex {#db_gethex}
-
-Returns binary data from the local database.
-
-**Note** this function is deprecated and will be removed in the future.
-
-**Parameters**
-
-1. `String` - Database name.
-2. `String` - Key name.
-
-```js
-params: ["testDB", "myKey"]
-```
-
-**Returns**
-
-`DATA` - The previously stored data.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"db_getHex","params":["testDB","myKey"],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc":"2.0",
- "result": "0x68656c6c6f20776f726c64"
-}
-```
-
-
-
-### shh_version {#shh_post}
-
-Returns the current whisper protocol version.
-
-**Parameters**
-
-None
-
-**Returns**
-
-`String` - The current whisper protocol version
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"shh_version","params":[],"id":67}'
-
-// Result
-{
- "id":67,
- "jsonrpc": "2.0",
- "result": "2"
-}
-```
-
-
-
-### shh_post {#shh_version}
-
-Sends a whisper message.
-
-**Parameters**
-
-1. `Object` - The whisper post object:
-
-- `from`: `DATA`, 60 Bytes - (optional) The identity of the sender.
-- `to`: `DATA`, 60 Bytes - (optional) The identity of the receiver. When present whisper will encrypt the message so that only the receiver can decrypt it.
-- `topics`: `Array of DATA` - Array of `DATA` topics, for the receiver to identify messages.
-- `payload`: `DATA` - The payload of the message.
-- `priority`: `QUANTITY` - The integer of the priority in a rang from ... (?).
-- `ttl`: `QUANTITY` - integer of the time to live in seconds.
-
-```js
-params: [
- {
- from:
- "0x04f96a5e25610293e42a73908e93ccc8c4d4dc0edcfa9fa872f50cb214e08ebf61a03e245533f97284d442460f2998cd41858798ddfd4d661997d3940272b717b1",
- to:
- "0x3e245533f97284d442460f2998cd41858798ddf04f96a5e25610293e42a73908e93ccc8c4d4dc0edcfa9fa872f50cb214e08ebf61a0d4d661997d3940272b717b1",
- topics: [
- "0x776869737065722d636861742d636c69656e74",
- "0x4d5a695276454c39425154466b61693532",
- ],
- payload: "0x7b2274797065223a226d6",
- priority: "0x64",
- ttl: "0x64",
- },
-]
-```
-
-**Returns**
-
-`Boolean` - returns `true` if the message was send, otherwise `false`.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"shh_post","params":[{"from":"0xc931d93e97ab07fe42d923478ba2465f2..","topics": ["0x68656c6c6f20776f726c64"],"payload":"0x68656c6c6f20776f726c64","ttl":0x64,"priority":0x64}],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc":"2.0",
- "result": true
-}
-```
-
-
-
-### shh_newIdentity {#shh_newidentity}
-
-Creates new whisper identity in the client.
-
-**Parameters**
-
-None
-
-**Returns**
-
-`DATA`, 60 Bytes - the address of the new identiy.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"shh_newIdentity","params":[],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0xc931d93e97ab07fe42d923478ba2465f283f440fd6cabea4dd7a2c807108f651b7135d1d6ca9007d5b68aa497e4619ac10aa3b27726e1863c1fd9b570d99bbaf"
-}
-```
-
-
-
-### shh_hasIdentity {#shh_hasidentity}
-
-Checks if the client hold the private keys for a given identity.
-
-**Parameters**
-
-1. `DATA`, 60 Bytes - The identity address to check.
-
-```js
-params: [
- "0x04f96a5e25610293e42a73908e93ccc8c4d4dc0edcfa9fa872f50cb214e08ebf61a03e245533f97284d442460f2998cd41858798ddfd4d661997d3940272b717b1",
-]
-```
-
-**Returns**
-
-`Boolean` - returns `true` if the client holds the privatekey for that identity, otherwise `false`.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"shh_hasIdentity","params":["0x04f96a5e25610293e42a73908e93ccc8c4d4dc0edcfa9fa872f50cb214e08ebf61a03e245533f97284d442460f2998cd41858798ddfd4d661997d3940272b717b1"],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": true
-}
-```
-
-
-
-### shh_newGroup {#shh_newgroup}
-
-(?)
-
-**Parameters**
-
-None
-
-**Returns**
-
-`DATA`, 60 Bytes - the address of the new group. (?)
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"shh_newGroup","params":[],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": "0xc65f283f440fd6cabea4dd7a2c807108f651b7135d1d6ca90931d93e97ab07fe42d923478ba2407d5b68aa497e4619ac10aa3b27726e1863c1fd9b570d99bbaf"
-}
-```
-
-
-
-### shh_addToGroup {#shh_addtogroup}
-
-(?)
-
-**Parameters**
-
-1. `DATA`, 60 Bytes - The identity address to add to a group (?).
-
-```js
-params: [
- "0x04f96a5e25610293e42a73908e93ccc8c4d4dc0edcfa9fa872f50cb214e08ebf61a03e245533f97284d442460f2998cd41858798ddfd4d661997d3940272b717b1",
-]
-```
-
-**Returns**
-
-`Boolean` - returns `true` if the identity was successfully added to the group, otherwise `false` (?).
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"shh_addToGroup","params":["0x04f96a5e25610293e42a73908e93ccc8c4d4dc0edcfa9fa872f50cb214e08ebf61a03e245533f97284d442460f2998cd41858798ddfd4d661997d3940272b717b1"],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc": "2.0",
- "result": true
-}
-```
-
-
-
-### shh_newFilter {#shh_newfilter}
-
-Creates filter to notify, when client receives whisper message matching the filter options.
-
-**Parameters**
-
-1. `Object` - The filter options:
-
-- `to`: `DATA`, 60 Bytes - (optional) Identity of the receiver. _When present it will try to decrypt any incoming message if the client holds the private key to this identity._
-- `topics`: `Array of DATA` - Array of `DATA` topics which the incoming message's topics should match. You can use the following combinations:
- - `[A, B] = A && B`
- - `[A, [B, C]] = A && (B || C)`
- - `[null, A, B] = ANYTHING && A && B` `null` works as a wildcard
-
-```js
-params: [
- {
- topics: ["0x12341234bf4b564f"],
- to:
- "0x04f96a5e25610293e42a73908e93ccc8c4d4dc0edcfa9fa872f50cb214e08ebf61a03e245533f97284d442460f2998cd41858798ddfd4d661997d3940272b717b1",
- },
-]
-```
-
-**Returns**
-
-`QUANTITY` - The newly created filter.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"shh_newFilter","params":[{"topics": ['0x12341234bf4b564f'],"to": "0x2341234bf4b2341234bf4b564f..."}],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc":"2.0",
- "result": "0x7" // 7
-}
-```
-
-
-
-### shh_uninstallFilter {#shh_uninstallfilter}
-
-Uninstalls a filter with given id. Should always be called when watch is no longer needed.
-Additonally Filters timeout when they aren't requested with [shh_getFilterChanges](#shh_getfilterchanges) for a period of time.
-
-**Parameters**
-
-1. `QUANTITY` - The filter id.
-
-```js
-params: [
- "0x7", // 7
-]
-```
-
-**Returns**
-
-`Boolean` - `true` if the filter was successfully uninstalled, otherwise `false`.
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"shh_uninstallFilter","params":["0x7"],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc":"2.0",
- "result": true
-}
-```
-
-
-
-### shh_getFilterChanges {#shh_getfilterchanges}
-
-Polling method for whisper filters. Returns new messages since the last call of this method.
-
-**Note** calling the [shh_getMessages](#shh_getmessages) method, will reset the buffer for this method, so that you won't receive duplicate messages.
-
-**Parameters**
-
-1. `QUANTITY` - The filter id.
-
-```js
-params: [
- "0x7", // 7
-]
-```
-
-**Returns**
-
-`Array` - Array of messages received since last poll:
-
-- `hash`: `DATA`, 32 Bytes (?) - The hash of the message.
-- `from`: `DATA`, 60 Bytes - The sender of the message, if a sender was specified.
-- `to`: `DATA`, 60 Bytes - The receiver of the message, if a receiver was specified.
-- `expiry`: `QUANTITY` - Integer of the time in seconds when this message should expire (?).
-- `ttl`: `QUANTITY` - Integer of the time the message should float in the system in seconds (?).
-- `sent`: `QUANTITY` - Integer of the unix timestamp when the message was sent.
-- `topics`: `Array of DATA` - Array of `DATA` topics the message contained.
-- `payload`: `DATA` - The payload of the message.
-- `workProved`: `QUANTITY` - Integer of the work this message required before it was send (?).
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"shh_getFilterChanges","params":["0x7"],"id":73}'
-
-// Result
-{
- "id":1,
- "jsonrpc":"2.0",
- "result": [{
- "hash": "0x33eb2da77bf3527e28f8bf493650b1879b08c4f2a362beae4ba2f71bafcd91f9",
- "from": "0x3ec052fc33..",
- "to": "0x87gdf76g8d7fgdfg...",
- "expiry": "0x54caa50a", // 1422566666
- "sent": "0x54ca9ea2", // 1422565026
- "ttl": "0x64", // 100
- "topics": ["0x6578616d"],
- "payload": "0x7b2274797065223a226d657373616765222c2263686...",
- "workProved": "0x0"
- }]
-}
-```
-
-
-
-### shh_getMessages {#shh_getmessages}
-
-Get all messages matching a filter. Unlike `shh_getFilterChanges` this returns all messages.
-
-**Parameters**
-
-1. `QUANTITY` - The filter id.
-
-```js
-params: [
- "0x7", // 7
-]
-```
-
-**Returns**
-
-See [shh_getFilterChanges](#shh_getfilterchanges)
-
-**Example**
-
-```js
-// Request
-curl -X POST --data '{"jsonrpc":"2.0","method":"shh_getMessages","params":["0x7"],"id":73}'
-```
-
-Result see [shh_getFilterChanges](#shh_getfilterchanges)
+- [JSON-RPC Spec](https://github.com/ethereum/eth1.0-apis)
+- [JSON-RPC Playground ](https://github.com/OpenZeppelin/openzeppelin-contracts)
diff --git a/src/content/developers/docs/blocks/index.md b/src/content/developers/docs/blocks/index.md
index 6e045c59ab3..dd2415ec041 100644
--- a/src/content/developers/docs/blocks/index.md
+++ b/src/content/developers/docs/blocks/index.md
@@ -44,18 +44,19 @@ Proof of work means the following:
## What's in a block? {#block-anatomy}
-- Timestamp – the time when the block was mined.
-- Block number – the length of the blockchain in blocks.
-- Difficulty – the effort required to mine the block.
-- mixHash – a unique identifier for that block.
-- A parent hash – the unique identifier for the block that came before (this is how blocks are linked in a chain).
-- Transactions list – the transactions included in the block.
-- State root – the entire state of the system: account balances, contract storage, contract code and account nonces are inside.
-- Nonce – a hash that, when combined with the mixHash, proves that the block has gone through [proof of work](/developers/docs/consensus-mechanisms/pow/).
+- `timestamp` – the time when the block was mined.
+- `blockNumber` – the length of the blockchain in blocks.
+- `baseFeePerGas` - the minimum fee per gas required for a transaction to be included in the block.
+- `difficulty` – the effort required to mine the block.
+- `mixHash` – a unique identifier for that block.
+- `parentHash` – the unique identifier for the block that came before (this is how blocks are linked in a chain).
+- `transactions` – the transactions included in the block.
+- `stateRoot` – the entire state of the system: account balances, contract storage, contract code and account nonces are inside.
+- `nonce` – a hash that, when combined with the mixHash, proves that the block has gone through [proof of work](/developers/docs/consensus-mechanisms/pow/).
## Block size {#block-size}
-A final important note is that blocks themselves are bounded in size. Each block has a block gas limit which is set by the network and the miners collectively: the total amount of gas expended by all transactions in the block must be less than the block gas limit. This is important because it ensures that blocks can’t be arbitrarily large. If blocks could be arbitrarily large, then less performant full nodes would gradually stop being able to keep up with the network due to space and speed requirements. The block gas limit at block 0 was initialized to 5,000; any miner who mines a new block can alter the gas limit by up to about 0.1% in either direction from the parent block gas limit. The gas limit as of April 2021 currently hovers around 15,000,000.
+A final important note is that blocks themselves are bounded in size. Each block has a target size of 15 million gas but the size of blocks will increase or decrease in accordance with network demands, up until the block limit of 30 milion gas (2x target block size). The total amount of gas expended by all transactions in the block must be less than the block gas limit. This is important because it ensures that blocks can’t be arbitrarily large. If blocks could be arbitrarily large, then less performant full nodes would gradually stop being able to keep up with the network due to space and speed requirements.
## Further reading {#further-reading}
diff --git a/src/content/developers/docs/gas/index.md b/src/content/developers/docs/gas/index.md
index a05eeddf58e..bc4067caa51 100644
--- a/src/content/developers/docs/gas/index.md
+++ b/src/content/developers/docs/gas/index.md
@@ -3,7 +3,6 @@ title: Gas and fees
description:
lang: en
sidebar: true
-incomplete: true
---
Gas is essential to the Ethereum network. It is the fuel that allows it to operate, in the same way that a car needs gasoline to run.
@@ -21,88 +20,123 @@ Since each Ethereum transaction requires computational resources to execute, eac
_Diagram adapted from [Ethereum EVM illustrated](https://takenobu-hs.github.io/downloads/ethereum_evm_illustrated.pdf)_
-In essence, gas fees are paid in Ethereum's native currency, ether (ETH). Gas prices are denoted in gwei, which itself is a denomination of ETH - each gwei is equal to 0.000000001 ETH (10-9 ETH). For example, instead of saying that your gas costs 0.000000001 ether, you can say your gas costs 1 gwei.
+Gas fees are paid in Ethereum's native currency, ether (ETH). Gas prices are denoted in gwei, which itself is a denomination of ETH - each gwei is equal to 0.000000001 ETH (10-9 ETH). For example, instead of saying that your gas costs 0.000000001 ether, you can say your gas costs 1 gwei.
-Let's say Alice has to pay Bob 1ETH.
+## Prior to the London upgrade {#pre-london}
+
+The way transaction fees on the Ethereum network are calculated changed during the London network upgrade. Here is a recap of how things used to work:
+
+Let's say Alice had to pay Bob 1 ETH.
In the transaction the gas limit is 21,000 units and the gas price is 200 gwei.
-Total fee will be: `Gas units (limit) * Gas price per unit`
+Total fee would have been: `Gas units (limit) * Gas price per unit`
i.e `21,000 * 200 = 4,200,000 gwei` or 0.0042 ETH
-Now, when Alice sends the money, 1.0042 ETH will be deducted from Alice's account.
-Bob will be credited 1.0000 ETH.
-Miner gets 0.0042 ETH.
+When Alice sent the money, 1.0042 ETH would be deducted from Alice's account.
+Bob would be credited 1.0000 ETH.
+Miner would receive 0.0042 ETH.
This video offers a concise overview of gas and why it exists:
-## Why do gas fees exist? {#why-do-gas-fees-exist}
+## After the London Upgrade {#post-london}
-In short, gas fees help keep the Ethereum network secure. By requiring a fee for every computation executed on the network, we prevent actors from spamming the network. In order to prevent accidental or hostile infinite loops or other computational wastage in code, each transaction is required to set a limit to how many computational steps of code execution it can use. The fundamental unit of computation is "gas".
+[The London Upgrade](/history/#london) aims to make transacting on Ethereum more predictable for users by overhauling Ethereum's transaction-fee-mechanism. The high-level benefits introduced by this change include better transaction fee estimation, generally quicker transaction inclusion, and offsetting the ETH issuance by burning a percentage of transaction fees.
-Although a transaction includes a limit, any gas not used in a transaction is returned to the user.
+Starting with the London network upgrade, every block has a base fee, the minimum price per unit of gas for inclusion in this block, calculated by the network based on demand for block space. As the base fee of the transaction fee is burnt, users are also expected to set a tip (priority fee) in their transactions. The tip compensates miners for executing and propagating user transactions in blocks and is expected to be set automatically by most wallets.
-
-_Diagram adapted from [Ethereum EVM illustrated](https://takenobu-hs.github.io/downloads/ethereum_evm_illustrated.pdf)_
+Calculating the total transaction fee works as follows: `Gas units (limit) * (Base fee + Tip)`
-## What is gas limit? {#what-is-gas-limit}
+Let’s say Jordan has to pay Taylor 1 ETH. In the transaction the gas limit is 21,000 units and the base fee is 100 gwei. Jordan includes a tip of 10 gwei.
-Gas limit refers to the maximum amount of gas you are willing to consume on a transaction. More complicated transactions, involving [smart contracts](/developers/docs/smart-contracts/), require more computational work so they require a higher gas limit than a simple payment. A standard ETH transfer requires a gas limit of 21,000 units of gas.
+Using the formula above we can calculate this as `21,000 * (100 + 10) = 2,310,000 gwei` or 0.0023 ETH.
-For example if you put a gas limit of 50,000 for a simple ETH transfer, the EVM would consume 21,000, and you would get back the remaining 29,000. However, if you specify too little gas say for example, a gas limit of 20,000 for a simple ETH transfer, the EVM will consume your 20,000 gas units attempting to fulfill the txn, but it will not complete. The EVM then reverts any changes, but since 20k gas units worth of work has already been done by the miner, that gas is consumed.
+When Jordan sends the money, 1.0023 ETH will be deducted from Jordan's account.
+Taylor will be credited 1.0000 ETH.
+Miner receives the tip of 0.000195 ETH.
+Base fee of 0.001953 ETH is burned.
+
+Additionally, Jordan can also set a max fee (`maxFeePerGas`) for the transaction. The difference between the max fee and the actual fee is refunded to Jordan, i.e. `refund = max fee - (base fee + priority fee)`. Jordan can set a maximum amount to pay for the transaction to execute and not worry about are overpaying "beyond" the base fee when the transaction is executed.
+
+### Block Size {#block-size}
+
+Before the London Upgrade, Ethereum had fixed-sized blocks. In times of high network demand, these blocks operated at total capacity. As a result, users often had to wait for high demand to reduce to get included in a block, which led to a poor user experience.
+
+The London Upgrade introduced variable-size blocks to Ethereum. Each block has a target size of 15 million gas but, the size of blocks will increase or decrease in accordance with network demand, up until the block limit of 30 million gas (2x the target block size). The protocol achieves an equilibrium block size of 15 million on average through the process of _tâtonnement_. This means if the block size is greater than the target block size, the protocol will increase the base fee for the following block. Similarly, the protocol will decrease the base fee if the block size is less than the target block size. The amount the base fee is adjusted by is proportional to how far from the current block size is from the target. [More on blocks](/developers/docs/blocks/).
+
+### Base Fee {#base-fee}
+
+Every block has a base fee which acts as a reserve price. To be eligible for inclusion in a block the offered price per gas must at least equal the base fee. The base fee is calculated independently of the current block and is instead determined by the blocks before it - making transaction fees more predictable for users. When the block is mined this base fee is "burned", removing it from circulation.
+
+The base fee is calculated by a formula that compares the size of the previous block (the amount of gas used for all the transactions) with the target size. The base fee will increase by a maximum of 12.5% per block if the target block size is exceeded. This exponential growth makes it economically non-viable for block size to remain high indefinitely.
+
+| Block Number | Included Gas | Fee Increase | Current Base Fee |
+| ------------ | -----------: | -----------: | ---------------: |
+| 1 | 15M | 0% | 100 gwei |
+| 2 | 30M | 0% | 100 gwei |
+| 3 | 30M | 12.5% | 112.5 gwei |
+| 4 | 30M | 12.5% | 126.5 gwei |
+| 5 | 30M | 12.5% | 142.4 gwei |
+| 6 | 30M | 12.5% | 160.2 gwei |
+| 7 | 30M | 12.5% | 180.2 gwei |
+| 8 | 30M | 12.5% | 202.8 gwei |
-## What is gas price? {#what-is-gas-price}
+Relative to the pre-London gas auction market, this transaction-fee-mechanism change causes fee prediction to be more reliable. Following the table above - to create a transaction on block number 9, a wallet will let the user know with certainty that the **maximum base fee** to be added to the next block is `current base fee * 112.5%` or `202.8 gwei * 112.5% = 256.8 gwei`.
-Gas price refers to the amount of Ether you are willing to pay for every unit of gas, and this is usually measured in 'gwei'. Prior to
-[the London update](/history/#london), you specify in the transaction how much you are willing to pay per gas, and you pay exactly that amount.
-Different transactions in the same block can have very different gas prices.
+It's also important to note it is unlikely we will see extended spikes of full blocks because of the speed at which the base fee increases proceeding a full block.
-### The London update {#gas-price-london-update}
+| Block Number | Included Gas | Fee Increase | Current Base Fee |
+| ------------ | -----------: | -----------: | ---------------: |
+| 30 | 30M | 12.5% | 2705.6 gwei |
+| ... | ... | 12.5% | ... |
+| 50 | 30M | 12.5% | 28531.3 gwei |
+| ... | ... | 12.5% | ... |
+| 100 | 30M | 12.5% | 10302608.57 gwei |
-Starting with the London update, every block has a base fee, the minimum per gas price for inclusion in this block. The base fee is calculated by a formula
-that compares the size of the previous block (the amount of gas used for all the transactions) with a target size. This upgrade will double the allowable block size, while targeting blocks to be 50% full. If the block size is higher than the target, there is more demand for inclusion in the blockchain than targeted supply, so the base fee in the subsequent block is increased. If the block size is lower than the target then there is less demand for block space than targeted supply, so the base fee is subsequently decreased. The amount the base fee is adjusted by is proportional to how far from the target the block size is. This base fee is "burned", removing it from circulation.
+### Priority Fee (Tips) {#priority-fee}
-Transactions can either specify a gas price using the old mechanism, or specify two other parameters:
+Before the London Upgrade, miners would receive the total gas fee from any transaction included in a block.
-- Maximum Fee per Gas: The maximum gas price the transaction can be charged.
-- Maximum Priority Fee per Gas (a.k.a. Tip): The maximum priority fee the transaction signer is willing to pay the miner per gas to be included.
- If the base fee plus this amount is less than the maximum fee per gas, this is the priority fee. Otherwise, the priority fee is the maximum
- fee minus the base fee.
+With the new base fee getting burned, the London Upgrade introduced a priority fee (tip) to incentivize miners to include a transaction in the block. Without tips, miners would find it economically viable to mine empty blocks, as they would receive the same block reward. Under normal conditions, a small tip provides miners a minimal incentive to include a transaction. For transactions that need to get preferentially executed ahead of other transactions in the same block, a higher tip will be necessary to attempt to outbid competing transactions.
-For example, imagine a block with a base fee of 100 gwei. The pool of available transactions contains the transactions
-in the table below. Transactions A-C are type 2, so they include both a maximum fee per gas and a maximum priority fee per gas.
-Transaction D is an older transaction type (either 0, without an access list, or 1, which does have an access list), so it only specifies
-a gas price. That gas price is used for both maximum fee per gas and maximum priority fee per gas.
+### Max Fee {#maxfee}
-| ID | Maximum Fee per Gas | Maximum Priority Fee per Gas | Actual Priority Fee | Actual Gas Price | Remarks |
-| --- | ------------------: | ---------------------------: | ------------------: | ---------------: | --------------------------------------------------------------- |
-| A | 90 gwei | 90 gwei | N/A | N/A | This transaction is not going in the block |
-| B | 200 gwei | 5 gwei | 5 gwei | 105 gwei | The priority fee is the maximum priority fee |
-| C | 120 gwei | 30 gwei | 20 gwei | 120 gwei | The priority fee is the maximum (total) fee minus the base fee |
-| D | 200 gwei | 200 gwei | 100 gwei | 200 gwei | Transactions that specify gas price are charged the full amount |
+To execute a transaction on the network users are able to specify a maximum limit they are willing to pay for their transaction to be executed. This optional parameter is known as the `maxFeePerGas`. In order for a transaction to be executed the max fee must exceed the sum of the base fee and the tip. The transaction sender is refunded the difference between the max fee and the sum of the base fee and tip.
-Miners and validators are expected to choose the transactions that will pay them the highest priority fees.
+## EIP-1559 {#eip-1559}
-This mechanism is more complicated than the simple gas price auction, but it has the advantage of making gas fees more predictable, as well as making ETH more
-valuable by removing some of it from circulation. The maximum fee per gas functions as a [second price auction](https://oko.uk/blog/first-price-vs-second-price-auctions),
-which is more efficient than the previous mechanism that is a first price auction. Users can submit transactions with a much higher maximum fee per gas, corresponding
-to how much they need the transaction to happen, without having to worry that they will be overcharged.
+The implementation of [EIP-1559](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1559.md) in the London Upgrade makes the transaction fee mechanism more complex than the current gas price auction, but it has the advantage of making gas fees more predictable, resulting in a more efficient transaction fee market. Users can submit transactions with a `maxFeePerGas` corresponding to how much they are willing to pay for the transaction to be executing, knowing that they will not pay more than the market price for gas (`baseFeePerGas`), and get any extra, minus their tip, refunded.
+
+This video explains EIP-1559 and the benefits it brings:
+
+
If you are interested you can read the exact
[EIP-1559 specifications](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1559.md).
Continue down the rabbit hole with these [EIP-1559 Resources](https://hackmd.io/@timbeiko/1559-resources).
-## Why can gas fees get so high? {#why-can-gas-fees-get-so-high}
+## Why do gas fees exist? {#why-do-gas-fees-exist}
-High gas fees are due to the popularity of Ethereum. Performing any operation on Ethereum requires consuming gas, and gas space is limited per block. This includes calculations, storing or manipulating data, or transferring tokens, each consuming different amounts of "gas" units. As dapp functionality grows more complex, the number of operations a smart contract performs grows too, meaning each transaction takes up more space of a limited size block. If there's too much demand, users must offer a higher gas price to try and out-bid other users' transactions. A higher price can make it more likely that your transaction will get into the next block.
+In short, gas fees help keep the Ethereum network secure. By requiring a fee for every computation executed on the network, we prevent bad actors from spamming the network. In order to prevent accidental or hostile infinite loops or other computational wastage in code, each transaction is required to set a limit to how many computational steps of code execution it can use. The fundamental unit of computation is "gas".
+
+Although a transaction includes a limit, any gas not used in a transaction is returned to the user (i.e `max fee - (base fee + tip)` is returned).
+
+
+_Diagram adapted from [Ethereum EVM illustrated](https://takenobu-hs.github.io/downloads/ethereum_evm_illustrated.pdf)_
-Gas price alone does not actually determine how much we have to pay for a particular transaction. To calculate the transaction fee we have to multiply the gas used by gas price, which is measured in gwei.
+## What is gas limit? {#what-is-gas-limit}
+
+Gas limit refers to the maximum amount of gas you are willing to consume on a transaction. More complicated transactions, involving [smart contracts](/developers/docs/smart-contracts/), require more computational work so they require a higher gas limit than a simple payment. A standard ETH transfer requires a gas limit of 21,000 units of gas.
+
+For example if you put a gas limit of 50,000 for a simple ETH transfer, the EVM would consume 21,000, and you would get back the remaining 29,000. However, if you specify too little gas say for example, a gas limit of 20,000 for a simple ETH transfer, the EVM will consume your 20,000 gas units attempting to fulfill the txn, but it will not complete. The EVM then reverts any changes, but since 20k gas units worth of work has already been done by the miner, that gas is consumed.
+
+## Why can gas fees get so high? {#why-can-gas-fees-get-so-high}
-This video about gas fees explains fully why fees can be so expensive:
+High gas fees are due to the popularity of Ethereum. Performing any operation on Ethereum requires consuming gas, and gas space is limited per block. This includes calculations, storing or manipulating data, or transferring tokens, each consuming different amounts of "gas" units. As dapp functionality grows more complex, the number of operations a smart contract performs grows too, meaning each transaction takes up more space of a limited size block. If there's too much demand, users must offer a higher tip amount to try and out-bid other users' transactions. A higher tip can make it more likely that your transaction will get into the next block.
-
+Gas price alone does not actually determine how much we have to pay for a particular transaction. To calculate the transaction fee we have to multiply the gas used by the transaction fee, which is measured in gwei.
## Initiatives to reduce gas costs {#initiatives-to-reduce-gas-costs}
@@ -116,7 +150,7 @@ Anyone with at least 32 ETH is able to stake them and become a validator respons
## Strategies for you to reduce gas costs {#strategies-for-you-to-reduce-gas-costs}
-If you are looking to reduce gas costs for your ETH you are able to set the price of your own gas fees and choose the priority level of your transaction. Miners will 'work on' and execute transactions that offer a higher gas price, as they get to keep the fees that you pay and will be less inclined to execute transactions with lower gas fees set. The gas price you set is how much you are willing to pay per unit of gas. However if you set the amount of gas too low you will not be able to send your ETH as you will run out of gas, you would then have to resubmit your transaction costing you more in gas fees. You can do this from some wallet providers when sending ETH.
+If you are looking to reduce gas costs for your ETH you are able to set a tip to indicate the priority level of your transaction. Miners will 'work on' and execute transactions that offer a higher tip per gas, as they get to keep the tips that you pay and will be less inclined to execute transactions with lower tips set.
If you want to monitor gas prices so you are able to send your ETH for less you can use many different tools such as:
@@ -125,7 +159,6 @@ If you want to monitor gas prices so you are able to send your ETH for less you
## Further Reading {#further-reading}
-- [Understanding Ethereum Gas, Blocks and the Fee Market](https://medium.com/@eric.conner/understanding-ethereum-gas-blocks-and-the-fee-market-d5e268bf0a0e)
- [Ethereum Gas Explained](https://defiprime.com/gas)
- [Is Ethereum more expensive to use as price rises?](https://docs.ethhub.io/questions-about-ethereum/is-ethereum-more-expensive-to-use-as-price-rises/)
- [Reducing the gas consumption of your Smart Contracts](https://medium.com/coinmonks/8-ways-of-reducing-the-gas-consumption-of-your-smart-contracts-9a506b339c0a)
diff --git a/src/content/developers/docs/transactions/index.md b/src/content/developers/docs/transactions/index.md
index e0a047e0db8..e634d166fa5 100644
--- a/src/content/developers/docs/transactions/index.md
+++ b/src/content/developers/docs/transactions/index.md
@@ -33,9 +33,10 @@ A submitted transaction includes the following information:
- `value` – amount of ETH to transfer from sender to recipient (in WEI, a denomination of ETH)
- `data` – optional field to include arbitrary data
- `gasLimit` – the maximum amount of gas units that can be consumed by the transaction. Units of gas represent computational steps
-- `gasPrice` – the fee the sender pays per unit of gas
+- `maxPriorityFeePerGas` - the maximum amount of gas to be included as a tip to the miner
+- `maxFeePerGas` - the maximum amount of gas willing to be paid for the transaction (inclusive of `baseFeePerGas` and `maxPriorityFeePerGas`)
-Gas is a reference to the computation required to process the transaction by a miner. Users have to pay a fee for this computation. The `gasLimit` and `gasPrice` determine the maximum transaction fee paid to the miner. [More on Gas](/developers/docs/gas/).
+Gas is a reference to the computation required to process the transaction by a miner. Users have to pay a fee for this computation. The `gasLimit`, and `maxPriorityFeePerGas` determine the maximum transaction fee paid to the miner. [More on Gas](/developers/docs/gas/).
The transaction object will look a little like this:
@@ -44,7 +45,8 @@ The transaction object will look a little like this:
from: "0xEA674fdDe714fd979de3EdF0F56AA9716B898ec8",
to: "0xac03bb73b6a9e108530aff4df5077c2b3d481e5a",
gasLimit: "21000",
- gasPrice: "200",
+ maxFeePerGas: "300"
+ maxPriorityFeePerGas: "10"
nonce: "0",
value: "10000000000",
}
@@ -65,7 +67,8 @@ Example [JSON-RPC](https://eth.wiki/json-rpc/API) call:
{
"from": "0x1923f626bb8dc025849e00f99c25fe2b2f7fb0db",
"gas": "0x55555",
- "gasPrice": "0x1234",
+ "maxFeePerGas": "0x1234",
+ "maxPriorityFeePerGas": "0x1234",
"input": "0xabcd",
"nonce": "0x0",
"to": "0x07a565b7ed7d7a678680a4c162885bedbb695fe0",
@@ -85,7 +88,8 @@ Example response:
"raw": "0xf88380018203339407a565b7ed7d7a678680a4c162885bedbb695fe080a44401a6e4000000000000000000000000000000000000000000000000000000000000001226a0223a7c9bcf5531c99be5ea7082183816eb20cfe0bbc322e97cc5c7f71ab8b20ea02aadee6b34b45bb15bc42d9c09de4a6754e7000908da72d48cc7704971491663",
"tx": {
"nonce": "0x0",
- "gasPrice": "0x1234",
+ "maxFeePerGas": "0x1234",
+ "maxPriorityFeePerGas": "0x1234",
"gas": "0x55555",
"to": "0x07a565b7ed7d7a678680a4c162885bedbb695fe0",
"value": "0x1234",
@@ -108,10 +112,10 @@ With the signature hash, the transaction can be cryptographically proven that it
As mentioned, transactions cost [gas](/developers/docs/gas/) to execute. Simple transfer transactions require 21000 units of Gas.
-So for Bob to send Alice 1 ETH at a `gasPrice` of 200 gwei, Bob will need to pay the following fee:
+So for Bob to send Alice 1 ETH at a `baseFeePerGas` of 190 gwei and `maxPriorityFeePerGas` of 10 gwei, Bob will need to pay the following fee:
```
-200 * 21000 = 4,200,000 gwei
+(190 + 10) * 21000 = 4,200,000 gwei
--or--
0.0042 ETH
```
@@ -120,7 +124,9 @@ Bob's account will be debited **-1.0042 ETH**
Alice's account will be credited **+1.0 ETH**
-The miner processing the transaction will get **+0.0042 ETH**
+The base fee will be burned **-0.003735 ETH**
+
+Miner keeps the tip **+0.000197 ETH**
Gas is required for any smart contract interaction too.
@@ -137,7 +143,7 @@ Once the transaction has been submitted the following happens:
`0x97d99bc7729211111a21b12c933c949d4f31684f1d6954ff477d0477538ff017`
2. The transaction is then broadcast to the network and included in a pool with lots of other transactions.
3. A miner must pick your transaction and include it in a block in order to verify the transaction and consider it "successful".
- - You may end up waiting at this stage if the network is busy and miners aren't able to keep up. Miners will always prioritise transactions with higher `GASPRICE` because they get to keep the fees.
+ - You may end up waiting at this stage if the network is busy and miners aren't able to keep up.
4. Your transaction will also get a block confirmation number. This is the number of blocks created since the block that your transaction was included in. The higher the number, the greater the certainty that the transaction was processed and recognised by the network. This is because sometimes the block your transaction was included in may not have made it into the chain.
- The larger the block confirmation number the more immutable the transaction is. So for higher value transactions, more block confirmations may be desired.
diff --git a/src/content/eips/index.md b/src/content/eips/index.md
index 20ec0b9367b..70e8993ada7 100644
--- a/src/content/eips/index.md
+++ b/src/content/eips/index.md
@@ -25,7 +25,7 @@ Along with providing a technical specification for changes, EIPs are the unit ar
The [Ethereum Improvement Proposals (EIPs) Github repository](https://github.com/ethereum/EIPs) was created in October 2015. The EIP process is based on the [Bitcoin Improvement Proposals (BIPs)](https://github.com/bitcoin/bips) process, which itself is based on the [Python Enhancement Proposals (PEPs)](https://www.python.org/dev/peps/) process.
-EIP editors are tasked with reviewing EIPs for technical soundness, correct spelling/grammar, and code style. Martin Becze, Vitalik Buterin, Gavin Wood, and a few others were the original EIP editors from 2015 to late 2016. The current EIP editors are:
+EIP editors are tasked with process of reviewing EIPs for technical soundness, correct spelling/grammar, and code style. Martin Becze, Vitalik Buterin, Gavin Wood, and a few others were the original EIP editors from 2015 to late 2016. The current EIP editors are:
- Alex Beregszaszi (EWASM/Ethereum Foundation)
- Greg Colvin (Community)
@@ -36,6 +36,11 @@ EIP editors are tasked with reviewing EIPs for technical soundness, correct spel
- Nick Savers (Community)
- Micah Zoltu (Community)
+EIP editors alongside with community members of [Ethereum Cat Herders](https://ethereumcatherders.com/) and [Ethererum Magicians](https://ethereum-magicians.org/) are deciding which EIP gets implemented, are responsible for facilitation of EIPs as well as moving the EIPs to "Final" or "Withdrawn" stage.
+
+Full standardization process alongside with chart is described in [EIP-1](https://eips.ethereum.org/EIPS/eip-1)
+
+
## Learn more {#learn-more}
If you’re interested to read more about EIPs, check out the [EIPs website](https://eips.ethereum.org/) where you can find additional information, including:
@@ -45,8 +50,9 @@ If you’re interested to read more about EIPs, check out the [EIPs website](htt
- [EIP statuses and what they mean](https://eips.ethereum.org/)
## Participate {#participate}
+Anyone can create EIP or ERC although you should read [EIP-1](https://eips.ethereum.org/EIPS/eip-1) which outlines the EIP process, what is EIP, types of EIPs, what EIP document should contain, EIP format and template, list of EIP Editors and all you need to know about EIPs before creating one. Your new EIP should define new feature that is not really complex yet not super niche and can be used in by projects in the Ethereum ecosystem. The hardest part is facilitation, you as the author need to facilitate people around your EIP, collect feedback, write articles describing problems that your EIP solves and collaborate with projects to implement your EIP.
-If you’re interested to follow along or share your input about EIPs, check out the [Ethereum Magicians forum](https://ethereum-magicians.org/), where EIPs are discussed with the community.
+If you’re interested to follow along the discussion process or share your input about EIPs, check out the [Ethereum Magicians forum](https://ethereum-magicians.org/), where EIPs are discussed with the community.
Also see:
diff --git a/src/content/history/index.md b/src/content/history/index.md
index 81029db4147..56792052db2 100644
--- a/src/content/history/index.md
+++ b/src/content/history/index.md
@@ -24,33 +24,41 @@ These rule changes may create a temporary split in the network. New blocks could
## 2021 {#2021}
-### (_In Progress_) London {#london}
+### (_In Progress_) Altair {#altair}
+
+The Altair upgrade is the first scheduled upgrade for the [Beacon Chain](/eth2/beacon-chain). It is expected to go live in 2021. It will add support for "sync committees", which can enable light clients, and will bring inactivity and slashing penalties up to their full values.
+
+- [Read the Altair upgrade specification](https://github.com/ethereum/eth2.0-specs/tree/dev/specs/altair)
+
+---
+
+### London {#london}
+
+Aug-05-2021 12:11:34 PM +UTC
+ Block number: 12,965,000
+ ETH price: $2710 USD
+ethereum.org on waybackmachine
-The London upgrade is scheduled to go live on Ethereum in August 2021, on block [12,965,000](https://etherscan.io/block/countdown/12965000). It will introduce [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559), which reforms the transaction fee market, along with changes to how gas refunds are handled and the [Ice Age](https://ethereum.org/en/glossary/#ice-age) schedule.
+#### Summary {#london-summary}
-- [Read the London upgrade specification](https://github.com/ethereum/eth1.0-specs/blob/master/network-upgrades/mainnet-upgrades/london.md)
-- [Read the London Mainnet announcement](https://blog.ethereum.org/2021/07/15/london-mainnet-announcement/)
+The London upgrade introduced [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559), which reformed the transaction fee market, along with changes to how gas refunds are handled and the [Ice Age](https://ethereum.org/en/glossary/#ice-age) schedule.
-
+- [Are you a dApp developer? Be sure to upgrade your libraries and tooling.](https://github.com/ethereum/eth1.0-specs/blob/master/network-upgrades/ecosystem-readiness.md)
+- [Read the Ethereum Foundation announcement](https://blog.ethereum.org/2021/07/15/london-mainnet-announcement/)
+- [Read the Ethereum Cat Herder's explainer](https://medium.com/ethereum-cat-herders/london-upgrade-overview-8eccb0041b41)
+
+
- [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559) – _improves the transaction fee market_
- [EIP-3198](https://eips.ethereum.org/EIPS/eip-3198) – _returns the `BASEFEE` from a block_
- [EIP-3529](https://eips.ethereum.org/EIPS/eip-3529) - _reduces gas refunds for EVM operations_
- [EIP-3541](https://eips.ethereum.org/EIPS/eip-3541) - _prevents deploying contracts starting with `0xEF`_
-- [EIP-3554](https://eips.ethereum.org/EIPS/eip-3554) – _delays the Ice Age_
+- [EIP-3554](https://eips.ethereum.org/EIPS/eip-3554) – _delays the Ice Age until December 2021_
---
-### (_In Progress_) Altair {#altair}
-
-The Altair upgrade is the first scheduled upgrade for the [Beacon Chain](/eth2/beacon-chain). It is expected to go live in 2021. It will add support for "sync committees", which can enable light clients, and will bring inactivity and slashing penalties up to their full values.
-
-- [Read the Altair upgrade specification](https://github.com/ethereum/eth2.0-specs/tree/dev/specs/altair)
-
----
-
### Berlin {#berlin}
Apr-15-2021 10:07:03 AM +UTC
diff --git a/src/content/learn/index.md b/src/content/learn/index.md
index 72d57cadc9b..15dd92d01bd 100644
--- a/src/content/learn/index.md
+++ b/src/content/learn/index.md
@@ -119,3 +119,24 @@ Critical views of Ethereum and Cryptocurrencies.
- [The Challenges of Building Ethereum Infrastructure](https://medium.com/@lopp/the-challenges-of-building-ethereum-infrastructure-87e443e47a4b) _Jan 8, 2018 - Jameson Lopp_
- [Parsimonious Answers to Difficult Questions](https://www.youtube.com/watch?v=GOkSg0BuSdw&feature=youtu.be) _(Video) March 10, 2019 - Rick Dudley_
- [There’s no good reason to trust blockchain technology](https://www.wired.com/story/theres-no-good-reason-to-trust-blockchain-technology/) _Feb 6, 2019 - Bruce Schneier_
+
+## Books and podcasts {#books-and-podcasts}
+
+Books on Ethereum and Cryptocurrencies:
+
+- [Out of the Ether: The Amazing Story of Ethereum and the $55 Million Heist that Almost Destroyed It All](https://www.goodreads.com/book/show/55360267-out-of-the-ether) _September 29, 2020 - Matthew Leising_
+- [The Infinite Machine: How an Army of Crypto-hackers Is Building the Next Internet with Ethereum](https://www.goodreads.com/en/book/show/50175330-the-infinite-machine) _July 14, 2020 - Camila Russo_
+- [The Age of Cryptocurrency: How Bitcoin and the Blockchain Are Challenging the Global Economic Order](https://www.goodreads.com/en/book/show/22174460-the-age-of-cryptocurrency) _January 12, 2016 - Paul Vigna, Michael J. Casey_
+- [The Truth Machine: The Blockchain and the Future of Everything](https://www.goodreads.com/en/book/show/34964890-the-truth-machine) _February 27, 2018 - Paul Vigna, Michael J. Casey_
+- [Digital Gold: Bitcoin and the Inside Story of the Misfits and Millionaires Trying to Reinvent Money](https://www.goodreads.com/book/show/23546676-digital-gold) _May 24, 2021 - Nathaniel Popper_
+- [Kings of Crypto: One Startup's Quest to Take Cryptocurrency Out of Silicon Valley and Onto Wall Street](https://www.goodreads.com/en/book/show/56274031-kings-of-crypto) _December 15, 2020 - Jeff John Roberts_
+- [Mastering Ethereum](https://github.com/ethereumbook/ethereumbook) _December 23, 2018 – Andreas M. Antonopoulos, Gavin Wood Ph.D. _
+
+Podcasts addressing Ethereum and Cryptocurrencies:
+
+- [Into the Ether](https://podcast.ethhub.io/) _A podcast focusing on all things Ethereum and DeFi_
+- [Bankless](http://podcast.banklesshq.com/) _A guide to Crypto finance_
+- [Uncommon Core](https://uncommoncore.co/podcast/) _Explores the transformative nature of trust-minimized currency and financial services_
+- [Zero Knowledge](https://www.zeroknowledge.fm/) _Goes deep into the tech that will power the emerging decentralised web and the community building this_
+- [Epicenter](https://epicenter.tv/) _Explores the technical, economic, and social implications of the Crypto industry_
+- [Unchained](https://unchainedpodcast.com/) _dives deep into the people building the decentralized internet, the details of this technology that could underpin our future, and some of the thorniest topics in crypto, such as regulation, security and privacy_
diff --git a/src/data/eth2-bounty-hunters.csv b/src/data/eth2-bounty-hunters.csv
index 728f542acc2..f650c0f329a 100644
--- a/src/data/eth2-bounty-hunters.csv
+++ b/src/data/eth2-bounty-hunters.csv
@@ -1,5 +1,5 @@
username, name, score
-cryptosubtlety, "Quan Thoi Minh Nguyen", 17500
+cryptosubtlety, "Quan Thoi Minh Nguyen", 19650
jrhea, "Jonny Rhea", 15500
AlexSSD7, "Alexander Sadovskyi", 2500
tintinweb, "tintin", 2500
