feat: update subpages copy
This commit is contained in:
jinho jang
Jinho Jang
parent
21be02d5ae
commit
ddd121d3a1
|
|
@ -3,20 +3,19 @@ title: Description and architecture
|
|||
sidebar_position: 2
|
||||
---
|
||||
|
||||
Nimbus is a suite of Ethereum client implementations designed to be as lightweight, easy to use and as adaptive as possible. The consensus client is the first of three Nimbus implementations to reach production. Meanwhile, an execution client and a true Ethereum light client are still in development.
|
||||
Nimbus is a suite of Ethereum client implementations designed to be as lightweight, easy to use, and adaptive as possible. The consensus client is the first of three Nimbus implementations to reach production. Meanwhile, an execution client and a true Ethereum light client are still in development.
|
||||
|
||||
From their programming language upward, Nimbus clients are optimized to conserve system resources, making them suitable to run on embedded systems and lower-specification devices. Nim, the language in which Nimbus clients are written, was chosen for the following reasons:
|
||||
From their programming language upwards, Nimbus clients are optimized to conserve system resources, making them suitable to run on embedded systems and lower-specification devices. Nim, the language in which Nimbus clients are written, was chosen for the following reasons:
|
||||
|
||||
- It is an efficient, general-purpose systems programming language.
|
||||
|
||||
- It features Python-like syntax that compiles to C, enabling us to take advantage of the C language's mature tooling for code compilation and static code analysis.
|
||||
|
||||
- It has a high degree of reasonability for researchers.
|
||||
- It has a high degree of reasonability for researchers.
|
||||
|
||||
- It is performant in production.
|
||||
|
||||
- The above qualities make it easy for us to bring research into production, resulting in more adaptive, dynamic clients.
|
||||
|
||||
- The above qualities make it easy for us to bring research into production, resulting in more adaptive, dynamic clients.
|
||||
|
||||
Nimbus is fortunate to have multiple Nim contributors working on its client implementations as core team members. Additionally, the wider Nim community has expressed support for the Nimbus project.
|
||||
|
||||
|
|
@ -24,15 +23,9 @@ Nimbus is fortunate to have multiple Nim contributors working on its client impl
|
|||
|
||||
### Nimbus consensus client
|
||||
|
||||
Since the Nimbus consensus client's initial release in 2020, its representation in the Ethereum network has swung between 3% and 15%. We attribute this variance primarily to Nimbus' relative adoption among solo stakers and those providing services to the Rocket Pool network.
|
||||
The Nimbus consensus client offers significant advantages for all levels of users from hobbyists to institutional operators. The advantages include:
|
||||
|
||||
Larger node operators within the Lido network and those affiliated with centralized exchanges or other staking service providers—for which node count rises and falls with retail user interest—tend to favor alternate clients and need a strong reason to switch clients in the absence of risk.
|
||||
|
||||
The variation in Nimbus' representation arises from the flows of capital staked via different services. As more funds flow into centralized offerings using non-Nimbus clients, Nimbus' representation decreases. Conversely, the number of blocks produced by Nimbus clients increases when more ETH is staked via Rocketpool or by solo stakers.
|
||||
|
||||
The Nimbus consensus client offers significant advantages for all levels of user—from hobbyists to institutional operators—including:
|
||||
|
||||
- **Lightweight:** Nimbus consensus client strives to be as lightweight as possible in terms of resource overheads, leaving more headroom during times of heightened network usage. Operators can also run Nimbus together with other workloads on their servers to reduce overall costs.
|
||||
- **Lightweight:** Nimbus consensus client strives to be as lightweight as possible in terms of resource overhead, leaving more headroom during times of heightened network usage. Operators can also run Nimbus together with other workloads on their servers to reduce overall costs.
|
||||
|
||||
- **Flexible:** Nimbus consensus client is the only Ethereum client that offers the flexibility of running beacon node and validator clients independently, as operators often require. Additionally, it offers a simpler beacon node mode in which the beacon node assumes validator responsibilities, mitigating the need for operators to manage the two separately.
|
||||
|
||||
|
|
@ -46,24 +39,24 @@ The Nimbus consensus client offers significant advantages for all levels of user
|
|||
|
||||
### Nimbus execution client
|
||||
|
||||
Following Ethereum's switch to proof-of-stake in 2022—aka, "The Merge"—Ethereum validators must operate clients on both the consensus and execution layers. Yet, today, no client team offers both an execution and consensus layer client.
|
||||
Following Ethereum's switch to proof-of-stake in 2022, Ethereum validators must operate clients on both the consensus and execution layers. Yet as of today, no client team offers both an execution and consensus layer client.
|
||||
|
||||
Although the Nimbus execution client is still in development, when in production, pairing the Eth1 and Eth2 Nimbus clients will make for a user-friendly and convenient option for all levels of Ethereum node operator in terms of both installation and subsequent support.
|
||||
Although the Nimbus execution client is still in development, when in production, pairing the Eth1 and Eth2 Nimbus clients will make for a user-friendly and convenient option for all levels of Ethereum node operator, in terms of both installation and subsequent support.
|
||||
|
||||
Like the Nimbus consensus client, the execution client is written in Nim and designed to be as lightweight as possible, preserving valuable system resources and running in environments other clients cannot.
|
||||
Like the Nimbus consensus client, the execution client is written in Nim and designed to be as lightweight as possible, preserving valuable system resources and running in environments other clients cannot.
|
||||
|
||||
<br/>
|
||||
|
||||
### Nimbus Portal
|
||||
### Nimbus Portal Client
|
||||
|
||||
An absence of true light clients presents a major issue in today's web3 sector and contributes toward various centralizing tendencies on Ethereum. When users cannot validate on-chain data themselves—due to the technical or resource overheads of running their own validating node—they fall back on RPC nodes operated by centralized entities.
|
||||
An absence of true light clients presents a major issue in web3 because it contributes toward various centralizing tendencies on Ethereum. When users cannot validate on-chain data themselves (due to the technical or resource overheads of running their own validating node) they fall back on RPC nodes operated by centralized entities.
|
||||
|
||||
While convenient, this approach requires users to trust the data returned and represents a pale imitation of the true revolutionary promise of blockchain technology.
|
||||
While convenient, this approach requires users to trust the data returned and represents a pale imitation of the true revolutionary promise of decentralized blockchain technology.
|
||||
|
||||
Nimbus Portal—our light client implementation—is among a few promising efforts to develop an Ethereum light client. Its development is part of a cross-team Ethereum Foundation initiative called Portal Network that seeks to realize the light client vision.
|
||||
Nimbus Porta Client, our light client implementation known as “Fluffy”, is among a few promising efforts to develop an Ethereum light client. Its development is part of a cross-team Ethereum Foundation initiative called Portal Network that seeks to realize the light client vision.
|
||||
|
||||
Alongside Nimbus Portal, Nimbus has developed a Light Web Proxy that can run in the background of applications, providing on-chain data directly to wallet apps and Ethereum-native operating systems, among other use cases.
|
||||
|
||||
Ultimately, light clients will provide greater security to users, reveal new blockchain use cases and enable the Ethereum ecosystem to reduce its dependency on centralized entities that represent single points of failure or capture.
|
||||
Ultimately, light clients will provide greater security to users, reveal new blockchain use cases, and enable the Ethereum ecosystem to reduce its dependency on centralized entities that represent single points of failure or capture.
|
||||
|
||||
[See the docs](https://github.com/status-im/nimbus-eth2)
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: About
|
|||
sidebar_position: 1
|
||||
---
|
||||
|
||||
Nimbus was created to promote client diversity and network decentralization on Ethereum in the belief that blockchain technology's full transformative potential can only be realized if running its infrastructure is widely accessible.
|
||||
Nimbus was created to promote client diversity and network decentralization on Ethereum, with the belief that blockchain technology's full transformative potential can only be realized if running Ethereum infrastructure is widely accessible.
|
||||
|
||||
Alongside its work building Ethereum clients, Nimbus lends its expertise in decentralized systems to the [Logos Collective](https://logos.co/)—a network of aligned projects and contributors building trust-minimized, corruption-resistant governing services and social institutions for its citizens. Nimbus is one of the Logos Collective's foundational projects.
|
||||
|
||||
|
|
@ -11,11 +11,11 @@ Alongside its work building Ethereum clients, Nimbus lends its expertise in dece
|
|||
|
||||
### Motivation
|
||||
|
||||
Ethereum's security—its resistance to external threats and censorship—comes from its decentralization. We believe that lowering the barrier to network participation will result in greater decentralization and, consequently, a more resilient network. As such, we are building each of the three Nimbus clients to be as lightweight, secure and easy to use as possible.
|
||||
Ethereum's security—its resistance to external threats and censorship—comes from its decentralization. We believe that lowering the barrier to network participation will result in greater decentralization, and consequently, a more resilient network. As such, we are building each of the three Nimbus clients to be as lightweight, secure, and easy to use as possible.
|
||||
|
||||
The Nimbus consensus client—along with the still-in-development execution and light clients— are designed to perform on a range of systems, including Raspberry Pis and mobile devices, lowering the barrier to entry to run Ethereum's infrastructure. Meanwhile, our resource-conserving optimizations benefit those operating more powerful systems by freeing resources for other tasks, without compromising on reward performance.
|
||||
The Nimbus consensus client, along with the still-in-development execution and light clients, are designed to perform on a range of systems including Raspberry Pis and mobile devices, lowering the barrier to entry to run Ethereum's infrastructure. Meanwhile, our resource-conserving optimizations benefit those operating more powerful systems by freeing resources for other tasks, without compromising on reward performance.
|
||||
|
||||
Those client teams earlier to market than Nimbus have typically developed for higher specification hardware, as one would expect from the first client implementations to serve a new, cutting-edge system like post-Merge Ethereum. While their implementations make for a more diverse client ecosystem and their R&D efforts have pushed the space forward tremendously, there remains a gap for an Ethereum client tailored to lower specification devices, that encourages increased network decentralization. Nimbus fills that gap.
|
||||
Client projects that were earlier to market than Nimbus have typically developed for higher specification hardware, as one would expect from the first client implementations to serve a new, cutting-edge system like post-merge Ethereum. While their implementations make for a more diverse client ecosystem and their R&D efforts have pushed the space forward tremendously, there remains a gap for an Ethereum client tailored to lower specification devices that encourages increased network decentralization. Nimbus fills that gap.
|
||||
|
||||
In addition to striving for maximum accessibility via lighter client implementations, Nimbus' design goals are to provide an architecture that makes it simple to embed Nimbus into other software. The Nimbus Light Web Proxy, for example, enables decentralized applications to verify data received from external RPC endpoints. Consequently, Nimbus reduces reliance on third-party software and service providers that introduce potential vulnerabilities through single points of failure.
|
||||
|
||||
|
|
@ -23,25 +23,10 @@ In addition to striving for maximum accessibility via lighter client implementat
|
|||
|
||||
### Nimbus history
|
||||
|
||||
Status—the creator of the Ethereum-based decentralized messaging application—first announced Nimbus in August 2018 as a client implementation research project focused on sharding, light clients and next-generation Ethereum technologies, with a goal of addressing scalability and accessibility concerns. It was inspired by a vision of the future in which Ethereum "lives" on millions of embedded systems around the world rather than a few thousand powerful computers.
|
||||
Status, the creator of the Ethereum-based decentralized messaging application, first announced Nimbus in August 2018 as a client implementation research project focused on sharding, light clients, and next-generation Ethereum technologies, with a goal of addressing scalability and accessibility concerns. It was inspired by a vision of the future in which Ethereum "lives" on millions of embedded systems around the world rather than a few thousand powerful computers.
|
||||
|
||||
At its creation, Nimbus' goal was to research and build a client light enough to run on such resource-restricted devices and modular enough to allow for rapid iteration and implementation of research. Initially, the team planned to develop an energy- and compute-efficient, mobile-first client for the full web3 tech stack—decentralized logic, decentralized storage and decentralized messaging.
|
||||
At its creation, Nimbus' goal was to research and build a client light enough to run on such resource-restricted devices, and modular enough to allow for rapid iteration and implementation of research. Initially the team planned to develop an energy and compute efficient, mobile-first client for the full web3 tech stack, with decentralized logic, decentralized storage, and decentralized messaging.
|
||||
|
||||
However, as research into the latter two branches slowed, Nimbus narrowed its focus to crafting high-quality, lightweight Ethereum implementations to promote decentralization and strengthen the network against single-client failures.
|
||||
However, as research into the latter two branches slowed, Nimbus narrowed its focus to crafting high-quality, lightweight Ethereum implementations to promote decentralization and strengthen the network against single-client failures.
|
||||
|
||||
Nimbus was announced as a core Logos project in June 2023.
|
||||
|
||||
<br/>
|
||||
|
||||
### Why "Nimbus"?
|
||||
|
||||
The name Nimbus was chosen because of its allusions to:
|
||||
|
||||
- A different kind of "dark cloud" computing.
|
||||
|
||||
- The spiritual symbolism of sanctity and holiness.
|
||||
|
||||
- Nim, the language in which it is written.
|
||||
|
||||
- A "bus" in communications systems architecture.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Development roadmap
|
|||
sidebar_position: 4
|
||||
---
|
||||
|
||||
As a leading Ethereum client implementation already in production, the Nimbus consensus client team's development priorities are largely dependent on Ethereum's core roadmap. Client implementations must support network updates, such as "The Merge" to proof-of-stake, to ensure users face minimal disruption during such events.
|
||||
As a leading Ethereum client implementation already in production, the Nimbus consensus client team's development priorities are largely dependent on Ethereum's core roadmap. Client implementations must support network updates, such as the merge to proof-of-stake, to ensure users face minimal disruption during such events.
|
||||
|
||||
Known future upgrades and ecosystem developments guiding our research and development efforts include:
|
||||
|
||||
|
|
@ -13,11 +13,11 @@ After "The Merge" in 2022, the next major Ethereum upgrade is "The Surge," which
|
|||
|
||||
### Distributed Validator Technology
|
||||
|
||||
DVT is an open-source protocol already use. It enables a group of validators to combine ETH to reach the minimum stake required to operate a validator.
|
||||
DVT is an open-source protocol already in use. It enables a group of validators to combine ETH to reach the minimum stake required to operate a validator.
|
||||
|
||||
Additionally, Nimbus maintains relationships with various user types, including solo stakers and liquid staking protocol operators, to ensure their feedback informs our work on the client implementations.
|
||||
|
||||
Consequently, Nimbus development follows a monthly update schedule that incorporates the above variables while remaining flexible and adaptive to unforeseen ecosystem advances (and potential crises.) Over the last year, for example, Nimbus has shipped more than 20 updates to its consensus client implementation.
|
||||
Consequently, Nimbus development follows a monthly update schedule that incorporates the above variables while remaining flexible and adaptive to unforeseen ecosystem advances (and potential crises). Over the last year for example, Nimbus has shipped more than 20 updates to its consensus client implementation.
|
||||
|
||||
<br/>
|
||||
|
||||
|
|
@ -31,4 +31,4 @@ Despite this responsive approach, the team is working on several focus areas dur
|
|||
|
||||
- Enhancing the light client, Nimbus Portal.
|
||||
|
||||
[Contribute to Waku](https://github.com/status-im/nimbus-eth2)
|
||||
[Contribute to Nimbus](https://github.com/status-im/nimbus-eth2)
|
||||
|
|
|
|||
|
|
@ -3,28 +3,12 @@ title: Core contributors
|
|||
sidebar_position: 3
|
||||
---
|
||||
|
||||
The Nimbus client suite is built and maintained by a passionate and driven team of 10 technologists from around the world.
|
||||
The Nimbus client suite is built and maintained by a passionate and driven team of technologists from around the world.
|
||||
|
||||
Development work is divided into subgroups, each focusing on one of the three client implementations. Skillsets and requirements often overlap, meaning that some members take on responsibilities across the subgroups. Additionally, several team members are core contributors to Nim, the programming language in which Nimbus clients are written.
|
||||
|
||||
<br/>
|
||||
The three subgroups include Nimbus Consensus, Nimbus Execution, and Nimbus Portal. Team members include development leads, supporting developers, research officers and engineers, and data scientists.
|
||||
|
||||
### Nimbus consensus
|
||||
|
||||
The team maintaining the in-production Nimbus consensus client consists of a development lead, two supporting developers, a research officer and a senior data scientist. Combined, they draw on decades of experience both within the crypto and web3 sector, and at more traditional tech startups.
|
||||
|
||||
<br/>
|
||||
|
||||
### Nimbus execution
|
||||
|
||||
Building the Nimbus execution client is a team consisting of a development lead, supporting developer, research engineer and software engineer. Like the consensus subgroup, the Nimbus execution client team has a rich background in software development both within web3 and beyond it.
|
||||
|
||||
<br/>
|
||||
|
||||
### Nimbus Portal
|
||||
|
||||
Currently, the light client, Nimbus Portal, has one full-time developer with a background in software engineering and consultancy at various tech startups.
|
||||
|
||||
Nimbus is looking to expand the above structure and currently has multiple openings for core contributors. As an open-source public goods project Nimbus also welcomes community contributions.
|
||||
Nimbus is looking to expand the above structure and currently has multiple openings for core contributors. As an open-source public goods project Nimbus also welcomes community contributions.
|
||||
|
||||
[Work with us](https://jobs.status.im/)
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ import {
|
|||
FeatureList,
|
||||
Showcase,
|
||||
HeroInfo,
|
||||
Box,
|
||||
Box
|
||||
} from '../components/mdx'
|
||||
|
||||
<Hero size="large">
|
||||
|
|
|
|||
Loading…
Reference in New Issue