update preset and content
This commit is contained in:
jinhojang6
Jinho Jang
parent
d330684333
commit
3d292081fa
|
|
@ -9,7 +9,7 @@ From their programming language upward, Nimbus clients are optimized to conserve
|
|||
|
||||
- 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 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.
|
||||
|
||||
|
|
@ -17,21 +17,22 @@ From their programming language upward, Nimbus clients are optimized to conserve
|
|||
|
||||
- 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.
|
||||
|
||||
<br/>
|
||||
|
||||
### 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.
|
||||
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.
|
||||
|
||||
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.
|
||||
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 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 also can run Nimbus together with other workloads on their server to reduce overall costs.
|
||||
- **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.
|
||||
|
||||
- **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.
|
||||
|
||||
|
|
@ -39,17 +40,15 @@ The Nimbus consensus client offers significant advantages for all levels of user
|
|||
|
||||
<br/>
|
||||
|
||||
### 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.
|
||||
|
||||
<br/>
|
||||
|
||||
|
||||
|
||||
<br/>
|
||||
|
||||
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.
|
||||
### 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.
|
||||
|
||||
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.
|
||||
|
||||
|
|
@ -57,13 +56,13 @@ Like the Nimbus consensus client, the execution client is written in Nim and des
|
|||
|
||||
### Nimbus Portal
|
||||
|
||||
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 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.
|
||||
|
||||
While convenient, this approach requires users to trust the data returned and represents a pale imitation of the true revolutionary promise of 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 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.
|
||||
|
||||
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 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.
|
||||
|
||||
|
|
@ -3,25 +3,33 @@ 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 in the belief that blockchain technology's full transformative potential can only be realized if running its infrastructure is widely accessible.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
The Nimbus' consensus client—along with its still-in-development execution and light clients— are designed to perform well 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.
|
||||
<br/>
|
||||
|
||||
### 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.
|
||||
|
||||
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.
|
||||
|
||||
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 end-points. 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. 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.
|
||||
|
||||
<br/>
|
||||
|
||||
### 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" in 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—decentralized logic, decentralized storage and decentralized messaging.
|
||||
|
||||
However, as research into the latter two branches slowed, Nimbus narrowed its focus to crafting a high-quality, lightweight Ethereum implementation 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/>
|
||||
|
||||
|
|
@ -36,3 +44,4 @@ The name Nimbus was chosen because of its allusions to:
|
|||
- Nim, the language in which it is written.
|
||||
|
||||
- A "bus" in communications systems architecture.
|
||||
|
||||
|
|
@ -7,9 +7,13 @@ 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):** 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.
|
||||
### EIP-4844 (proto-danksharding)
|
||||
|
||||
- **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.
|
||||
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.
|
||||
|
||||
### 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.
|
||||
|
||||
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.
|
||||
|
||||
|
|
@ -17,14 +21,14 @@ Consequently, Nimbus development follows a monthly update schedule that incorpor
|
|||
|
||||
<br/>
|
||||
|
||||
### Nimbus focus areas: 2023/24
|
||||
## Nimbus focus areas: 2023/24
|
||||
|
||||
Despite this responsive approach, the team is working on several focus areas during 2023 and 2024, including:
|
||||
|
||||
- Supporting EIP-4844 and distributed validator protocols.
|
||||
- Supporting EIP-4844 and distributed validator protocols.
|
||||
|
||||
- Releasing the Nimbus execution client—expected early 2024
|
||||
|
||||
- Enhancing the light client, Nimbus Portal.
|
||||
- Enhancing the light client, Nimbus Portal.
|
||||
|
||||
[Contribute to Waku](https://github.com/status-im/nimbus-eth2)
|
||||
|
|
@ -3,7 +3,7 @@ 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 10 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.
|
||||
|
||||
|
|
@ -26,3 +26,5 @@ Building the Nimbus execution client is a team consisting of a development lead,
|
|||
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.
|
||||
|
||||
[Work with us](https://jobs.status.im/)
|
||||
|
|
@ -5,7 +5,7 @@ require('dotenv').config()
|
|||
/** @type {import('@docusaurus/types').Config} */
|
||||
const config = {
|
||||
title: 'Nimbus',
|
||||
url: 'https://url',
|
||||
url: 'https://nimbus.team/',
|
||||
baseUrl: '/',
|
||||
|
||||
customFields: {
|
||||
|
|
@ -36,19 +36,25 @@ const config = {
|
|||
},
|
||||
},
|
||||
docs: {
|
||||
routeBasePath: '/about',
|
||||
versions: {
|
||||
current: {
|
||||
label: 'current',
|
||||
},
|
||||
},
|
||||
lastVersion: 'current',
|
||||
routeBasePath: '/',
|
||||
path: 'root-pages',
|
||||
},
|
||||
}),
|
||||
],
|
||||
],
|
||||
themes: ['@docusaurus/theme-mermaid'],
|
||||
|
||||
plugins: [
|
||||
[
|
||||
'@docusaurus/plugin-content-docs',
|
||||
{
|
||||
id: 'about',
|
||||
routeBasePath: '/about',
|
||||
path: 'about',
|
||||
},
|
||||
],
|
||||
],
|
||||
|
||||
themeConfig:
|
||||
/** @type {import('@acid-info/logos-docusaurus-preset').ThemeConfig} */
|
||||
({
|
||||
|
|
@ -65,10 +71,6 @@ const config = {
|
|||
label: 'About',
|
||||
to: '/about',
|
||||
},
|
||||
{
|
||||
label: 'Blog',
|
||||
href: '/',
|
||||
},
|
||||
{
|
||||
label: 'Github',
|
||||
href: 'https://github.com/status-im',
|
||||
|
|
@ -93,7 +95,7 @@ const config = {
|
|||
label: 'Docs',
|
||||
},
|
||||
{
|
||||
href: '/',
|
||||
href: 'https://github.com/status-im',
|
||||
label: 'Github',
|
||||
},
|
||||
],
|
||||
|
|
@ -109,11 +111,7 @@ const config = {
|
|||
label: 'Work with us',
|
||||
},
|
||||
{
|
||||
href: '/',
|
||||
label: 'Privacy policy',
|
||||
},
|
||||
{
|
||||
href: '/',
|
||||
href: '/terms',
|
||||
label: 'Terms & conditions',
|
||||
},
|
||||
],
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@
|
|||
"typecheck": "tsc"
|
||||
},
|
||||
"dependencies": {
|
||||
"@acid-info/logos-docusaurus-preset": "^1.0.0-alpha.4",
|
||||
"@acid-info/logos-docusaurus-preset": "^1.0.0-alpha.13",
|
||||
"@docusaurus/core": "2.4.1",
|
||||
"@docusaurus/preset-classic": "2.4.1",
|
||||
"@docusaurus/theme-mermaid": "^2.4.1",
|
||||
|
|
|
|||
|
|
@ -0,0 +1,67 @@
|
|||
# Terms of Use
|
||||
|
||||
These terms and conditions (“**Website Terms of Use**”) are entered into by you and us, and they govern your access and use of the Website, including any content and functionality contained in the Website.
|
||||
|
||||
It is your responsibility to read the Website Terms of Use carefully before your use of the Website and your use of the Website means you have agreed to be bound and comply with these Website Terms of Use.
|
||||
|
||||
If you do not agree with these Website Terms of Use, you must not access or use the Website.
|
||||
|
||||
### Content provided for informational purposes only
|
||||
|
||||
Content available on the Website is for informational purposes only and is not intended to address the specific circumstances of any particular individual or entity. Such content may not always be entirely accurate, complete, or up to date and may also include inaccuracies or typographical errors. You are solely responsible for verifying their adequacy, completeness and accuracy and any reliance you place on such content is at your own risk.
|
||||
|
||||
None of the content on this Website should be considered by you as legal, tax, investment, financial, professional or any other type of advice. You should always conduct your own research and seek independent professional advice if necessary. You are solely responsible for the decisions or actions you might take in this respect. We are not liable for any loss resulting from your action (or inaction) and decisions based on this content on this Website.
|
||||
|
||||
Additionally, we are not responsible for any information, content, or services contained in any third-party content or on any third-party websites accessible or linked through this website.
|
||||
|
||||
### Intellectual property rights
|
||||
|
||||
The Website and its contents are made available under free and open source licences. This means that anyone can use, share, and modify such content, as long as they follow the terms of the applicable licence.
|
||||
|
||||
### Third party website links
|
||||
|
||||
To the extent the Website provides any links to a third party website, then their terms and conditions, including privacy policies, govern your use of those third party websites. We have no control over such third party websites and will not be liable for your use of or activities on any third party websites accessed through the Website. If you access such third party websites through the Website, it is at your own risk and you are solely responsible for your activities on such third party websites.
|
||||
|
||||
### Disclaimer
|
||||
|
||||
The Website is provided by us on an ‘as is’ basis and you use the Website at your own sole discretion and risk.
|
||||
|
||||
We disclaims all warranties of any kind, express or implied, including without limitation the warranties of merchantability, fitness for a particular purpose, and non-infringement of intellectual property or other violation of rights. We do not warrant or make any representations concerning the completeness, accuracy, legality, utility, reliability, suitability or availability of the use of the Website, the content on this Website or otherwise relating to the Website, such content or on any sites linked to this site.
|
||||
|
||||
We make no claims that the Website or any of its content is accessible, legally compliant or appropriate in your jurisdiction. Your access or use of the Website is at your own sole discretion and you are solely responsible for complying with any applicable local laws. These disclaimers will apply to the maximum extent permitted by applicable law.
|
||||
|
||||
### Limitation of liability
|
||||
|
||||
We will not be held liable to you under any contract, negligence, strict liability, or other legal or equitable theory for any lost profits, cost of procurement for substitute services, or any special, incidental, or consequential damages related to, arising from, or in any way connected with these Website Terms of Use, the Website, the content on the Website, or your use of the Website, even if we have been advised of the possibility of such damages. In any event, our aggregate liability for such claims is limited to EUR 100 (one hundred Euros). This limitation of liability will apply to the maximum extent permitted by applicable law.
|
||||
|
||||
### Indemnity
|
||||
|
||||
You shall indemnify us and hold us harmless from and against any and all claims, damages and expenses, including attorneys’ fees, arising from or related to your use of the Website, the content on the Website, including without limitation your violation of these Website Terms of Use.
|
||||
|
||||
### Modifications
|
||||
|
||||
We may modify or replace any part of this Website Terms of Use at any time and without notice. You are responsible for checking the Website periodically for any changes. The new Website Terms of Use will be effective immediately upon its posting on the Website.
|
||||
|
||||
### Governing law
|
||||
|
||||
Swiss law governs these Website Terms of Use and any disputes between you and us, whether in court or arbitration, without regard to conflict of laws provisions.
|
||||
|
||||
### Disputes
|
||||
|
||||
In these terms, “dispute” has the broadest meaning enforceable by law and includes any claim you make against or controversy you may have in relation to these Website Terms of Use, the Website, the content on the Website, or your use of the Website
|
||||
|
||||
We prefer arbitration over litigation as we believe it meets our principle of resolving disputes in the most effective and cost effective manner. You are bound by the following arbitration clause, which waives your right to litigation and to be heard by a judge. Please note that court review of an arbitration award is limited. You also waive all your rights to a jury trial (if any) in any and all jurisdictions.
|
||||
|
||||
If a (potential) dispute arises, you must first use your reasonable efforts to resolve it amicably with us. If these efforts do not result in a resolution of such dispute, you shall then send us a written notice of dispute setting out (i) the nature of the dispute, and the claim you are making; and (ii) the remedy you are seeking.
|
||||
|
||||
If we and you are unable to further resolve this dispute within sixty (60) calendar days of us receiving this notice of dispute, then any such dispute will be referred to and finally resolved by you and us through an arbitration administered by the Swiss Chambers’ Arbitration Institution in accordance with the Swiss Rules of International Arbitration for the time being in force, which rules are deemed to be incorporated herein by reference. The arbitral decision may be enforced in any court. The arbitration will be held in Zug, Switzerland, and may be conducted via video conference virtual/online methods if possible. The tribunal will consist of one arbitrator, and all proceedings as well as communications between the parties will be kept confidential. The language of the arbitration will be in English. Payment of all relevant fees in respect of the arbitration, including filing, administration and arbitrator fees will be in accordance with the Swiss Rules of International Arbitration.
|
||||
|
||||
Regardless of any applicable statute of limitations, you must bring any claims within one year after the claim arose or the time when you should have reasonably known about the claim. You also waive the right to participate in a class action lawsuit or a classwide arbitration against us.
|
||||
|
||||
### About these Website Terms of Use
|
||||
|
||||
These Website Terms of Use cover the entire agreement between you and us regarding the Website and supersede all prior and contemporaneous understandings, agreements, representations and warranties, both written and oral, with respect to the Website.
|
||||
|
||||
The captions and headings identifying sections and subsections of these Website Terms of Use are for reference only and do not define, modify, expand, limit, or affect the interpretation of any provisions of these Website Terms of Use.
|
||||
|
||||
If any part of these Website Terms of Use is held invalid or unenforceable, that part will be severable from these Website Terms of Use, and the remaining portions will remain in full force and effect. If we fail to enforce any of these Website Terms of Use, that does not mean that we have waived our right to enforce them.
|
||||
|
|
@ -5,41 +5,37 @@ import {
|
|||
HeroActions,
|
||||
HeroAction,
|
||||
CallToActionSection,
|
||||
CallToActionButton,
|
||||
FeatureList,
|
||||
Showcase,
|
||||
HeroModel,
|
||||
HeroInfo,
|
||||
Box,
|
||||
} from '../components/mdx'
|
||||
|
||||
<Hero size="large">
|
||||
<Hero size="medium">
|
||||
<HeroInfo>
|
||||
<HeroTitle>The web3 managing standard</HeroTitle>
|
||||
<HeroTitle>Ethereum network participation for everyone</HeroTitle>
|
||||
<HeroDescription>
|
||||
Nimbus promotes client diversity and decentralization on Ethereum by lowering participation barriers and reducing hardware overheads for validators.
|
||||
</HeroDescription>
|
||||
{/*
|
||||
<HeroDescription>
|
||||
Waku is a decentralized communications network that enables private, censorship-resistant messaging for web3 applications.
|
||||
</HeroDescription>
|
||||
* */}
|
||||
<HeroDescription>
|
||||
WAKU IS A DECENTRALIZED COMMUNICATIONS NETWORK.
|
||||
Nimbus promotes client diversity and decentralization on Ethereum
|
||||
</HeroDescription>
|
||||
* */}
|
||||
<HeroActions>
|
||||
<HeroAction href="https://docs.waku.org" target="_blank">
|
||||
Build on Waku
|
||||
</HeroAction>
|
||||
<HeroAction variant="filled" href="https://docs.waku.org" target="_blank">
|
||||
Run Waku
|
||||
<HeroAction variant="filled" href="https://github.com/status-im/nimbus-eth2" target="_blank">
|
||||
Explore Nimbus
|
||||
</HeroAction>
|
||||
</HeroActions>
|
||||
</HeroInfo>
|
||||
<HeroModel
|
||||
modelUrl="/hero/bulanding-generic-hand-01.glb"
|
||||
layout="floating"
|
||||
renderer="ascii"
|
||||
initialX={-0.9831336272264352}
|
||||
initialY={-0.14592188008227222}
|
||||
rotateSpeed={0.1}
|
||||
modelId={'architecture04'}
|
||||
mode={'abstract'}
|
||||
rotateSpeed={0.04}
|
||||
asciiConfig={{
|
||||
characters: ' .,:;ox%# ||| ||| waku @',
|
||||
characters: ' + ^ ^%%%0 -a @@@ ###',
|
||||
}}
|
||||
/>
|
||||
</Hero>
|
||||
|
|
@ -48,61 +44,82 @@ import {
|
|||
id="features"
|
||||
features={[
|
||||
{
|
||||
title: 'Private',
|
||||
title: 'Resource efficiency',
|
||||
description:
|
||||
'Waku leverages cutting-edge zero-knowledge encryption to ensure all messages and associated metadata benefit from rock-solid privacy guarantees.',
|
||||
'Low resource footprints make Nimbus clients more attractive for solo stakers and distributed validators while institutional operators enjoy more headroom when Ethereum is under stress.',
|
||||
},
|
||||
{
|
||||
title: 'Runs anywhere',
|
||||
title: 'Convenient',
|
||||
description:
|
||||
"Waku's modularity enables developers to integrate Waku protocols according to their use case and users' hardware restraints",
|
||||
"Nimbus offers a simple consensus layer setup, combining beacon node and validator clients while also offering the flexibility to run the two independently.",
|
||||
},
|
||||
{
|
||||
title: 'Scalable',
|
||||
title: 'Multiple clients',
|
||||
description:
|
||||
'Waku aims to scale to support millions of users by dividing the flow of messages into shards—not every node needs to forward every message—while discovery protocols ensure users connect to the nodes serving relevant messages.',
|
||||
'Nimbus execution layer and light clients are in development and will bring greater convenience to node operators while empowering network users to verify on-chain data directly.',
|
||||
},
|
||||
{
|
||||
title: 'Secure',
|
||||
title: 'Mission-driven',
|
||||
description:
|
||||
"Waku's native incentivization mechanisms ensure a wide node distribution, making it highly secure and strengthening its privacy assurances.",
|
||||
"Nimbus believes in an internet that is truly free and is owned and operated by the people that use it. All code is open source under MIT and Apache v2 licenses.",
|
||||
},
|
||||
]}
|
||||
/>
|
||||
>
|
||||
<CallToActionButton variant="outlined" href="/about/architect" target="_self">
|
||||
Read More
|
||||
</CallToActionButton>
|
||||
</FeatureList>
|
||||
|
||||
<CallToActionSection
|
||||
title="User adoptions"
|
||||
description="Waku has brought private, censorship-resistant communications to several notable web3 DApps, decentralizing their messaging components:"
|
||||
label="Decentralize your DApp"
|
||||
href="/join"
|
||||
/>
|
||||
<Box top={{ xs: 144, lg: 216 }}>
|
||||
<CallToActionSection
|
||||
title="Used by"
|
||||
columns={2}
|
||||
description="Besides building Ethereum clients, Nimbus lends its expertise in decentralized systems to the Logos Collective—a network of aligned projects and contributors building trust-minimized, corruption-resistant governing services and social institutions."
|
||||
label="Streamline your Ethereum validator setup with Nimbus"
|
||||
href="https://github.com/status-im/nimbus-eth2"
|
||||
/>
|
||||
</Box>
|
||||
|
||||
<Showcase
|
||||
id="showcase"
|
||||
items={[
|
||||
{
|
||||
name: 'XMTP',
|
||||
logo: '/showcase/xmtp-mark-white.svg',
|
||||
description:
|
||||
"Inter-blockchain account messaging protocol XMTP uses Waku's Go implementation to facilitate communication between nodes in its currently permissioned network.",
|
||||
},
|
||||
{
|
||||
name: 'Status',
|
||||
logo: '/showcase/status-mark-white.svg',
|
||||
description:
|
||||
"Waku powers many of the Status super app's features, including its private messaging.",
|
||||
},
|
||||
{
|
||||
name: 'Railgun',
|
||||
logo: '/showcase/railgun-mark-white.svg',
|
||||
description:
|
||||
'The privacy-focused DeFi protocol Railgun anonymizes Ethereum transactions with Waku. ',
|
||||
},
|
||||
]}
|
||||
/>
|
||||
<Box top={{ xs: 64, lg: 100 }}>
|
||||
<Showcase
|
||||
id="showcase"
|
||||
items={[
|
||||
{
|
||||
name: 'Solo stakers',
|
||||
description:
|
||||
"Individual and hobbyist stakers benefit from reduced hardware demands by running Nimbus clients, making participation in Ethereum widely accessible.",
|
||||
},
|
||||
{
|
||||
name: 'Institutional stakers',
|
||||
description:
|
||||
'Operators with high-specification hardware benefit from reduced system load, freeing resources for other tasks.',
|
||||
},
|
||||
{
|
||||
name: 'Distributed validator and mini-pool operators',
|
||||
description:
|
||||
'Benefit from the simplicity and low resource requirements of Nimbus clients. Nimbus is supported by major DV protocols and hardware vendors.',
|
||||
},
|
||||
]}
|
||||
/>
|
||||
</Box>
|
||||
|
||||
<CallToActionSection
|
||||
title="Join the community to discover what Waku can bring to your DApp"
|
||||
label="Decentralize your DApp"
|
||||
href="/join"
|
||||
/>
|
||||
<Box top={{ xs: 144, lg: 216 }}>
|
||||
<CallToActionSection
|
||||
title="Contributors"
|
||||
columns={1}
|
||||
description="Nimbus clients are built and maintained by a group of contributors with extensive software engineering, distributed systems, data science and research expertise that shares a passion for decentralized technologies and democratizing access to their disruptive potential."
|
||||
label="Read more"
|
||||
href="/about/team"
|
||||
target="_self"
|
||||
/>
|
||||
</Box>
|
||||
|
||||
<Box top={{ xs: 144, lg: 216 }}>
|
||||
<CallToActionSection
|
||||
title="Development roadmap"
|
||||
description="Nimbus follows a regular update schedule that is responsive to the Ethereum community's own roadmap, developments in the staking ecosystem and node operator feedback."
|
||||
label="Read more"
|
||||
href="/about/roadmap"
|
||||
target="_self"
|
||||
/>
|
||||
</Box>
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
|
Before Width: | Height: | Size: 69 KiB After Width: | Height: | Size: 46 KiB |
19
yarn.lock
19
yarn.lock
|
|
@ -2,13 +2,13 @@
|
|||
# yarn lockfile v1
|
||||
|
||||
|
||||
"@acid-info/logos-docusaurus-preset@^1.0.0-alpha.4":
|
||||
version "1.0.0-alpha.4"
|
||||
resolved "https://registry.yarnpkg.com/@acid-info/logos-docusaurus-preset/-/logos-docusaurus-preset-1.0.0-alpha.4.tgz#ec958cc49d0420bc361541002138dc0bd8595889"
|
||||
integrity sha512-kVOaa0bCPy5tBJxEZS51N3+UgtO6M4TciRA7x/4JQ+uwy1s5cSldkecmjmb1Ch5/tGB6QCllU2tjuZrsY1aiRg==
|
||||
"@acid-info/logos-docusaurus-preset@^1.0.0-alpha.13":
|
||||
version "1.0.0-alpha.13"
|
||||
resolved "https://registry.yarnpkg.com/@acid-info/logos-docusaurus-preset/-/logos-docusaurus-preset-1.0.0-alpha.13.tgz#da9ef880598a48513b06d66e2b411fe732ef5f05"
|
||||
integrity sha512-pGFblt957C9aYMautNO8oEEQQW7WRQ+7MGbkHbmfJHiSBIaLLrYi5B9Kkj5tud5LoFuZ3qh6Hk2L6WXU7faOCA==
|
||||
dependencies:
|
||||
"@acid-info/logos-docusaurus-search-local" "^1.0.0-alpha.0"
|
||||
"@acid-info/logos-docusaurus-theme" "^1.0.0-alpha.4"
|
||||
"@acid-info/logos-docusaurus-theme" "^1.0.0-alpha.13"
|
||||
"@docusaurus/core" "^2.4.1"
|
||||
"@docusaurus/module-type-aliases" "^2.4.1"
|
||||
"@docusaurus/preset-classic" "^2.4.1"
|
||||
|
|
@ -34,12 +34,11 @@
|
|||
"@easyops-cn/docusaurus-search-local" "^0.33.6"
|
||||
lodash "^4.17.21"
|
||||
|
||||
"@acid-info/logos-docusaurus-theme@^1.0.0-alpha.4":
|
||||
version "1.0.0-alpha.4"
|
||||
resolved "https://registry.yarnpkg.com/@acid-info/logos-docusaurus-theme/-/logos-docusaurus-theme-1.0.0-alpha.4.tgz#63ef02dc4f9acc816bc9bdb7fb5a4664c0a5a3ee"
|
||||
integrity sha512-mQBaIUVVe2LWnKHFfeCnMtLkbCbJxe306DrO+Q2v4f4VXkDiTygXDCd8Rs/DFCPhlyIDRkZRfgH4Fzmb1S+lwA==
|
||||
"@acid-info/logos-docusaurus-theme@^1.0.0-alpha.13":
|
||||
version "1.0.0-alpha.13"
|
||||
resolved "https://registry.yarnpkg.com/@acid-info/logos-docusaurus-theme/-/logos-docusaurus-theme-1.0.0-alpha.13.tgz#de118574ee54f1f7569a0ffd3b3db0688e63ee5f"
|
||||
integrity sha512-nqUvJ/0iKyXiu05NJXTLjmpK1XGUBGvWyStfFNXkRnFPzzaIZ/NfKO84+HKdF1B1OFmQjfBQvAaVrQL/8HYrsw==
|
||||
dependencies:
|
||||
"@acid-info/logos-docusaurus-preset" "^1.0.0-alpha.4"
|
||||
"@acid-info/lsd-react" "^0.1.0-alpha.8"
|
||||
"@docusaurus/core" "^2.4.1"
|
||||
"@docusaurus/mdx-loader" "^2.4.1"
|
||||
|
|
|
|||
Loading…
Reference in New Issue