BFT Chain Clients
Inbound Observations
Inbound transactions on BFT chains (e.g. Cosmos-based) are observed by scanning finalized blocks via RPC/WebSocket APIs. A transaction is valid for observation if:
- It includes a
MsgSendto an Asgard vault address - It includes a valid memo matching THORChain memo structure
BFT chains do not support mempool observation. Only confirmed transactions can be processed.
See Inbound Transactions. For wallet developers, see Sending Transactions.
Confirmation Counting
BFT chains achieve deterministic finality, so transactions are treated as final after one block. No extended confirmation counting logic is applied.
See Finality & Confirmation Counting.
Gas Tracking
Gas is tracked per transaction based on actual gas usage and price reported on-chain. The fee is calculated as:
Fee = gas_used * gas_price
Reported to THORChain in native asset units.
See Gas Tracking.
Vault Address Format
BFT chains use Bech32-encoded addresses. The vault address is derived from the chain-specific prefix and public key.
Example:
sdk.AccAddress(pubKey.Address()).String() // Cosmos SDK
Reorg Handling
Reorgs are extremely rare on BFT chains. No special reorg detection or ErrataTx logic is required.
Other Considerations
- Only the base asset of the BFT chain is supported (e.g., ATOM for Cosmos Hub).
- Non-standard transaction types (e.g., smart contract calls) are not supported.
- Transactions must not contain multiple outputs or messages.