Skip to content

Commit

Permalink
fix: added correct graph
Browse files Browse the repository at this point in the history
  • Loading branch information
troykessler committed Sep 18, 2023
1 parent 394b35c commit 05f8e65
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions docs/validators/protocol_nodes/pools/archway/introduction.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,6 @@ sidebar_position: 1
This data pool validates and archives all blocks and block results from Archway and makes them permanently
available with Arweave and Bundlr.


:::info
**INFO**: The Archway pool is currently **not** live on Mainnet, only on Kaon and Korellia.
:::
Expand All @@ -19,6 +18,7 @@ available with Arweave and Bundlr.
- **Data**: Blocks from Genesis ongoing
- **Storage Provider**: Bundlr
- **Networks**
- [Mainnet](https://app.kyve.network/#/pools/2) (Pool Id: 2)
- [Kaon](https://app.kaon.kyve.network/#/pools/2) (Pool Id: 2)
- [Korellia](https://app.korellia.kyve.network/#/pools/31) (Pool Id: 31)
- **Min Hardware Requirements**
Expand Down Expand Up @@ -52,4 +52,4 @@ data are the blocks and the block results from the tendermint application - vali
The goal of this pool is to validate and archive all blocks and block results from Archway permanently and decentralized. With this
data we want to make it possible for other nodes to block sync the data from KYVE, making expensive archival nodes
on Archway obsolete in the long run. More information on how to perform block sync with KYVE visit the documentation about
KSYNC [here](https://github.com/KYVENetwork/ksync). In addition, the validated archived block results enable a number of further use cases for data analysis.
KSYNC [here](https://github.com/KYVENetwork/ksync). In addition, the validated archived block results enable a number of further use cases for data analysis.
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ actual KYVE protocol validator.
This architecture diagram summarizes the setup of the Axelar integration on KYVE:

<p align="center">
<img width="90%" src="/img/tendermint_archway.png" />
<img width="90%" src="/img/tendermint_axelar.png" />
</p>

Here the tendermint runtime is responsible for communicating with the tendermint application (purple) - in this case archwayd, and forwarding the data to the KYVE core protocol. The KYVE core then handles the communication with the pool. This entire process (yellow) is the KYVE protocol validator. The resulting
Expand Down
Binary file added static/img/tendermint_axelar.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

1 comment on commit 05f8e65

@vercel
Copy link

@vercel vercel bot commented on 05f8e65 Sep 18, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please sign in to comment.