terianil ( Kamil Maciejczek )

Without this change Geth gives the error Fatal: Failed to write genesis block: unsupported fork ordering: petersburgBlock not enabled, but istanbulBlock enabled at 0

+1 -0

1 commit in ryanschneider/eth1.0-specs/tree/patch-1 ethereum/eth1.0-specs/tree/master

0 comment

1 changed file

pr created time in 2 months

PR merged ethereum/eth1.0-specs

Change genesis file to work with Besu and Geth

+1 -1

1 commit in ethereum/eth1.0-specs/tree/timbeiko-patch-1 ethereum/eth1.0-specs/tree/master

0 comment

1 changed file

timbeiko

pr closed time in 2 months

push eventethereum/eth1.0-specs

Tim Beiko

commit sha ce42880fb2722840ea3fa9cb0241f32f07f63264

Change genesis file to work with Besu and Geth

view details

Tim Beiko

commit sha add6c32d166f819c41accb166eb23c605ed35318

Merge pull request #29 from ethereum/timbeiko-patch-1 Change genesis file to work with Besu and Geth

view details

push time in 2 months

PR opened ethereum/eth1.0-specs

Change genesis file to work with Besu and Geth

+1 -1

1 commit in ethereum/eth1.0-specs/tree/timbeiko-patch-1 ethereum/eth1.0-specs/tree/master

0 comment

1 changed file

pr created time in 2 months

create barnchethereum/eth1.0-specs

branch : timbeiko-patch-1

created branch time in 2 months

pull request commentethereum/eth1.0-specs

eth_blockNumber

Thank you @MicahZoltu!

alita-moore

comment created time in 2 months

push eventethereum/eth1.0-specs

Tim Beiko

commit sha ba429763250ab9f55800bc7efc9f5957377216fe

Update aleut.md

view details

push time in 2 months

Pull request review commentethereum/eth1.0-specs

eth_blockNumber

+---+title: JSPON RPC Quantity Type Spec+author: Alita Moore (@alita-moore)+discussions-to: https://github.com/ethereum-oasis/eth1.x-JSON-RPC-API-standard+created: 2021-04-13+---++# `Quantity`++##### Description

Recommend against skipping heading levels, it can break some markdown tools like table of contents generators.

alita-moore

comment created time in 2 months

Pull request review commentethereum/eth1.0-specs

eth_blockNumber

+---+title: JSPON RPC Quantity Type Spec+author: Alita Moore (@alita-moore)+discussions-to: https://github.com/ethereum-oasis/eth1.x-JSON-RPC-API-standard+created: 2021-04-13+---++# `Quantity`++##### Description++`Quantity` represents the

Did this sentence get truncated somehow?

alita-moore

comment created time in 2 months

Pull request review commentethereum/eth1.0-specs

eth_blockNumber

+---+title: JSPON RPC Quantity Type Spec+author: Alita Moore (@alita-moore)+discussions-to: https://github.com/ethereum-oasis/eth1.x-JSON-RPC-API-standard+created: 2021-04-13+---++# `Quantity`++##### Description++`Quantity` represents the ++##### Requirements++| Req. | Description  |+| ----------- | ------------ |+|    **Γ1**   | A `Quantity` value **MUST** be hex-encoded |+|    **Γ2**   | A `Quantity` value **MUST** be "0x"-prefixed |+|    **Γ3**   | A `Quantity` value **MUST** be expressed using the fewest possible hex digits per byte |+|    **Γ4**   | A `Quantity` value **MUST** express zero as "0x0" |

May want to mention that leading 0s should be stripped.

alita-moore

comment created time in 2 months

Pull request review commentethereum/eth1.0-specs

eth_blockNumber

