From e24a57525ec79a3fd3e73c418e5b11c8e6172a39 Mon Sep 17 00:00:00 2001 From: babybunn Date: Fri, 28 Feb 2025 15:56:15 +0700 Subject: [PATCH] fix: typos --- docs/core-concepts/accounts-and-wallets.md | 5 +---- docs/core-concepts/lite-client-protocol.md | 2 +- docs/data-tunnel/01-what-is-data-tunnel.md | 4 ++-- 3 files changed, 4 insertions(+), 7 deletions(-) diff --git a/docs/core-concepts/accounts-and-wallets.md b/docs/core-concepts/accounts-and-wallets.md index fd23d39..744e888 100644 --- a/docs/core-concepts/accounts-and-wallets.md +++ b/docs/core-concepts/accounts-and-wallets.md @@ -89,10 +89,7 @@ curl -X GET "https://laozi1.bandchain.org/api/cosmos/auth/v1beta1/accounts/band1 As mentioned earlier, building on the CosmosSDK allows us to enable our users to interact with BandChain using Cosmos native wallets. The most popular Cosmos and IBC-enabled wallets are supported on BandChain. These include: - -1. [Cosmostation](https://www.cosmostation.io) +1. [Cosmostation](https://www.cosmostation.io/products/cosmostation_extension) 2. [Ledger](https://www.ledger.com) 3. [Leap](https://www.leapwallet.io/ecosystem/chains/band-protocol) 4. [Keplr](https://www.keplr.app) -5. [Cosmostation](https://www.cosmostation.io/products/cosmostation_extension) - diff --git a/docs/core-concepts/lite-client-protocol.md b/docs/core-concepts/lite-client-protocol.md index bfa29dc..4716ad9 100644 --- a/docs/core-concepts/lite-client-protocol.md +++ b/docs/core-concepts/lite-client-protocol.md @@ -66,7 +66,7 @@ We can then use that `appHash` to finally compute the `blockHash` using the very ## Recovering Signer Addresses -After we have constructed a `blockHash`, we can move on to prove its validity by attempting to use it to recover the addresses of the validators who signed on this block using Ethereum’s [ecrecover](https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/utils/cryptography/ECDSA.sol#L16) opcode. To ensure that the addresses we extracted are valid, we verify that each address we extract is unique. +After we have constructed a `blockHash`, we can move on to prove its validity by attempting to use it to recover the addresses of the validators who signed on this block using Ethereum’s [ECDSA recover](https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/utils/cryptography/ECDSA.sol#L16) opcode. To ensure that the addresses we extracted are valid, we verify that each address we extract is unique. As we recover each signer, we also add each extracted validator’s voting power to a counting tally, which we will use in the next step. diff --git a/docs/data-tunnel/01-what-is-data-tunnel.md b/docs/data-tunnel/01-what-is-data-tunnel.md index 6cad458..7ab2e49 100644 --- a/docs/data-tunnel/01-what-is-data-tunnel.md +++ b/docs/data-tunnel/01-what-is-data-tunnel.md @@ -2,7 +2,7 @@ :::warning -We are excited to announce that the Band V3 is currently under development! +We are excited to announce that Band V3 is currently under development! During this period, you may encounter intermittent updates, changes, and limited availability as we work to enhance its features and performance. @@ -10,7 +10,7 @@ We appreciate your patience and understanding as we aim to deliver a robust and ::: -In BandChain v3, price data are constantly and automatically updated through the concurrent price stream module. These price data can be publci accessible and can be used off-chain without any charge. However, to utilize the price data on a different blockchain, the price data needs to be passed through **data tunnel** to ensure data integrity. +In BandChain v3, price data is constantly and automatically updated through the concurrent price stream module. This price data is publicly accessible and can be used off-chain without any charge. However, to utilize the price data on a different blockchain, the price data needs to be passed through a **data tunnel** to ensure data integrity. BandChain allows developers to create a tunnel specifying the pricing symbols (signals), the feeding interval, and the price deviation triggering condition. Once registered, BandChain continuously and automatically checks for data delivery conditions, which are met if any of the following occurs: