diff --git a/docs/babylon/_category_.json b/docs/babylon/_category_.json new file mode 100644 index 00000000..911da25d --- /dev/null +++ b/docs/babylon/_category_.json @@ -0,0 +1,4 @@ +{ + "label": "Babylon", + "position": 16 +} \ No newline at end of file diff --git a/docs/babylon/endpoints.mdx b/docs/babylon/endpoints.mdx new file mode 100644 index 00000000..066501db --- /dev/null +++ b/docs/babylon/endpoints.mdx @@ -0,0 +1,137 @@ +--- +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 Band's nodes, querying the node's state and transmitting transactions within the Band Protocol. + +> 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. + + + + +#### F5 Nodes: +```bash +https://babylon-api.f5nodes.com +``` + +#### kjnodes: +```bash +https://babylon-testnet.api.kjnodes.com +``` + +#### L0vd: +```bash +https://babylon-testnet.api.l0vd.com +``` + +#### Nodeist: +```bash +https://api-testnet-babylon.nodeist.net +``` + +#### [Noders]Team: +```bash +http://babylon.api.nodersteam.com:11317 +``` + +#### NodeX: +```bash +https://babylon-testnet.api.nodex.one +``` + +#### Polkachu: +```bash +https://babylon-testnet-api.polkachu.com +``` + +#### lesnik | UTSA: +```bash +https://t-babylon.api.utsa.tech +``` + + + + +#### F5 Nodes: +```bash +https://babylon-rpc.f5nodes.com +``` + +#### kjnodes: +```bash +https://babylon-testnet.rpc.kjnodes.com +``` + +#### L0vd: +```bash +https://babylon-testnet.rpc.l0vd.com +``` + +#### Nodeist: +```bash +https://rpc-testnet-babylon.nodeist.net +``` + +#### [Noders]Team: +```bash +http://babylon.rpc.nodersteam.com:16657 +``` + +#### NodeX: +```bash +https://babylon-testnet.nodex.one +``` + +#### Polkachu: +```bash +https://babylon-testnet-rpc.polkachu.com +``` + +#### lesnik | UTSA: +```bash +https://t-babylon.rpc.utsa.tech +``` + + + + +#### F5 Nodes: +```bash +babylon-grpc.f5nodes.com +``` + +#### kjnodes: +```bash +babylon-testnet.grpc.kjnodes.com:443 +``` + +#### Nodeist: +```bash +grpc-testnet-babylon.nodeist.net:443 +``` + +#### [Noders]Team: +```bash +babylon.grpc.nodersteam.com:16656 +``` + +#### NodeX: +```bash +babylon-testnet.grpc.nodex.one +``` + +#### Polkachu: +```bash +babylon-testnet-grpc.polkachu.com:20690 +``` + + + diff --git a/docs/babylon/img/babylon.png b/docs/babylon/img/babylon.png new file mode 100644 index 00000000..15758929 Binary files /dev/null and b/docs/babylon/img/babylon.png differ diff --git a/docs/babylon/index.mdx b/docs/babylon/index.mdx new file mode 100644 index 00000000..d5aa0b44 --- /dev/null +++ b/docs/babylon/index.mdx @@ -0,0 +1,23 @@ +# Babylon + +import MainpageMetrics from '@site/src/components/MainpageMetrics'; + + + +[Babylon](https://babylonchain.io/) – is a Layer 1 blockchain that provides secure Bitcoin timestamps to its transactions. + +Babylon project designs security protocols that scale Bitcoin to secure the decentralized world. To this end, Babylon utilizes the three primary facets of Bitcoin: Bitcoin the asset, Bitcoin the reliable timestamping server, and Bitcoin the blockchain that contains the most censorship-resistant blockspace in the world. + +Babylon consists of two innovative security-sharing protocols between Bitcoin and other PoS blockchains: +- Bitcoin timestamping: This protocol sends succinct and verifiable timestamps of PoS blockchains to Bitcoin; and +- Bitcoin staking: Using Bitcoin timestamping as a building block, this protocol allows Bitcoin holders to stake their Bitcoin to PoS blockchains. + +![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) + +```mdx-code-block +import DocCardList from '@theme/DocCardList'; + + +``` \ No newline at end of file diff --git a/docs/babylon/sync/_category_.json b/docs/babylon/sync/_category_.json new file mode 100644 index 00000000..84b2d96a --- /dev/null +++ b/docs/babylon/sync/_category_.json @@ -0,0 +1,4 @@ +{ + "label": "Sync", + "position": 2 +} \ No newline at end of file diff --git a/docs/babylon/sync/addrbook.mdx b/docs/babylon/sync/addrbook.mdx new file mode 100644 index 00000000..fb5a997e --- /dev/null +++ b/docs/babylon/sync/addrbook.mdx @@ -0,0 +1,28 @@ +--- +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/testnets-addrbook/babylon/addrbook.json', + 'https://snapshots.kjnodes.com/babylon-testnet/addrbook.json', + `https://ss.nodeist.net/t/babylon/addrbook.json`, + 'https://raw.githubusercontent.com/nodersteam/cosmos-adrbook/main/babylon/addrbook.json', + 'https://snap.nodex.one/babylon-testnet/addrbook.json', + 'https://snapshots.polkachu.com/testnet-addrbook/babylon/addrbook.json', + 'https://share101.utsa.tech/babylon/addrbook.json', +]; + +export let home = 'babylond'; + +export let binary = 'babylond'; + + \ No newline at end of file diff --git a/docs/babylon/sync/peers-seeds.mdx b/docs/babylon/sync/peers-seeds.mdx new file mode 100644 index 00000000..a55f3351 --- /dev/null +++ b/docs/babylon/sync/peers-seeds.mdx @@ -0,0 +1,20 @@ +--- +sidebar_position: 3 +description: Live Peers / Seeds +--- + +# Live Peers / Seeds + +> When you start a node, you often need to connect to the network. This requires you to connect to one or more peers to start downloading the blockchain and receiving new blocks and transactions. Seeding nodes or bootstrap nodes help in this initial connection process. + +:::info +Copy and run the commands below to add your peers into `config.toml`. +::: + +import LivePeers from '@site/src/components/LivePeers'; + +export let home = 'babylond'; + +export let binary = 'babylond'; + + \ No newline at end of file diff --git a/docs/babylon/sync/snapshot.md b/docs/babylon/sync/snapshot.md new file mode 100644 index 00000000..3e5accf6 --- /dev/null +++ b/docs/babylon/sync/snapshot.md @@ -0,0 +1,45 @@ +--- +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 babylond + +# make a backup +cp $HOME/.babylond/data/priv_validator_state.json $HOME/.babylond/priv_validator_state.json.backup + +# reset your node and download a snapshot +babylond tendermint unsafe-reset-all --home $HOME/.babylond --keep-addr-book +wget | lz4 -dc - | tar -xf - -C $HOME/.bbabylond + +# replace the priv_validator_state.json you have backed up +mv $HOME/.babylond/priv_validator_state.json.backup $HOME/.babylond/data/priv_validator_state.json + +sudo systemctl restart babylond && sudo journalctl -u babylond -f -o cat +``` + +A list of Snapshots you can use: + +#### kjnodes: +```bash +https://snapshots.kjnodes.com/babylon-testnet/snapshot_latest.tar.lz4 +``` + +#### Nodeist: +```bash +https://ss.nodeist.net/t/babylon/snapshot_latest.tar.lz4 +``` + +#### NodeX: +```bash +https://snap.nodex.one/babylon-testnet/babylon-latest.tar.lz4 +``` \ No newline at end of file diff --git a/docs/babylon/sync/state-sync.mdx b/docs/babylon/sync/state-sync.mdx new file mode 100644 index 00000000..7c809862 --- /dev/null +++ b/docs/babylon/sync/state-sync.mdx @@ -0,0 +1,29 @@ +--- +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://babylon-rpc.f5nodes.com`, + `https://babylon-testnet.rpc.kjnodes.com`, + `https://babylon-testnet.rpc.l0vd.com`, + `https://rpc-testnet-babylon.nodeist.net`, + `http://babylon.rpc.nodersteam.com:16657`, + `https://babylon-testnet.nodex.one`, + `https://babylon-testnet-rpc.polkachu.com`, + `https://t-babylon.rpc.utsa.tech`, +]; + +export let home = 'babylond'; + +export let binary = 'babylond'; + + diff --git a/docs/babylon/useful-tools/_category_.json b/docs/babylon/useful-tools/_category_.json new file mode 100644 index 00000000..e7b879e6 --- /dev/null +++ b/docs/babylon/useful-tools/_category_.json @@ -0,0 +1,4 @@ +{ + "label": "Useful Resources", + "position": 3 +} diff --git a/docs/babylon/useful-tools/explorers.md b/docs/babylon/useful-tools/explorers.md new file mode 100644 index 00000000..5413c7c1 --- /dev/null +++ b/docs/babylon/useful-tools/explorers.md @@ -0,0 +1,19 @@ +--- +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 Babylon: + +| Name | Layer | Network | URL | +| --- | --- | --- | --- | +| Babylon (official) | Cosmos | bbn-test-2 | https://babylonscan.io | +| kjnodes | Cosmos | bbn-test-2 | https://explorer.kjnodes.com/babylon-testnet | +| Lovd | Cosmos | bbn-test-2 | https://explorers.l0vd.com/babylon-testnet | +| Nodes.Guru | Cosmos | bbn-test-2 | https://babylon.explorers.guru | +| NodeX | Cosmos | bbn-test-2 | https://explorer.nodex.one/babylon | +| lesnik | Cosmos | bbn-test-2 | https://exp.utsa.tech/babylon-test | \ No newline at end of file diff --git a/docs/babylon/useful-tools/telegram-bots.md b/docs/babylon/useful-tools/telegram-bots.md new file mode 100644 index 00000000..da8a79bb --- /dev/null +++ b/docs/babylon/useful-tools/telegram-bots.md @@ -0,0 +1,16 @@ +--- +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. + +| 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