+---+title: JSPON RPC Quantity Type Spec+author: Alita Moore (@alita-moore)+discussions-to: https://github.com/ethereum-oasis/eth1.x-JSON-RPC-API-standard+created: 2021-04-13+---++# `Quantity`++##### Description++`Quantity` represents the ++##### Requirements++| Req. | Description  |+| ----------- | ------------ |+|    **Γ1**   | A `Quantity` value **MUST** be hex-encoded |+|    **Γ2**   | A `Quantity` value **MUST** be "0x"-prefixed |+|    **Γ3**   | A `Quantity` value **MUST** be expressed using the fewest possible hex digits per byte |+|    **Γ4**   | A `Quantity` value **MUST** express zero as "0x0" |

May want to add a note/line indicating that quantities must be unsigned integers (negative values not supported).

alita-moore

comment created time in 2 months

Pull request review commentethereum/eth1.0-specs

eth_blockNumber

+---+title: JSPON RPC Quantity Type Spec+author: Alita Moore (@alita-moore)+discussions-to: https://github.com/ethereum-oasis/eth1.x-JSON-RPC-API-standard+created: 2021-04-13+---++# `Quantity`++##### Description++`Quantity` represents the ++##### Requirements++| Req. | Description  |+| ----------- | ------------ |+|    **Γ1**   | A `Quantity` value **MUST** be hex-encoded |+|    **Γ2**   | A `Quantity` value **MUST** be "0x"-prefixed |+|    **Γ3**   | A `Quantity` value **MUST** be expressed using the fewest possible hex digits per byte |+|    **Γ4**   | A `Quantity` value **MUST** express zero as "0x0" |

I think I would just prefer a bulleted list here rather than a table.

* A `Quantity` value **MUST** be hex-encoded
* A `Quantity` value **MUST** be "0x"-prefixed
* A `Quantity` value **MUST** be expressed using the fewest possible hex digits per byte
* A `Quantity` value **MUST** express zero as "0x0"

alita-moore

comment created time in 2 months

Pull request review commentethereum/eth1.0-specs

eth_blockNumber

+---+title: JSPON RPC Quantity Type Spec+author: Alita Moore (@alita-moore)+discussions-to: https://github.com/ethereum-oasis/eth1.x-JSON-RPC-API-standard+created: 2021-04-13+---

I don't think metadata is required. We can get most of it from other places like GitHub history, file name, etc. and I think the plan is to have discussion just take place on the PR directly.

alita-moore

comment created time in 2 months

pull request commentethereum/eth1.0-specs

eth_blockNumber

Inviting @tkstanczak, @MicahZoltu for review.

alita-moore

comment created time in 2 months

issue openedethereum/eth1.0-specs

eth_blockNumber

see the drafted spec here

The following specs are expected to strictly define the behavior of eth_blockNumber

Spec	Description
δ1	Returns the number of the block that is the current chain head (the latest best processed and verified block on the chain)
δ2	The number of the chain head is returned if the node has ability of serving the header, body, and the full state starting from the state root of the block having the number in a finite time
δ3	The node may know a higher block number but still return a lower one if the lower number block has higher total difficulty or if the higher number block has not been fully processed yet
δ4	Provides no promise on for how long the node will keep the block details so if you request the block data for the given block number any time after receiving the block number itself, you may get a null response
δ5	Returns an error if the node has not yet processed or failed to process the genesis block. Some nodes MAY decide not to enable JSON RPC if the genesis block calculation has not been done yet

The purpose of this issue is to collect consensus for the specifications as described; please respond with a comment or ✅; I will collect your responses and keep track of consensus between clients. For example:

δ1) ✅ δ2) ✅ δ3) ✅ δ4) ✅ δ5) ✅

created time in 2 months

PR opened ethereum/eth1.0-specs

Get block number

+75 -0

2 commit in alita-moore/eth1.0-specs/tree/getBlockNumber ethereum/eth1.0-specs/tree/master

0 comment

1 changed file

pr created time in 2 months

push eventethereum/eth1.0-specs

lightclient

commit sha 7bbc49f28defd4f879e3afc146f8e8e493151dba