diff --git a/docs/archway/_category_.json b/docs/archway/_category_.json new file mode 100644 index 00000000..0d4c997f --- /dev/null +++ b/docs/archway/_category_.json @@ -0,0 +1,4 @@ +{ + "label": "Archway", + "position": 2 +} diff --git a/docs/archway/endpoints.mdx b/docs/archway/endpoints.mdx new file mode 100644 index 00000000..3041d1bc --- /dev/null +++ b/docs/archway/endpoints.mdx @@ -0,0 +1,15 @@ +--- +sidebar_position: 1 +description: Endpoints +--- + +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +# Endpoints — API / RPC / gRPC + +> In the Cosmos SDK, the gRPC-gateway translates gRPC endpoints into RESTful ones, enabling users to interact via the REST API. This adaptation is essential for clients that don't natively support gRPC or HTTP2. + +> The RPC endpoint enables users to interact with Archway's nodes, querying the node's state and transmitting transactions within the Archway Network. + +> The gRPC endpoint enables user interactions with a Archway Node through the efficient gRPC framework. In the Cosmos SDK, this protocol is crucial for state queries and transaction broadcasts. diff --git a/docs/archway/img/archway.png b/docs/archway/img/archway.png new file mode 100644 index 00000000..87273cfd Binary files /dev/null and b/docs/archway/img/archway.png differ diff --git a/docs/archway/index.mdx b/docs/archway/index.mdx new file mode 100644 index 00000000..280caa0d --- /dev/null +++ b/docs/archway/index.mdx @@ -0,0 +1,21 @@ +# Archway + +import MainpageMetrics from '@site/src/components/MainpageMetrics'; + + + +[Archway](https://archway.io/) is designed to reward developers and builders for the value they contribute to the protocol. + +- Archway is a smart contract chain within the Cosmos ecosystem that rewards developers for building scalable cross-chain dapps. It's easy to use - just deploy your contracts to the established Proof-of-Stake network for a fast and low-cost experience. +- Archway is built for flexible smart contract development and hassle-free deployment to Cosmos. With contract libraries, the Archway CLI, and the GO CosmWasm SDK available, developers can easily build and deploy their projects. +- Archway is a great platform for developers looking for a simple and rewarding way to build scalable cross-chain dapps and deploy them to the Cosmos network. + +![archway](./img/archway.png) + +[Website](https://archway.io/) | [Blog](https://blog.archway.io/) | [GitHub](https://github.com/archway-network) | [Twitter](https://twitter.com/archwayhq) | [Discord](https://discord.gg/5FVvx3WGfa) | [Docs](https://docs.archway.io/) | [Lightpaper](https://archway.io/lightpaper) + +```mdx-code-block +import DocCardList from '@theme/DocCardList'; + + +``` \ No newline at end of file diff --git a/docs/archway/sync/_category_.json b/docs/archway/sync/_category_.json new file mode 100644 index 00000000..84b2d96a --- /dev/null +++ b/docs/archway/sync/_category_.json @@ -0,0 +1,4 @@ +{ + "label": "Sync", + "position": 2 +} \ No newline at end of file diff --git a/docs/archway/sync/addrbook.mdx b/docs/archway/sync/addrbook.mdx new file mode 100644 index 00000000..61cd8dab --- /dev/null +++ b/docs/archway/sync/addrbook.mdx @@ -0,0 +1,22 @@ +--- +sidebar_position: 4 +description: AddrBook +--- + +# AddrBook + +> Address book refers to a local database or record that a node maintains of all the peers it has come into contact with or learned about. This helps in the peer discovery process. + +import SelectPaste from '@site/src/components/SelectPaste'; + +import { addrBook } from '@site/src/components/SelectPaste/addrBook.ts'; + +export let endpoints = [ + 'https://s3.imperator.co/mainnets-addrbook/archway/addrbook.json', +]; + +export let home = 'archway'; + +export let binary = 'archwayd'; + + diff --git a/docs/archway/sync/snapshot.md b/docs/archway/sync/snapshot.md new file mode 100644 index 00000000..3bb9aa45 --- /dev/null +++ b/docs/archway/sync/snapshot.md @@ -0,0 +1,30 @@ +--- +sidebar_position: 1 +description: Snapshot +--- + +# Snapshot + +> When a new node joins a network, it can use a snapshot — a compressed backup of the chain's data — to quickly synchronize with the current state. Snapshots expedite the process, reducing the need to download and verify every transaction from the beginning. + +:::info +Choose a snapshot from the list and run the commands below. Don't forget to change `snapshot_url`. +::: + +```bash +sudo systemctl stop archwayd + +# make a backup +cp $HOME/.archway/data/priv_validator_state.json $HOME/.archway/priv_validator_state.json.backup + +# reset your node and download a snapshot +archwayd tendermint unsafe-reset-all --home $HOME/.archway --keep-addr-book +wget | lz4 -dc - | tar -xf - -C $HOME/.archway + +# replace the priv_validator_state.json you have backed up +mv $HOME/.archway/priv_validator_state.json.backup $HOME/.archway/data/priv_validator_state.json + +sudo systemctl restart archwayd && sudo journalctl -u archwayd -f -o cat +``` + +A list of Snapshots you can use: \ No newline at end of file diff --git a/docs/archway/sync/state-sync.md b/docs/archway/sync/state-sync.md new file mode 100644 index 00000000..bd1df406 --- /dev/null +++ b/docs/archway/sync/state-sync.md @@ -0,0 +1,22 @@ +--- +sidebar_position: 2 +description: State Sync +--- + +# State Sync + +> State Sync allows new nodes to join a blockchain network by downloading a recent snapshot of the application state instead of processing all historical blocks. This approach is typically faster and requires less data, as the application state is usually more concise than the entire block history. + +import SelectPaste from '@site/src/components/SelectPaste'; + +import { stateSync } from '@site/src/components/SelectPaste/stateSync.ts'; + +export let endpoints = [ + 'https://rpc-archway.imperator.co', +]; + +export let home = 'archway'; + +export let binary = 'archwayd'; + + diff --git a/docs/archway/useful-tools/_category_.json b/docs/archway/useful-tools/_category_.json new file mode 100644 index 00000000..c6e2f5cd --- /dev/null +++ b/docs/archway/useful-tools/_category_.json @@ -0,0 +1,4 @@ +{ + "label": "Useful Resources", + "position": 3 +} \ No newline at end of file diff --git a/docs/archway/useful-tools/explorers.md b/docs/archway/useful-tools/explorers.md new file mode 100644 index 00000000..875fc095 --- /dev/null +++ b/docs/archway/useful-tools/explorers.md @@ -0,0 +1,10 @@ +--- +sidebar_position: 1 +description: Explorers +--- + +# Explorers + +> A block explorer is a search engine that allows users to access and explore the contents of individual blocks, transactions, validators, and addresses on a blockchain. It provides a visual interface to navigate the intricate details of blockchain operations. + +### There are a number of explorers that you can use for Archway: \ No newline at end of file diff --git a/docs/archway/useful-tools/other-tools.md b/docs/archway/useful-tools/other-tools.md new file mode 100644 index 00000000..c972a683 --- /dev/null +++ b/docs/archway/useful-tools/other-tools.md @@ -0,0 +1,14 @@ +--- +sidebar_position: 3 +description: Other-tools +--- + +# Other Tools + +> This page is a repository of valuable tools and resources offered by the Archway Community, including monitoring systems, dashboards, and versatile platforms. These resources are designed to enhance your capabilities and are backed by Archway Community's commitment to support your needs. + +:::info +The following page contains links to third-party content. Archway does not endorse or provide support for these contributions. +::: + +To contribute your own resource, simply click on **Edit this page** at the bottom, insert your resource using Markdown formatting, and then initiate a pull request for the submission to be reviewed. \ No newline at end of file diff --git a/docs/archway/useful-tools/telegram-bots.md b/docs/archway/useful-tools/telegram-bots.md new file mode 100644 index 00000000..5f4d0b67 --- /dev/null +++ b/docs/archway/useful-tools/telegram-bots.md @@ -0,0 +1,10 @@ +--- +sidebar_position: 2 +description: Telegram Bots +--- + +# Telegram Bots + +> Telegram bots are designed to monitor nodes, provide real-time alerts and health statistics. Bots deliver instant notifications on server downtimes, resource usage, or governance proposals, enabling administrators to act swiftly in response to any anomalies. + +To contribute your own resource, simply click on **Edit this** page at the bottom, insert your resource using Markdown formatting, and then initiate a pull request for the submission to be reviewed. \ No newline at end of file diff --git a/docs/babylon/_category_.json b/docs/babylon/_category_.json index 911da25d..08409f77 100644 --- a/docs/babylon/_category_.json +++ b/docs/babylon/_category_.json @@ -1,4 +1,4 @@ { "label": "Babylon", - "position": 16 + "position": 3 } \ No newline at end of file diff --git a/docs/babylon/endpoints.mdx b/docs/babylon/endpoints.mdx index 066501db..b6129e67 100644 --- a/docs/babylon/endpoints.mdx +++ b/docs/babylon/endpoints.mdx @@ -10,9 +10,9 @@ import TabItem from '@theme/TabItem'; > In the Cosmos SDK, the gRPC-gateway translates gRPC endpoints into RESTful ones, enabling users to interact via the REST API. This adaptation is essential for clients that don't natively support gRPC or HTTP2. -> The RPC endpoint enables users to interact with Band's nodes, querying the node's state and transmitting transactions within the Band Protocol. +> The RPC endpoint enables users to interact with Babylon's nodes, querying the node's state and transmitting transactions within the Babylon Network. -> The gRPC endpoint enables user interactions with a Band Node through the efficient gRPC framework. In the Cosmos SDK, this protocol is crucial for state queries and transaction broadcasts. +> The gRPC endpoint enables user interactions with a Babylon Node through the efficient gRPC framework. In the Cosmos SDK, this protocol is crucial for state queries and transaction broadcasts. diff --git a/docs/babylon/index.mdx b/docs/babylon/index.mdx index d5aa0b44..f6d21410 100644 --- a/docs/babylon/index.mdx +++ b/docs/babylon/index.mdx @@ -14,7 +14,7 @@ Babylon consists of two innovative security-sharing protocols between Bitcoin an ![babylon](./img/babylon.png) -[Website](https://babylonchain.io/) | [Blog](https://babylonchain.io/blog) | [GitHub](https://github.com/babylonchain) | [Twitter] (https://twitter.com/babylon_chain) | [Discord](https://discord.com/invite/babylonglobal) | [Docs](https://docs.babylonchain.io) +[Website](https://babylonchain.io/) | [Blog](https://babylonchain.io/blog) | [GitHub](https://github.com/babylonchain) | [Twitter](https://twitter.com/babylon_chain) | [Discord](https://discord.com/invite/babylonglobal) | [Docs](https://docs.babylonchain.io) ```mdx-code-block import DocCardList from '@theme/DocCardList'; diff --git a/docs/babylon/useful-tools/telegram-bots.md b/docs/babylon/useful-tools/telegram-bots.md index da8a79bb..50197a57 100644 --- a/docs/babylon/useful-tools/telegram-bots.md +++ b/docs/babylon/useful-tools/telegram-bots.md @@ -11,6 +11,6 @@ To contribute your own resource, simply click on **Edit this** page at the botto | Name | Description | Author | Date added/updated | | --- | --- | --- | --- | -| [Testnet Proposal Bot](https://t.me/kjnodes_testnet_proposal_bot) | A telegram bot to notify users of governance proposals when they're available for voting. | [kjnodes](https://github.com/kj89) | 2023-18-11 | -[L0vd](https://t.me/L0vdBot) | A telegram bot to notify notifications for Babylon blockchain events: aggregates BBN token info, comission, stake, etc. | [L0vd](https://t.me/L0vdBot) | 2023-10-11 | -| [Governance Bot](https://t.me/nodejumper_governance_bot) | A telegram bot to notify users of governance proposals when they're available for voting. | [NodeJumper](https://github.com/nodejumper-org) | 2023-09-14 | \ No newline at end of file +| [Testnet Proposal Bot](https://t.me/kjnodes_testnet_proposal_bot) | A telegram bot to notify users of governance proposals when they're available for voting. | [kjnodes](https://github.com/kj89) | 2023-08-22 | +[L0vd](https://t.me/L0vdBot) | A telegram bot to notify notifications for Babylon blockchain events: aggregates BBN token info, comission, stake, etc. | [L0vd](https://t.me/L0vdBot) | 2023-04-05 | +| [Governance Bot](https://t.me/nodejumper_governance_bot) | A telegram bot to notify users of governance proposals when they're available for voting. | [NodeJumper](https://github.com/nodejumper-org) | 2023-06-27 | \ No newline at end of file diff --git a/docs/band-protocol/_category_.json b/docs/band-protocol/_category_.json index d9958c1e..7a9e62a0 100644 --- a/docs/band-protocol/_category_.json +++ b/docs/band-protocol/_category_.json @@ -1,4 +1,4 @@ { "label": "Band Protocol", - "position": 2 + "position": 4 } diff --git a/docs/celestia/_category_.json b/docs/celestia/_category_.json index f3bc0c3f..969a73c0 100644 --- a/docs/celestia/_category_.json +++ b/docs/celestia/_category_.json @@ -1,4 +1,4 @@ { "label": "Celestia", - "position": 3 + "position": 5 } diff --git a/docs/celestia/endpoints.mdx b/docs/celestia/endpoints.mdx index 4a1e744d..555751b9 100644 --- a/docs/celestia/endpoints.mdx +++ b/docs/celestia/endpoints.mdx @@ -10,9 +10,9 @@ import TabItem from '@theme/TabItem'; > In the Cosmos SDK, the gRPC-gateway translates gRPC endpoints into RESTful ones, enabling users to interact via the REST API. This adaptation is essential for clients that don't natively support gRPC or HTTP2. -> The RPC endpoint enables users to interact with Band's nodes, querying the node's state and transmitting transactions within the Band Protocol. +> The RPC endpoint enables users to interact with Celestia's nodes, querying the node's state and transmitting transactions within the Celestia Network. -> The gRPC endpoint enables user interactions with a Band Node through the efficient gRPC framework. In the Cosmos SDK, this protocol is crucial for state queries and transaction broadcasts. +> The gRPC endpoint enables user interactions with a Celestia Node through the efficient gRPC framework. In the Cosmos SDK, this protocol is crucial for state queries and transaction broadcasts. diff --git a/docs/dymension/_category_.json b/docs/dymension/_category_.json index da7ef24d..315f4efb 100644 --- a/docs/dymension/_category_.json +++ b/docs/dymension/_category_.json @@ -1,4 +1,4 @@ { "label": "Dymension", - "position": 4 + "position": 6 } diff --git a/docs/dymension/endpoints.mdx b/docs/dymension/endpoints.mdx index 945837e7..1ea76845 100644 --- a/docs/dymension/endpoints.mdx +++ b/docs/dymension/endpoints.mdx @@ -10,7 +10,7 @@ import TabItem from '@theme/TabItem'; > In the Cosmos SDK, the gRPC-gateway translates gRPC endpoints into RESTful ones, enabling users to interact via the REST API. This adaptation is essential for clients that don't natively support gRPC or HTTP2. -> The RPC endpoint enables users to interact with Dymension's nodes, querying the node's state and transmitting transactions within the Dymension. +> The RPC endpoint enables users to interact with Dymension's nodes, querying the node's state and transmitting transactions within the Dymension Network. > The gRPC endpoint enables user interactions with a Dymension Node through the efficient gRPC framework. In the Cosmos SDK, this protocol is crucial for state queries and transaction broadcasts. diff --git a/docs/haqq-network/_category_.json b/docs/haqq-network/_category_.json index f3cb91b2..d5f53b59 100644 --- a/docs/haqq-network/_category_.json +++ b/docs/haqq-network/_category_.json @@ -1,4 +1,4 @@ { "label": "Haqq Network", - "position": 5 + "position": 7 } diff --git a/docs/lava-network/_category_.json b/docs/lava-network/_category_.json index 81f90ac1..ada98e29 100644 --- a/docs/lava-network/_category_.json +++ b/docs/lava-network/_category_.json @@ -1,4 +1,4 @@ { "label": "Lava Network", - "position": 6 + "position": 8 } diff --git a/docs/lava-network/endpoints.mdx b/docs/lava-network/endpoints.mdx index 826e58b8..6e2c4088 100644 --- a/docs/lava-network/endpoints.mdx +++ b/docs/lava-network/endpoints.mdx @@ -27,6 +27,11 @@ https://lava.api.t.anode.team https://api.lava-testnet-2.lava.aviaone.com ``` +#### F5 Nodes: +```bash +https://lava-api.f5nodes.com +``` + #### ITRocket: ```bash https://lava-testnet-api.itrocket.net:443 @@ -85,6 +90,11 @@ https://lava.rpc.t.anode.team https://rpc.lava-testnet-2.lava.aviaone.com ``` +#### F5 Nodes: +```bash +https://lava-rpc.f5nodes.com +``` + #### ITRocket: ```bash https://lava-testnet-rpc.itrocket.net:443 @@ -138,6 +148,11 @@ https://lava-testnet.rpc.stakevillage.net:443 grpc.lava-testnet-2.lava.aviaone.com:9096 ``` +#### F5 Nodes: +```bash +lava-grpc.f5nodes.com +``` + #### ITRocket: ```bash lava-testnet-grpc.itrocket.net:20090 diff --git a/docs/nibiru/_category_.json b/docs/nibiru/_category_.json index d4540c88..41ce79f4 100644 --- a/docs/nibiru/_category_.json +++ b/docs/nibiru/_category_.json @@ -1,5 +1,5 @@ { "label": "Nibiru", - "position": 7 + "position": 9 } diff --git a/docs/nibiru/endpoints.mdx b/docs/nibiru/endpoints.mdx index e2272a2c..d1871231 100644 --- a/docs/nibiru/endpoints.mdx +++ b/docs/nibiru/endpoints.mdx @@ -10,9 +10,9 @@ import TabItem from '@theme/TabItem'; > In the Cosmos SDK, the gRPC-gateway translates gRPC endpoints into RESTful ones, enabling users to interact via the REST API. This adaptation is essential for clients that don't natively support gRPC or HTTP2. -> The RPC endpoint enables users to interact with Band's nodes, querying the node's state and transmitting transactions within the Band Protocol. +> The RPC endpoint enables users to interact with Nibiru's nodes, querying the node's state and transmitting transactions within the Nibiru Network. -> The gRPC endpoint enables user interactions with a Band Node through the efficient gRPC framework. In the Cosmos SDK, this protocol is crucial for state queries and transaction broadcasts. +> The gRPC endpoint enables user interactions with a Nibiru Node through the efficient gRPC framework. In the Cosmos SDK, this protocol is crucial for state queries and transaction broadcasts. diff --git a/docs/sui/_category_.json b/docs/sui/_category_.json index 4527dc03..bff6a3ce 100644 --- a/docs/sui/_category_.json +++ b/docs/sui/_category_.json @@ -1,4 +1,4 @@ { "label": "Sui", - "position": 8 + "position": 10 } diff --git a/docs/zetachain/_category_.json b/docs/zetachain/_category_.json index 9479ef37..77d52a6a 100644 --- a/docs/zetachain/_category_.json +++ b/docs/zetachain/_category_.json @@ -1,4 +1,4 @@ { "label": "Zetachain", - "position": 9 + "position": 11 }