edit
This commit is contained in:
parent
bb9559898d
commit
29784c6f75
|
@ -1,9 +1,9 @@
|
|||
---
|
||||
id: eth1
|
||||
title: Execution layer client (eth1)
|
||||
title: Execution layer (eth1)
|
||||
---
|
||||
|
||||
While our core focus so far has been Ethereum 2, we are now devoting significant resources to our Ethereum 1 client.
|
||||
While our core focus so far has been Ethereum 2 (consensus layer), we are now devoting significant resources to our Ethereum 1 client (execution layer).
|
||||
|
||||
## Quickstart
|
||||
|
||||
|
@ -24,6 +24,6 @@ make nimbus
|
|||
./build/nimbus
|
||||
```
|
||||
|
||||
Nimbus will now run and attempt to synchronize with the Ethereum 1 blockchain.
|
||||
Nimbus will now run and attempt to synchronize with the Ethereum blockchain.
|
||||
|
||||
For a more complete overview see the [repository README](https://github.com/status-im/nimbus-eth1).
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
id: eth2
|
||||
title: Consensus layer client (eth2)
|
||||
title: Consensus layer (eth2)
|
||||
---
|
||||
|
||||
Depending on your objective, there are various ways to run Nimbus in [Ethereum 2 mode](https://github.com/status-im/nimbus-eth2).
|
||||
|
|
|
@ -7,15 +7,12 @@ Nimbus has joined the Ethereum Foundation’s Portal Network team as one of the
|
|||
|
||||
In a sentence, [the Portal Network](https://github.com/ethereum/stateless-ethereum-specs/blob/master/portal-network.md#network-functionality) is an in-progress cross-team effort to re-imagine the ethereum light client, and develop a practical and functional light client experience.
|
||||
|
||||
Nimbus has joined the Ethereum Foundation’s Portal Network team as one of the launch clients for the Portal Network.
|
||||
|
||||
In a sentence, [the Portal Network](https://github.com/ethereum/stateless-ethereum-specs/blob/master/portal-network.md#network-functionality) is an in-progress cross-team effort to re-imagine the Ethereum light client, and develop a practical and functional light client experience.
|
||||
|
||||
In particular, our aim is to work together with the EF to develop a new set of Ethereum protocols alongside the existing Eth protocol that will specifically serve this new way of accessing Ethereum data.
|
||||
|
||||
The overarching goal is to provide a mode of operation for Ethereum that serves common usage patterns, as opposed to keeping track of the full state at all times, as current clients do.
|
||||
|
||||
What we are talking about building here is the perfect client for a wallet. An ultra-light client that contributes to the network and does not require syncing (i.e. is immediately usable from a fresh install or after being offline).
|
||||
What we are talking about building here is **the perfect client for a wallet. An ultra-light client that contributes to the network and does not require syncing** (i.e. is immediately usable from a fresh install or after being offline).
|
||||
|
||||
As such, one of the end goals for us is to embed this sort of client directly inside the Status app.
|
||||
|
||||
|
|
|
@ -3,7 +3,7 @@ id: libraries
|
|||
title: Explore our libraries
|
||||
---
|
||||
|
||||
In addition to our [eth1](https://github.com/status-im/nimbus-eth1) and [eth2](https://github.com/status-im/nimbus-eth2) clients we have developed several high-quality libraries (the product of our ethereum work in Nim) These include:
|
||||
In addition to our [eth1](https://github.com/status-im/nimbus-eth1) (execution layer) and [eth2](https://github.com/status-im/nimbus-eth2) (consensus layer) clients we have developed several high-quality libraries (the product of our ethereum work in Nim) These include:
|
||||
|
||||
|
||||
- Nim libp2p: https://github.com/status-im/nim-libp2p
|
||||
|
|
Loading…
Reference in New Issue