docs: update copy
This commit is contained in:
Amelia7689
Jinho Jang
parent
28014a2eaf
commit
a410df1c66
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Nimbus Clients
|
||||
title: Nimbus clients
|
||||
sidebar_position: 1.1
|
||||
sidebar_label: Nimbus clients
|
||||
hide_table_of_contents: true
|
||||
|
|
@ -22,7 +22,7 @@ The Nimbus consensus client offers significant advantages for all levels of user
|
|||
|
||||
- Light and high performing: Nimbus consensus client strives to be as lightweight and high performing 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.
|
||||
- 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.
|
||||
|
||||
- Convenient: Nimbus will be among the first client teams to offer both a consensus and execution client, simplifying initial installation and making it easy for operators to receive tailored support.
|
||||
|
||||
|
|
@ -30,9 +30,9 @@ View the [Github repository](https://github.com/status-im/nimbus-eth1/tree/maste
|
|||
|
||||
## Verified web3 proxy
|
||||
|
||||
Nimbus is working with ethOS on a native and embedded proof of concept to provide additional protections with the Verified Web3 Proxy. The Ethereum JSON-RPC proxy uses the beacon chain light client sync protocol to verify the data supplied by any Ethereum node in order to deliver a new type of ultra light Ethereum client. It enables trust in data from potentially untrustworthy sources by having the proxy perform real-time verification.
|
||||
Nimbus is working with ethOS on a native and embedded proof of concept to provide additional protections with the verified web3 proxy. The Ethereum JSON-RPC proxy uses the beacon chain light client sync protocol to verify the data supplied by any Ethereum node in order to deliver a new type of ultra light Ethereum client. It enables trust in data from potentially untrustworthy sources by having the proxy perform real-time verification.
|
||||
|
||||
It simply requires user to set up a light web3 proxy on their phone and scan the proxy which fetches the state root from the LC network. This allows the proxy to request the balance and proof from any provider or untrusted node, checking this against the state root and verifies the balance.
|
||||
It simply requires the user to set up a light web3 proxy on their phone and scan the proxy, which fetches the state root from the LC network. This allows the proxy to request the balance and proof from any provider or untrusted node, checking this against the state root and verifying the balance.
|
||||
|
||||
View the [Github repository.](https://github.com/status-im/nimbus-eth1/tree/master/nimbus_verified_proxy)
|
||||
|
||||
|
|
@ -42,9 +42,9 @@ The absence of true light clients presents a major issue in web3 because it cont
|
|||
|
||||
While convenient, this approach requires users to trust the data returned and represents a pale imitation of the true revolutionary promise of decentralised blockchain technology.
|
||||
|
||||
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 realise the light client vision.
|
||||
Nimbus portal 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 realise 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.
|
||||
Alongside the portal client, Nimbus has developed a light, verified web3 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 centralised entities that represent single points of failure or capture.
|
||||
|
||||
|
|
@ -52,9 +52,9 @@ Ultimately, light clients will provide greater security to users, reveal new blo
|
|||
View the [Github repository](https://github.com/status-im/nimbus-eth1/tree/master/fluffy) or [read more.](nimbus.team/docs/fluffy)
|
||||
|
||||
## Execution 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.
|
||||
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 execution layer and consensus layer 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 execution layer and consensus layer clients will make for a user-friendly and convenient option for all Ethereum node operator levels in terms of 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -46,8 +46,8 @@ import { AccordionItem } from '@site/src/components/mdx'
|
|||
The best way to contact the Nimbus team for support, is through <a href="https://discord.gg/XRxWahP" target="_blank">Discord</a> in the #helpdesk channel.
|
||||
</AccordionItem>
|
||||
|
||||
<AccordionItem title="Can we use a LH/Prysm beacon node with Nimbus VC?">
|
||||
Yes, Nimbus VC works well with alternative beacon node setups. If you require support for such a setup, please reach out in the #helpdesk channel or refer to the <a href="https://nimbus.guide/validator-client.html" target="_blank">Nimbus Guide</a>.
|
||||
<AccordionItem title="Can we use a LH/Prysm Beacon Node with Nimbus VC?">
|
||||
Yes, Nimbus VC works well with alternative Beacon Node setups. If you require support for such a setup, please reach out in the #helpdesk channel or refer to the <a href="https://nimbus.guide/validator-client.html" target="_blank">Nimbus Guide</a>.
|
||||
</AccordionItem>
|
||||
|
||||
<AccordionItem title="How many validators can we run per machine?">
|
||||
|
|
|
|||
|
|
@ -4,21 +4,19 @@ sidebar_position: 1
|
|||
hide_table_of_contents: true
|
||||
---
|
||||
|
||||
Nimbus was created to promote client diversity and network decentralisation on Ethereum, with the belief that blockchain technology's full transformative potential can only be realised if running Ethereum infrastructure is widely accessible.
|
||||
|
||||
Alongside its work building Ethereum clients, Nimbus lends its expertise in decentralised systems to the [Logos Collective](https://logos.co/)—a network of aligned projects and contributors building trust-minimised, corruption-resistant governing services and social institutions for its citizens. Nimbus is one of the Logos Collective's foundational projects.
|
||||
Nimbus was created to promote client diversity and network decentralisation on Ethereum, believing that blockchain technology's full transformative potential can only be realised if running Ethereum infrastructure is widely accessible.
|
||||
|
||||
<br/>
|
||||
|
||||
### Motivation
|
||||
|
||||
Ethereum's security—its resistance to external threats and censorship—comes from its decentralisation. We believe that lowering the barrier to network participation will result in greater decentralisation, 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 decentralisation. We believe that lowering the barrier to network participation will result in greater decentralisation 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, is 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.
|
||||
|
||||
Client projects that were earlier to the network than Nimbus have typically developed for higher specification hardware, as one would expect from the first client implementations. While these other 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 encourage increased network decentralisation while delivering the same level of stability and reward performance expected from any Ethereum client. 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 decentralised 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.
|
||||
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. For example, the verified web3 proxy enables decentralised 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.
|
||||
|
||||
<br/>
|
||||
|
||||
|
|
@ -26,8 +24,8 @@ In addition to striving for maximum accessibility via lighter client implementat
|
|||
|
||||
Status, the creator of the Ethereum-based decentralised 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, with decentralised logic, decentralised storage, and decentralised 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 decentralised logic, decentralised storage, and decentralised messaging.
|
||||
|
||||
However, as research into the latter two branches slowed, Nimbus narrowed its focus to crafting high-quality, lightweight Ethereum implementations to promote decentralisation and strengthen the network against single-client failures.
|
||||
|
||||
Nimbus was announced as a core Logos project in June 2023.
|
||||
Nimbus is supported by the [Institute of Free Technology](https://free.technology/) as a member of its startup portfolio.
|
||||
|
|
|
|||
|
|
@ -8,17 +8,17 @@ As a leading Ethereum client implementation already in production, the Nimbus co
|
|||
|
||||
Known future upgrades and ecosystem developments guiding our research and development efforts include:
|
||||
|
||||
### EIP-4844 (proto-danksharding)
|
||||
### Dencun hardfork
|
||||
|
||||
After "The Merge" in 2022, the next major Ethereum upgrade is "The Surge," which aims to significantly increase the network's maximum transaction throughput via the implementation of an early form of sharding. The upgrade is expected in Q3 or Q4 2023.
|
||||
After "The Merge" in 2022, the next major Ethereum upgrade is "The Surge," which aims to significantly increase the network's maximum transaction throughput via the implementation of an early form of sharding. The Dencun hard fork is anticipated to go live on mainnet in Q2 2024.
|
||||
|
||||
### Distributed Validator Technology
|
||||
### Distributed validator technology
|
||||
|
||||
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/>
|
||||
|
||||
|
|
@ -28,8 +28,8 @@ Despite this responsive approach, the team is working on several focus areas dur
|
|||
|
||||
- Supporting EIP-4844 and distributed validator protocols.
|
||||
|
||||
- Releasing the Nimbus execution client—expected early 2024
|
||||
- Releasing the Nimbus execution client—expected in mid-2024
|
||||
|
||||
- Enhancing the light client, Nimbus Portal.
|
||||
- Enhancing the light Nimbus portal client.
|
||||
|
||||
[Contribute to Nimbus](https://github.com/status-im/nimbus-eth2)
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ The Nimbus client suite is built and maintained by a passionate and driven team
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ We use funds from donations to:
|
|||
|
||||
If you'd like to donate a conditional amount, i.e. one that depends on a certain milestone or deadline, please [get in touch](mailto:jacek@status.im).
|
||||
|
||||
## How To Get Involved with Nimbus' development
|
||||
## How to get involved with Nimbus' development
|
||||
|
||||
- look around [the repo](https://github.com/status-im/nimbus-eth2), especially the [open issues](https://github.com/status-im/nimbus-eth2/issues)
|
||||
- check out some [open bounties](https://gitcoin.co/explorer?keywords=nimbus&order_by=-web3_created)
|
||||
|
|
@ -31,7 +31,7 @@ make update
|
|||
|
||||
[Build](/docs/eth2.html) and start hacking!
|
||||
|
||||
## Thought Experiments
|
||||
## Thought experiments
|
||||
|
||||
<blockquote className="twitter-tweet" data-theme="dark"><p lang="en" dir="ltr">Still hoping to just have my <a href="https://twitter.com/ethstatus?ref_src=twsrc%5Etfw">@ethstatus</a> desktop wallet be my bn, and have my mobile device be my <a href="https://twitter.com/ethnimbus?ref_src=twsrc%5Etfw">@ethnimbus</a> vc 🤷🏽♀️😅. And then a nice little Rocketpool Staas run by <a href="https://twitter.com/search?q=%24SNT&src=ctag&ref_src=twsrc%5Etfw">$SNT</a>... And anonymous staking in "dark pools" build on application layer, fees paid to client/network nodes. 👌🏽😻.</p>— chloethedev.eth ⟠ δούλος 🏳️⚧️ (@Chloethedev) <a href="https://twitter.com/Chloethedev/status/1320710462032515072?ref_src=twsrc%5Etfw">October 26, 2020</a></blockquote>
|
||||
|
||||
|
|
|
|||
|
|
@ -42,7 +42,7 @@ import { Button } from '@acid-info/lsd-react'
|
|||
</Hero>
|
||||
|
||||
<Box>
|
||||
<SectionHeader noBorder title="Nimbus Clients"></SectionHeader>
|
||||
<SectionHeader noBorder title="Nimbus clients"></SectionHeader>
|
||||
<Box top={{ xs: 64 }}>
|
||||
<Grid
|
||||
xs={{ cols: 2, wrap: true, gap: '1.5rem 1em' }}
|
||||
|
|
@ -51,8 +51,8 @@ import { Button } from '@acid-info/lsd-react'
|
|||
<Grid.Item>
|
||||
<ShowcaseCard
|
||||
index={1}
|
||||
name="Consensus Client"
|
||||
description="Monitor the beacon chain and join the network as a validator to participate in proof of stake consensus."
|
||||
name="Consensus client"
|
||||
description="Monitor the Beacon Chain and join the network as a validator to participate in proof of stake consensus."
|
||||
borderStyle="none"
|
||||
cta={{
|
||||
label: 'Read more',
|
||||
|
|
@ -64,7 +64,7 @@ import { Button } from '@acid-info/lsd-react'
|
|||
<Grid.Item>
|
||||
<ShowcaseCard
|
||||
index={2}
|
||||
name="Verified Web3 Proxy"
|
||||
name="Verified web3 proxy"
|
||||
description="Independently verify data received from RPC endpoints and add a layer of protection."
|
||||
borderStyle="none"
|
||||
cta={{
|
||||
|
|
@ -77,7 +77,7 @@ import { Button } from '@acid-info/lsd-react'
|
|||
<Grid.Item>
|
||||
<ShowcaseCard
|
||||
index={3}
|
||||
name="Portal Client"
|
||||
name="Portal client"
|
||||
description="An ultra-light client that enables users to interact with the Ethereum blockchain in a trust-minimised manner."
|
||||
borderStyle="none"
|
||||
cta={{
|
||||
|
|
@ -90,7 +90,7 @@ import { Button } from '@acid-info/lsd-react'
|
|||
<Grid.Item>
|
||||
<ShowcaseCard
|
||||
index={4}
|
||||
name="Execution Client"
|
||||
name="Execution client"
|
||||
description="A lightweight execution layer client to complement the consensus client - coming soon."
|
||||
borderStyle="none"
|
||||
cta={{
|
||||
|
|
@ -109,21 +109,21 @@ import { Button } from '@acid-info/lsd-react'
|
|||
id="clients"
|
||||
alignment="top"
|
||||
ctaPosition="top"
|
||||
title="Nimbus Attributes"
|
||||
title="Nimbus attributes"
|
||||
indexStyle="number"
|
||||
borderStyle="none"
|
||||
features={[
|
||||
{
|
||||
title: 'Easy to use',
|
||||
description: <>Nimbus offers a simple and easy to use consensus layer client that combines beacon node and validator client duties in one package, while also offering the flexibility to run the two independently.</>
|
||||
description: <>Nimbus offers a simple and easy to use consensus layer client that combines Beacon Node and validator client duties in one package, while also offering the flexibility to run the two independently.</>
|
||||
},
|
||||
{
|
||||
title: 'Lightweight',
|
||||
description: "Nimbus' low resource footprint makes it an attractive option for solo stakers. It's low CPU and Memory consumption is also attractive for Institutional node operators, as it leaves more headroom on a server for when Ethereum network is under stress, reducing the risk of failover."
|
||||
description: "Nimbus' low resource footprint makes it an attractive option for solo stakers. It's low CPU and memory consumption is also attractive for Institutional node operators, as it leaves more headroom on a server for when Ethereum network is under stress, reducing the risk of failover."
|
||||
},
|
||||
{
|
||||
title: 'Resilient',
|
||||
description: "Nimbus offers the ability to connect the validator client with multiple beacon nodes. It also supports connection with multiple execution layer clients, creating redundancy and resilience in your setup."
|
||||
description: "Nimbus offers the ability to connect the validator client with multiple Beacon Nodes. It also supports connection with multiple execution layer clients, creating redundancy and resilience in your setup."
|
||||
},
|
||||
{
|
||||
title: 'Secure',
|
||||
|
|
@ -139,26 +139,26 @@ import { Button } from '@acid-info/lsd-react'
|
|||
title="Get started"
|
||||
description={
|
||||
<>
|
||||
Run the Nimbus Consensus Client <br/>in one of three ways
|
||||
Run the Nimbus consensus client <br/>in one of three ways
|
||||
</>
|
||||
}
|
||||
border={false}
|
||||
list={[
|
||||
{
|
||||
title: 'Simple setup',
|
||||
description: "Setup the Nimbus Beacon Node with Validator Client duties built in.",
|
||||
description: "Setup the Nimbus Beacon Node with validator client duties built in.",
|
||||
href: 'https://nimbus.guide/quick-start.html',
|
||||
target: '_blank',
|
||||
},
|
||||
{
|
||||
title: 'Beacon Node setup',
|
||||
description: "Use Nimbus Beacon Node with an alternative Validator Client.",
|
||||
description: "Use Nimbus Beacon Node with an alternative validator client.",
|
||||
href: 'https://nimbus.guide/validator-client.html',
|
||||
target: '_blank',
|
||||
},
|
||||
{
|
||||
title: 'Validator setup',
|
||||
description: "Use Nimbus Validator client with an alternative Beacon Node.",
|
||||
description: "Use Nimbus validator client with an alternative Beacon Node.",
|
||||
href: 'https://nimbus.guide/validator-client.html',
|
||||
target: '_blank',
|
||||
},
|
||||
|
|
@ -231,7 +231,7 @@ import { Button } from '@acid-info/lsd-react'
|
|||
|
||||
<Box top={{ xs: 144, lg: 190 }}>
|
||||
<LogoCarousel
|
||||
title="Nimbus Users"
|
||||
title="Nimbus users"
|
||||
items={[
|
||||
{
|
||||
logoSrc: "/showcase/diva-dark.svg",
|
||||
|
|
@ -329,13 +329,13 @@ import { Button } from '@acid-info/lsd-react'
|
|||
<a href="https://github.com/status-im/nimbus-eth2" target='_blank'>
|
||||
<Button className='link-button' size='small'>
|
||||
<div alt="GitHub" class='header-github-link' />
|
||||
<p>Consensus Client</p>
|
||||
<p>Consensus client</p>
|
||||
</Button>
|
||||
</a>
|
||||
<a href="https://github.com/status-im/nimbus-eth1" target='_blank'>
|
||||
<Button className='link-button' size='small'>
|
||||
<div alt="GitHub" class='header-github-link' />
|
||||
<p>Execution Client</p>
|
||||
<p>Execution client</p>
|
||||
</Button>
|
||||
</a>
|
||||
</div>
|
||||
|
|
@ -344,11 +344,11 @@ import { Button } from '@acid-info/lsd-react'
|
|||
<CallToActionSection
|
||||
columns={1}
|
||||
title="Support"
|
||||
description="As a web3 public good, largely dependent on both Status and the Ethereum Foundation for funding, grants are our lifeblood. Donate to Nimbus and to support us in our pursuit for building and maintaining the lightest Ethereum clients accessible to all."
|
||||
description="As a web3 public good that is largely dependent on both Status and the Ethereum Foundation for funding, grants are our lifeblood. Donate to Nimbus and support us in our pursuit of building and maintaining the lightest Ethereum clients accessible to all."
|
||||
border={false}
|
||||
label="Donate"
|
||||
target="_blank"
|
||||
href="https://etherscan.io/address/0xDeb4A0e8d9a8dB30a9f53AF2dCc9Eb27060c6557s"
|
||||
href="https://etherscan.io/address/0xDeb4A0e8d9a8dB30a9f53AF2dCc9Eb27060c6557"
|
||||
/>
|
||||
</Grid.Item>
|
||||
</Grid>
|
||||
|
|
@ -369,23 +369,23 @@ import { Button } from '@acid-info/lsd-react'
|
|||
},
|
||||
{
|
||||
period: [2020],
|
||||
description: "Runs 144 validators on mainnet at beacon chain launch"
|
||||
description: "Runs 144 validators on mainnet at Beacon Chain launch"
|
||||
},
|
||||
{
|
||||
period: [2021],
|
||||
description: "Nimbus receives EF grant to develop an Execution Client"
|
||||
description: "Nimbus receives EF grant to develop an execution client"
|
||||
},
|
||||
{
|
||||
period: [2022],
|
||||
description: "Feature enhancements to Nimbus Consensus Client and continued work on Execution Client"
|
||||
description: "Feature enhancements to Nimbus consensus client and continued work on execution client"
|
||||
},
|
||||
{
|
||||
period: [2023],
|
||||
description: "Improved resilience and performance of Consensus Client from multi-BN, multi-EL support"
|
||||
description: "Improved resilience and performance of consensus client from multi-BN, multi-EL support"
|
||||
},
|
||||
{
|
||||
period: [2024],
|
||||
description: "Nimbus Execution Client launch on mainnet"
|
||||
description: "Nimbus execution client launch on mainnet"
|
||||
},
|
||||
{
|
||||
period: [2024],
|
||||
|
|
@ -393,7 +393,7 @@ import { Button } from '@acid-info/lsd-react'
|
|||
},
|
||||
{
|
||||
period: [2024],
|
||||
description: "Distributed Validator features and improvements to the Nimbus Consensus Client"
|
||||
description: "Distributed validator features and improvements to the Nimbus consensus client"
|
||||
},
|
||||
]}
|
||||
>
|
||||
|
|
|
|||
Loading…
Reference in New Issue