Boba Network
Introduction
Boba Network is an EVM-equivalent Layer-2 scaling solution and Hybrid Compute platform offering lightning fast transactions and fees up to 100x less than Layer-1. Our Hybrid Compute technology brings the power of Web2 on-chain for the first time, allowing smart contracts to call any external Web2 API to execute complex algorithms such as machine learning classifiers, pull in real-world or enterprise data in a single atomic transaction, or sync with the latest state of a gaming engine. Leveraging off-chain computing and real-world data, developers and creators can offer an enriched experience unlike anything else on the market today. We’re delivering a faster, cheaper, and smarter experience for blockchain’s next billion users.
Supported Layer-1 blockchains include:
Quick facts
Network | Mainnet ChainID | Testnet ChainID | Block Explorer |
---|---|---|---|
Boba Ethereum | 288 |
28 |
https://bobascan.com/ |
Boba BNB | 56288 |
9728 |
https://blockexplorer.bnb.boba.network/ |
Boba Avalanche | 43288 |
4328 |
https://blockexplorer.avax.boba.network/ |
Bobabeam | 1294 |
1297 |
https://blockexplorer.bobabeam.boba.network/ |
Supported endpoints
chain_id
and wallet address
, return current token balances along with their spot prices. This endpoint supports a variety of token standards like ERC20, ERC721 and ERC1155. As a special case, network native tokens like ETH on Ethereum are also returned even though it’s not a token contract.
chain_id
and wallet address
, return all transactions along with their decoded log events. This endpoint does a deep-crawl of the blockchain to retrieve all kinds of transactions that references the address
including indexed topics within the event logs.
Go to Covalent’s API Reference
Appendix
Boba token
The BOBA
token is the native token of the Boba L2 network. To transact with a Boba L2 network, the cost of every transaction is the sum of two values:
- The Boba L2 (execution) fee, and
- The L1 (security) fee (e.g. ETH, BNB, AVAX, GLMR)
The Covalent API response returns the total amount of gas offered and spent but does not break these values down into corresponding L1 and L2 fees nor their respective tokens. The fees_paid
value in the response is in the L1 token.