├── .github └── workflow │ └── typo-check.yml ├── .gitignore ├── LICENSE ├── README.md ├── _typos.toml ├── api-reference ├── jtw.mdx ├── node-rpc │ ├── aptos │ │ ├── accounts │ │ │ ├── get-account-module.mdx │ │ │ ├── get-account-modules.mdx │ │ │ ├── get-account-resource.mdx │ │ │ ├── get-account-resources.mdx │ │ │ └── get-account.mdx │ │ ├── aptos_openapi.yaml │ │ ├── blocks │ │ │ ├── get-blocks-by-height.mdx │ │ │ └── get-blocks-by-version.mdx │ │ ├── events │ │ │ ├── get-events-by-creation-number.mdx │ │ │ └── get-events-by-event-handle.mdx │ │ ├── general │ │ │ ├── check-basic-node-health.mdx │ │ │ ├── get-ledger-info.mdx │ │ │ └── show-openapi-explorer.mdx │ │ ├── tables │ │ │ ├── get-raw-table-item.mdx │ │ │ └── get-table-item.mdx │ │ ├── transactions │ │ │ ├── encode-submission.mdx │ │ │ ├── estimate-gas-price.mdx │ │ │ ├── get-account-transactions.mdx │ │ │ ├── get-transaction-by-hash.mdx │ │ │ ├── get-transaction-by-version.mdx │ │ │ ├── get-transactions.mdx │ │ │ ├── simulate-transaction.mdx │ │ │ ├── submit-batch-transactions.mdx │ │ │ └── submit-transaction.mdx │ │ └── view │ │ │ └── execute-view-function-of-a-module.mdx │ ├── evm │ │ ├── debug_traceBlockByNumber.json │ │ ├── debug_traceBlockByNumber.mdx │ │ ├── debug_traceTransaction.json │ │ ├── debug_traceTransaction.mdx │ │ ├── debug_traceblockbyhash.json │ │ ├── debug_traceblockbyhash.mdx │ │ ├── eth_blockNumber.json │ │ ├── eth_blockNumber.mdx │ │ ├── eth_call.json │ │ ├── eth_call.mdx │ │ ├── eth_chainId.json │ │ ├── eth_chainId.mdx │ │ ├── eth_estimateGas.json │ │ ├── eth_estimateGas.mdx │ │ ├── eth_gasPrice.json │ │ ├── eth_gasPrice.mdx │ │ ├── eth_getBalance.json │ │ ├── eth_getBalance.mdx │ │ ├── eth_getBlockByHash.json │ │ ├── eth_getBlockByHash.mdx │ │ ├── eth_getBlockByNumber.json │ │ ├── eth_getBlockByNumber.mdx │ │ ├── eth_getBlockTransactionCountByHash.json │ │ ├── eth_getBlockTransactionCountByHash.mdx │ │ ├── eth_getBlockTransactionCountByNumber.json │ │ ├── eth_getBlockTransactionCountByNumber.mdx │ │ ├── eth_getCode.json │ │ ├── eth_getCode.mdx │ │ ├── eth_getFilterChanges.json │ │ ├── eth_getFilterChanges.mdx │ │ ├── eth_getLogs.json │ │ ├── eth_getLogs.mdx │ │ ├── eth_getStorageAt.json │ │ ├── eth_getStorageAt.mdx │ │ ├── eth_getTransactionByBlockHashAndIndex.json │ │ ├── eth_getTransactionByBlockHashAndIndex.mdx │ │ ├── eth_getTransactionByBlockNumberAndIndex.json │ │ ├── eth_getTransactionByBlockNumberAndIndex.mdx │ │ ├── eth_getTransactionByHash.json │ │ ├── eth_getTransactionByHash.mdx │ │ ├── eth_getTransactionCount.json │ │ ├── eth_getTransactionCount.mdx │ │ ├── eth_getTransactionReceipt.json │ │ ├── eth_getTransactionReceipt.mdx │ │ ├── eth_getUncleByBlockHashAndIndex.json │ │ ├── eth_getUncleByBlockHashAndIndex.mdx │ │ ├── eth_getUncleByBlockNumberAndIndex.json │ │ ├── eth_getUncleByBlockNumberAndIndex.mdx │ │ ├── eth_getUncleCountByBlockHash.json │ │ ├── eth_getUncleCountByBlockHash.mdx │ │ ├── eth_getUncleCountByBlockNumber.json │ │ ├── eth_getUncleCountByBlockNumber.mdx │ │ ├── eth_newBlockFilter.json │ │ ├── eth_newBlockFilter.mdx │ │ ├── eth_newFilter.json │ │ ├── eth_newFilter.mdx │ │ ├── eth_newPendingTransactionFilter.json │ │ ├── eth_newPendingTransactionFilter.mdx │ │ ├── eth_protocolVersion.json │ │ ├── eth_protocolVersion.mdx │ │ ├── eth_sendRawTransaction.json │ │ ├── eth_sendRawTransaction.mdx │ │ ├── eth_syncing.json │ │ ├── eth_syncing.mdx │ │ ├── eth_uninstallFilter.json │ │ ├── eth_uninstallFilter.mdx │ │ ├── net_listening.json │ │ ├── net_listening.mdx │ │ ├── net_version.json │ │ ├── net_version.mdx │ │ ├── trace_block.json │ │ ├── trace_block.mdx │ │ ├── trace_call.json │ │ ├── trace_call.mdx │ │ ├── trace_filter.json │ │ ├── trace_filter.mdx │ │ ├── trace_replayBlockTransactions.json │ │ ├── trace_replayBlockTransactions.mdx │ │ ├── trace_replayTransaction.json │ │ ├── trace_replayTransaction.mdx │ │ ├── trace_transaction.json │ │ ├── trace_transaction.mdx │ │ ├── web3_clientVersion.json │ │ ├── web3_clientVersion.mdx │ │ ├── web3_sha3.json │ │ └── web3_sha3.mdx │ ├── sui │ │ └── overview.mdx │ └── ton │ │ ├── accounts │ │ ├── detect-address.mdx │ │ ├── get-address-balance.mdx │ │ ├── get-address-information.mdx │ │ ├── get-address.mdx │ │ ├── get-extended-address-information.mdx │ │ ├── get-token-data.mdx │ │ ├── get-transactions.mdx │ │ ├── get-wallet-information.mdx │ │ ├── pack-address.mdx │ │ └── unpack-address.mdx │ │ ├── blocks │ │ ├── get-block-header.mdx │ │ ├── get-block-transactions.mdx │ │ ├── get-consensus-block.mdx │ │ ├── get-masterchain-block-signatures.mdx │ │ ├── get-masterchain-info.mdx │ │ ├── get-shard-block-proof.mdx │ │ ├── get-shards.mdx │ │ └── lookup-block.mdx │ │ ├── transactions │ │ ├── get-try-locate-result-tx.mdx │ │ ├── get-try-locate-source-tx.mdx │ │ └── get-try-locate-tx.mdx │ │ └── v2_openapi.json ├── overview.mdx ├── sql-api │ ├── data-cloud-sql-query.mdx │ ├── execute-queries.mdx │ ├── get-query-results.mdx │ ├── get-query-status.mdx │ └── sql_api.yml ├── status-code.mdx ├── web3-api │ ├── balance │ │ ├── balance_api.json │ │ ├── nft-balances │ │ │ └── get-nfts-owned-by-address.mdx │ │ └── token-balances │ │ │ ├── get-erc20-token-balances.mdx │ │ │ └── get-native-token-balances.mdx │ ├── basic │ │ ├── basic_api.json │ │ ├── block │ │ │ ├── get-block-by-number.mdx │ │ │ └── get-latest-block-number.mdx │ │ ├── contract │ │ │ └── contract-call.mdx │ │ ├── labels │ │ │ └── get-address-labels.mdx │ │ └── transaction │ │ │ ├── get-transaction.mdx │ │ │ └── get-transactions-by-account.mdx │ ├── domain │ │ ├── domain_api.json │ │ ├── ens-domain-endpoints │ │ │ ├── get-ens-domains.mdx │ │ │ ├── resolve-ens-domain.mdx │ │ │ └── reverse-resolve-ens-domain.mdx │ │ └── overview.mdx │ ├── nft │ │ ├── nft-collections │ │ │ ├── get-nft-collection-items.mdx │ │ │ ├── get-nft-collection-metadata.mdx │ │ │ └── search-for-nft-collections-using-names-and-contract-addresses.mdx │ │ ├── nft-metadata │ │ │ ├── get-nft-metadata.mdx │ │ │ └── get-nft-rarity.mdx │ │ ├── nft-ownership │ │ │ ├── get-nft-owner-by-token.mdx │ │ │ ├── get-nft-owner-history-by-token.mdx │ │ │ └── get-nft-owners-by-collection.mdx │ │ ├── nft-transfers │ │ │ └── get-nft-transfers-by-collection.mdx │ │ ├── nft_api.json │ │ └── overview.mdx │ └── token │ │ ├── market-data │ │ ├── get-token-price-history.mdx │ │ └── get-token-price.mdx │ │ ├── token-holders │ │ ├── get-token-holders.mdx │ │ └── get-top-token-holders.mdx │ │ ├── token-metadata │ │ └── get-token-metadata.mdx │ │ ├── token-transfers │ │ └── get-token-transfers-by-contract.mdx │ │ └── token_api.json └── webhook-api │ ├── activate-webhook.mdx │ ├── create-webhook.mdx │ ├── deactivate-webhook.mdx │ ├── delete-webhook.mdx │ ├── get-all-webhooks.mdx │ ├── get-webhook.mdx │ ├── openapi.json │ └── update-webhook.mdx ├── catalog ├── Arbitrum │ ├── Abstracted.mdx │ ├── Decoded.mdx │ ├── Overview.mdx │ └── Raw.mdx ├── Avalanche │ ├── Abstracted.mdx │ ├── Decoded.mdx │ ├── Overview.mdx │ └── Raw.mdx ├── BSC │ ├── Abstracted.mdx │ ├── Decoded.mdx │ ├── Overview.mdx │ └── Raw.mdx ├── Base │ ├── Abstracted.mdx │ ├── Decoded.mdx │ ├── Overview.mdx │ └── Raw.mdx ├── Bitcoin │ └── Abstracted.mdx ├── Blast │ ├── Abstracted.mdx │ ├── Decoded.mdx │ ├── Overview.mdx │ └── Raw.mdx ├── Ethereum │ ├── Abstracted.mdx │ ├── Decoded.mdx │ ├── Overview.mdx │ └── Raw.mdx ├── Fantom │ ├── Overview.mdx │ └── Raw.mdx ├── Labels │ ├── Abstracted.mdx │ └── Overview.mdx ├── Merlin │ ├── Overview.mdx │ └── Raw.mdx ├── Optimism │ ├── Abstracted.mdx │ ├── Decoded.mdx │ ├── Overview.mdx │ └── Raw.mdx ├── OtherEvm │ ├── APEX_Testnet.mdx │ ├── AgentLayer_Testnet.mdx │ ├── Ancient8.mdx │ ├── Arbitrum_Blueberry.mdx │ ├── Arbitrum_Nova.mdx │ ├── Arbitrum_One.mdx │ ├── Arbitrum_Sepolia.mdx │ ├── Atleta_Olympia.mdx │ ├── Automata_Testnet.mdx │ ├── B2_Hub_Mainnet.mdx │ ├── B2_Mainnet.mdx │ ├── B2_Testnet.mdx │ ├── BEVM_Mainnet.mdx │ ├── BEVM_Testnet.mdx │ ├── BNB_Smart_Chain_Testnet.mdx │ ├── Bahamut.mdx │ ├── Beam.mdx │ ├── Berachain_Artio.mdx │ ├── Berachain_bArtio.mdx │ ├── Bifrost_Mainnet.mdx │ ├── Bifrost_Testnet.mdx │ ├── Bitlayer_Mainnet.mdx │ ├── Bitlayer_Testnet.mdx │ ├── BlackFort_Exchange_Network.mdx │ ├── BlackFort_Exchange_Network_Testnet.mdx │ ├── Blast.mdx │ ├── Blast_Sepolia_Testnet.mdx │ ├── Celo_Alfajores_Testnet.mdx │ ├── Chiliz_Chain_Mainnet.mdx │ ├── Crab_Network.mdx │ ├── Creditcoin_Testnet.mdx │ ├── Crypto_Emergency.mdx │ ├── Cyber_Mainnet.mdx │ ├── Cyber_Testnet.mdx │ ├── DOS_Chain.mdx │ ├── Darwinia_Koi_Testnet.mdx │ ├── Darwinia_Network.mdx │ ├── Dodao.mdx │ ├── Ethereum_Classic.mdx │ ├── Fhenix_Helium.mdx │ ├── Form_Testnet.mdx │ ├── Forma.mdx │ ├── Forma_Sketchpad.mdx │ ├── Fuse_Mainnet.mdx │ ├── Fuse_Sparknet.mdx │ ├── GEEK_Verse_Mainnet.mdx │ ├── GEEK_Verse_Testnet.mdx │ ├── GUNZ_Testnet.mdx │ ├── Gnosis.mdx │ ├── Gnosis_Chiado_Testnet.mdx │ ├── Gobbl_Testnet.mdx │ ├── Hemi_Sepolia.mdx │ ├── Hybrid_Testnet.mdx │ ├── Immutable_zkEVM.mdx │ ├── Immutable_zkEVM_Testnet.mdx │ ├── Kakarot_Sepolia.mdx │ ├── Karak_Sepolia.mdx │ ├── Kingdom_Chain.mdx │ ├── Klaytn_Testnet_Baobab.mdx │ ├── Kroma.mdx │ ├── Kroma_Sepolia.mdx │ ├── Kyoto.mdx │ ├── Kyoto_Testnet.mdx │ ├── LUKSO_Mainnet.mdx │ ├── LUKSO_Testnet.mdx │ ├── Lambda_Chain_Mainnet.mdx │ ├── Lambda_Chain_Testnet.mdx │ ├── LayerEdge_testnet.mdx │ ├── Linea_Sepolia.mdx │ ├── MAXI_Chain_Testnet.mdx │ ├── Mantle.mdx │ ├── Memo_Smart_Chain_Mainnet.mdx │ ├── Meter_Mainnet.mdx │ ├── Meter_Testnet.mdx │ ├── Mint_Mainnet.mdx │ ├── Mint_Sepolia_Testnet.mdx │ ├── Mint_Testnet.mdx │ ├── Mode_Testnet.mdx │ ├── Moonbeam.mdx │ ├── Numbers_Mainnet.mdx │ ├── OP_Celestia_Raspberry.mdx │ ├── OP_Mainnet.mdx │ ├── Opal_testnet_by_Unique.mdx │ ├── Open_Campus_Codex.mdx │ ├── Orderly_Sepolia_Testnet.mdx │ ├── Ozone_Chain_Mainnet.mdx │ ├── Ozone_Chain_Testnet.mdx │ ├── PLAYA3ULL_GAMES.mdx │ ├── Plume_Testnet.mdx │ ├── Polygon_zkEVM.mdx │ ├── Polygon_zkEVM_Cardona_Testnet.mdx │ ├── Pools_Mainnet.mdx │ ├── PulseChain.mdx │ ├── PulseChain_Testnet_v4.mdx │ ├── RSS3_VSL_Sepolia_Testnet.mdx │ ├── Reya_Network.mdx │ ├── Rollux_Testnet.mdx │ ├── Saakuru_Mainnet.mdx │ ├── Scroll.mdx │ ├── Scroll_Sepolia_Testnet.mdx │ ├── Shyft_Mainnet.mdx │ ├── Step_Network.mdx │ ├── Swan_Proxima_Testnet.mdx │ ├── Swan_Saturn_Testnet.mdx │ ├── Syndicate_Frame_Chain.mdx │ ├── TAPROOT_Mainnet.mdx │ ├── Taiko_Hekla_L2.mdx │ ├── Tanssi_Demo.mdx │ ├── UPB_CRESCDI_Testnet.mdx │ ├── Unique.mdx │ ├── Vana_Satori_Testnet.mdx │ ├── Vanar_Mainnet.mdx │ ├── VeChain.mdx │ ├── VeChain_Testnet.mdx │ ├── Vitruveo_Mainnet.mdx │ ├── Vitruveo_Testnet.mdx │ ├── WeaveVM_Testnet.mdx │ ├── XDC_Apothem_Network.mdx │ ├── XR_Sepolia.mdx │ ├── Xai_Mainnet.mdx │ ├── Xterio_Testnet.mdx │ ├── Zilliqa_EVM.mdx │ ├── Zilliqa_EVM_Devnet.mdx │ ├── Zilliqa_EVM_Testnet.mdx │ ├── Zircuit_Testnet.mdx │ ├── Zora.mdx │ ├── opBNB_Mainnet.mdx │ ├── opBNB_Testnet.mdx │ ├── re.al.mdx │ ├── zkCandy_Sepolia_Testnet.mdx │ └── zkSync_Mainnet.mdx ├── Polygon │ ├── Abstracted.mdx │ ├── Decoded.mdx │ ├── Overview.mdx │ └── Raw.mdx ├── Price │ ├── Abstracted.mdx │ └── Overview.mdx ├── Sui │ ├── Overview.mdx │ └── Raw.mdx ├── Ton │ ├── Abstracted.mdx │ ├── Decoded.mdx │ ├── Overview.mdx │ └── Raw.mdx ├── Tron │ ├── Overview.mdx │ └── Raw.mdx ├── overview.mdx └── zkSync │ ├── Abstracted.mdx │ ├── Decoded.mdx │ ├── Overview.mdx │ └── Raw.mdx ├── contributing ├── cips.mdx ├── governance.mdx ├── overview.mdx └── roadmap.mdx ├── core-concepts ├── architecture │ ├── co_processor_layer.mdx │ ├── consensus_layer.mdx │ ├── data_accessibility_layer.mdx │ ├── execution_layer.mdx │ └── overview.mdx ├── avs-design.mdx ├── data-processing-based-on-avs.mdx ├── dual-chain.mdx ├── dual-staking.mdx ├── glossary.mdx └── manuscript │ ├── QuickStart │ ├── advanced_options.mdx │ ├── create_manuscript.mdx │ ├── prerequisites.mdx │ └── run_manuscript.mdx │ ├── overview.mdx │ ├── quick_start.mdx │ └── zone.mdx ├── developers ├── explorers.mdx ├── faucet.mdx ├── getting_started.mdx ├── manuscripts.mdx ├── open_apis.mdx ├── smart_contracts.mdx ├── testnet.mdx ├── tools_&_sdks.mdx └── wallet_integration.mdx ├── development.mdx ├── essentials ├── code.mdx ├── images.mdx ├── markdown.mdx ├── navigation.mdx ├── reusable-snippets.mdx └── settings.mdx ├── favicon.png ├── images ├── aquamarine-roadmap.png ├── avs-design-01.png ├── avs-design-01.svg ├── avs-design-02.png ├── catalog │ ├── blocks.png │ ├── contract_decoded.png │ ├── contracts.png │ ├── decoded.jpg │ ├── decoded02.jpg │ ├── decoded_ton_query.png │ ├── docs-blobs.png │ └── ton-decoded-search.png ├── chainbase_litepaper.jpg ├── chainbase_litepaper_kr.jpg ├── checks-passed.png ├── co-processor-layer.png ├── consensus-layer-1.png ├── da-1.png ├── da-2.png ├── da-3.png ├── da-4.png ├── da-5.png ├── data-processing-based-on-avs.png ├── dual-chain-1.png ├── dual-staking-1.png ├── dual-staking-2.png ├── faq │ └── how_to_get_api_key.gif ├── hero-dark.svg ├── hero-light.svg ├── introducing_banner.jpeg ├── manuscript_01.png ├── manuscript_02.png ├── manuscripts │ ├── manuscript_datasets.png │ ├── manuscript_debug_01.png │ ├── manuscript_debug_02.png │ ├── manuscript_deploy.png │ ├── manuscript_github.png │ ├── manuscript_gui.png │ ├── manuscript_yaml.png │ └── zone.png ├── manuscripts_overview.png ├── overview.png ├── role.png ├── tokenomic.png └── zircon-roadmap.png ├── introduction.mdx ├── introduction ├── about.mdx ├── faqs.mdx ├── litepaper.mdx ├── networks │ ├── benefits.mdx │ ├── delegators.mdx │ ├── developers.mdx │ ├── operators.mdx │ ├── overview.mdx │ └── validators.mdx └── tokenomics.mdx ├── logo ├── dark.svg └── light.svg ├── mint.json ├── node ├── configuration.mdx ├── introduction.mdx ├── mainnet.mdx ├── operator.mdx ├── testnet.mdx └── validator.mdx ├── pdf ├── Chainbase_litepaper.pdf └── Chainbase_litepaper_KR.pdf ├── platform ├── apis │ ├── data-cloud-v1.mdx │ ├── data-cloud-v2.mdx │ ├── data-sync.mdx │ ├── predefined-apis.mdx │ ├── quickstart.mdx │ └── rpc-nodes.mdx ├── datasets │ ├── data-catalog.mdx │ ├── inscription-and-rune.mdx │ └── overview.mdx ├── faqs │ └── faq.mdx ├── features │ ├── api │ │ ├── chain-rpc.mdx │ │ ├── log-explorer.mdx │ │ ├── sql-api │ │ │ ├── datacloud-api-classic.mdx │ │ │ ├── datacloud-custom-api.mdx │ │ │ ├── datacloud-task-api.mdx │ │ │ └── overview.mdx │ │ ├── web3-api.mdx │ │ └── webhook-api.mdx │ ├── datacloud │ │ ├── overview.mdx │ │ └── write-efficient-queries.mdx │ ├── decoding-contracts.mdx │ └── sync │ │ ├── kafka.mdx │ │ ├── overview.mdx │ │ └── webhook.mdx ├── overview.mdx ├── pricing │ └── pricing.mdx ├── support.mdx ├── supported-networks │ └── supported-networks.mdx └── usecases │ ├── balance-api │ ├── get-native-token-balances.mdx │ └── get-nfts-owned-by-address.mdx │ ├── domain-api │ ├── get-domain-names-by-address.mdx │ ├── resolve-domain.mdx │ └── reverse-resolve-domain.mdx │ ├── nft-api │ ├── get-all-transfers-of-a-collection.mdx │ ├── get-nft-metadata.mdx │ ├── get-nft-owner-by-token.mdx │ └── get-nft-owners-by-collection.mdx │ └── token-api │ ├── get-erc20-tokens-by-address.mdx │ ├── get-erc20-transfers-by-contract.mdx │ ├── get-holders-of-a-token.mdx │ ├── get-token-metadata.mdx │ ├── get-token-price-history.mdx │ ├── get-token-price.mdx │ └── get-top-token-holders.mdx ├── quickstart.mdx ├── snippets └── snippet-intro.mdx ├── style.css └── theia ├── Developers ├── Glossary │ ├── D2ORA.mdx │ └── G2D.mdx └── Open-APIs.mdx ├── Resources ├── FAQs.mdx ├── Roadmap.mdx └── Whitepaper.mdx ├── TheiaChat ├── create-task-models.mdx ├── overview.mdx └── task-models.mdx └── World_model ├── features.mdx ├── theia.mdx └── welcome.mdx /.github/workflow/typo-check.yml: -------------------------------------------------------------------------------- 1 | name: Typo Check 2 | 3 | on: [pull_request] 4 | 5 | jobs: 6 | check-for-typos: 7 | runs-on: 8 | steps: 9 | - name: Checkout the repository 10 | uses: actions/checkout@v4 11 | 12 | - name: Check for typos 13 | uses: crate-ci/typos@master 14 | with: 15 | config: ${{github.workspace}}/_typos.toml 16 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | .DS_Store 2 | .idea -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Chainbase Documentation 2 | 3 | ## Overview 4 | 5 | Welcome to Chainbase Documentation. This documentation provides information about Chainbase Data Network, Chainbase Data Platform, and Crypto World Model. 6 | 7 | * Chainbase Data Network: The world's largest omnichain data network designed to integrate all blockchain data into a unified ecosystem, providing an open and transparent data interoperability layer for the AI era. 8 | * Chainbase Data Platform: An all-in-one data infrastructure for Web3 that allows you to index, transform, and utilize large-scale on-chain data. 9 | * Crypto World Model: A comprehensive data model that provides a unified view of the entire crypto world, enabling developers to build powerful applications on top of it. 10 | 11 | ## Contributing 12 | 13 | We welcome contributions to the Chainbase documentation. If you find any issues or have suggestions for improvements, please create a pull request or open an issue. 14 | 15 | ### Running the documentation locally 16 | 17 | Install the [Mintlify CLI](https://www.npmjs.com/package/mintlify) to preview the documentation changes locally. To install, use the following command 18 | 19 | ```base 20 | npm i -g mintlify 21 | ``` 22 | 23 | Run the following command at the root of your documentation (where mint.json is) 24 | 25 | ```bash 26 | mintlify dev 27 | ``` 28 | 29 | ### Troubleshooting 30 | 31 | - Mintlify dev isn't running - Run `mintlify install` it'll re-install dependencies. 32 | - Page loads as a 404 - Make sure you are running in a folder with `mint.json` 33 | -------------------------------------------------------------------------------- /_typos.toml: -------------------------------------------------------------------------------- 1 | [default.extend-words] 2 | # Don't correct 3 | hsa = "hsa" 4 | cips = "cips" 5 | BA = "BA" 6 | Ded = "Ded" 7 | Yto = "Yto" 8 | 9 | 10 | [files] 11 | extend-exclude = ["images/**"] -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/accounts/get-account-module.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /accounts/{address}/module/{module_name} 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/accounts/get-account-modules.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /accounts/{address}/modules 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/accounts/get-account-resource.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /accounts/{address}/resource/{resource_type} 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/accounts/get-account-resources.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /accounts/{address}/resources 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/accounts/get-account.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /accounts/{address} 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/blocks/get-blocks-by-height.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /blocks/by_height/{block_height} 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/blocks/get-blocks-by-version.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /blocks/by_version/{version} 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/events/get-events-by-creation-number.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /accounts/{address}/events/{creation_number} 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/events/get-events-by-event-handle.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /accounts/{address}/events/{event_handle}/{field_name} 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/general/check-basic-node-health.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /-/healthy 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/general/get-ledger-info.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get / 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/general/show-openapi-explorer.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /spec 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/tables/get-raw-table-item.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: post /tables/{table_handle}/raw_item 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/tables/get-table-item.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: post /tables/{table_handle}/item 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/transactions/encode-submission.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: post /transactions/encode_submission 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/transactions/estimate-gas-price.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /estimate_gas_price 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/transactions/get-account-transactions.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /accounts/{address}/transactions 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/transactions/get-transaction-by-hash.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /transactions/by_hash/{txn_hash} 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/transactions/get-transaction-by-version.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /transactions/by_version/{txn_version} 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/transactions/get-transactions.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /transactions 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/transactions/simulate-transaction.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: post /transactions/simulate 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/transactions/submit-batch-transactions.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: post /transactions/batch 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/transactions/submit-transaction.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: post /transactions 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/aptos/view/execute-view-function-of-a-module.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: post /view 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/debug_traceBlockByNumber.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "debug_traceBlockByNumber post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/debug_traceTransaction.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "debug_traceTransaction post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/debug_traceblockbyhash.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "debug_traceblockbyhash post /{api-key}" 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_blockNumber.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_blockNumber post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_call.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_call post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_chainId.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_chainId post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_estimateGas.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_estimateGas post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_gasPrice.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_gasPrice post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getBalance.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getBalance post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getBlockByHash.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getBlockByHash post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getBlockByNumber.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getBlockByNumber post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getBlockTransactionCountByHash.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getBlockTransactionCountByHash post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getBlockTransactionCountByNumber.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getBlockTransactionCountByNumber post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getCode.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getCode post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getFilterChanges.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getFilterChanges post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getLogs.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getLogs post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getStorageAt.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getStorageAt post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getTransactionByBlockHashAndIndex.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getTransactionByBlockHashAndIndex post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getTransactionByBlockNumberAndIndex.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getTransactionByBlockNumberAndIndex post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getTransactionByHash.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getTransactionByHash post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getTransactionCount.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getTransactionCount post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getTransactionReceipt.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getTransactionReceipt post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getUncleByBlockHashAndIndex.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getUncleByBlockHashAndIndex post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getUncleByBlockNumberAndIndex.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getUncleByBlockNumberAndIndex post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getUncleCountByBlockHash.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getUncleCountByBlockHash post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_getUncleCountByBlockNumber.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_getUncleCountByBlockNumber post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_newBlockFilter.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_newBlockFilter post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_newFilter.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_newFilter post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_newPendingTransactionFilter.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_newPendingTransactionFilter post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_protocolVersion.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_protocolVersion post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_sendRawTransaction.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_sendRawTransaction post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_syncing.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_syncing post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/eth_uninstallFilter.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "eth_uninstallFilter post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/net_listening.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "net_listening post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/net_version.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "net_version post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/trace_block.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "trace_block post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/trace_call.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "trace_call post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/trace_filter.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "trace_filter post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/trace_replayBlockTransactions.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "trace_replayBlockTransactions post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/trace_replayTransaction.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "trace_replayTransaction post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/trace_transaction.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "trace_transaction post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/web3_clientVersion.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "web3_clientVersion post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/evm/web3_sha3.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: "web3_sha3 post /{api-key}" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/node-rpc/sui/overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Sui RPC API" 3 | --- 4 | 5 | Please refer to https://docs.sui.io/sui-api-ref. 6 | 7 | We will soon provide more detailed and convenient integration documents for testing. 8 | -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/accounts/detect-address.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /detectAddress 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/accounts/get-address-balance.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /getAddressBalance 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/accounts/get-address-information.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /getAddressInformation 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/accounts/get-address.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /getAddressState 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/accounts/get-extended-address-information.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /getExtendedAddressInformation 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/accounts/get-token-data.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /getTokenData 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/accounts/get-transactions.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /getTransactions 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/accounts/get-wallet-information.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /getWalletInformation 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/accounts/pack-address.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /packAddress 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/accounts/unpack-address.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /unpackAddress 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/blocks/get-block-header.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /getBlockHeader 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/blocks/get-block-transactions.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /getBlockTransactions 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/blocks/get-consensus-block.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /getConsensusBlock 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/blocks/get-masterchain-block-signatures.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /getMasterchainBlockSignatures 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/blocks/get-masterchain-info.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /getMasterchainInfo 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/blocks/get-shard-block-proof.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /getShardBlockProof 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/blocks/get-shards.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /shards 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/blocks/lookup-block.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /lookupBlock 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/transactions/get-try-locate-result-tx.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /tryLocateResultTx 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/transactions/get-try-locate-source-tx.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /tryLocateSourceTx 3 | --- -------------------------------------------------------------------------------- /api-reference/node-rpc/ton/transactions/get-try-locate-tx.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /tryLocateTx 3 | --- -------------------------------------------------------------------------------- /api-reference/sql-api/data-cloud-sql-query.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Data Cloud SQL Query (Classic)" 3 | openapi: "post /dw/query" 4 | --- 5 | 6 | ## Example 7 | 8 | Query the hashes of the last 3,000 blocks in Ethereum and the number of transactions in each block: 9 | 10 | ```bash 11 | curl -X "POST" "https://api.chainbase.online/v1/dw/query" \ 12 | -H 'X-API-KEY: YOUR-API-KEY ' \ 13 | -H 'Content-Type: application/json; charset=utf-8' \ 14 | -d $'{ 15 | "query": "select number, transactions_count from ethereum.blocks order by number desc limit 3000;" 16 | }' 17 | ``` 18 | 19 | If there are more than 1000 rows, you need to paginate through the`task_id` and `page` to get all the results: 20 | 21 | ```bash 22 | curl -X "POST" "https://api.chainbase.online/v1/dw/query" \ 23 | -H 'X-API-KEY: YOUR-API-KEY ' \ 24 | -H 'Content-Type: application/json; charset=utf-8' \ 25 | -d $'{ 26 | "task_id": "xxxxxxxxxxxxxxxxxxxxx", 27 | "page": 2 28 | }' 29 | ``` 30 | 31 | 32 | 🚧 Note 33 | 34 | 1. When `quey_id` is passed in, the content of query will be ignored 35 | 2. The executed request generates a `task_id`, which is valid for 1 hour 36 | 3. A maximum of 100,000 pieces of data are allowed to be obtained from the request, and 1,000 results are paginated per page 37 | 38 | -------------------------------------------------------------------------------- /api-reference/sql-api/execute-queries.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Execute Queries (Alpha)" 3 | description: "Limit of 100,000 results" 4 | openapi: "post /query/execute" 5 | --- 6 | -------------------------------------------------------------------------------- /api-reference/sql-api/get-query-results.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Get Query Results (Alpha)" 3 | openapi: "get /execution/{execution_id}/results" 4 | --- 5 | -------------------------------------------------------------------------------- /api-reference/sql-api/get-query-status.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Get Query Status (Alpha)" 3 | openapi: "get /execution/{execution_id}/status" 4 | --- 5 | -------------------------------------------------------------------------------- /api-reference/web3-api/balance/nft-balances/get-nfts-owned-by-address.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/account/nfts 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/balance/token-balances/get-erc20-token-balances.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/account/tokens 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/balance/token-balances/get-native-token-balances.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/account/balance 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/basic/block/get-block-by-number.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/block/detail 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/basic/block/get-latest-block-number.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/block/number/latest 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/basic/contract/contract-call.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: post /v1/contract/call 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/basic/labels/get-address-labels.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/address/labels 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/basic/transaction/get-transaction.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/tx/detail 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/basic/transaction/get-transactions-by-account.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/account/txs 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/domain/ens-domain-endpoints/get-ens-domains.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/account/ens 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/domain/ens-domain-endpoints/resolve-ens-domain.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/ens/records 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/domain/ens-domain-endpoints/reverse-resolve-ens-domain.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/ens/reverse 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/domain/overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Overview" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/web3-api/nft/nft-collections/get-nft-collection-items.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/nft/collection/items 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/nft/nft-collections/get-nft-collection-metadata.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/nft/collection 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/nft/nft-collections/search-for-nft-collections-using-names-and-contract-addresses.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/nft/search 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/nft/nft-metadata/get-nft-metadata.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/nft/metadata 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/nft/nft-metadata/get-nft-rarity.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/nft/rarity 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/nft/nft-ownership/get-nft-owner-by-token.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/nft/owner 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/nft/nft-ownership/get-nft-owner-history-by-token.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/nft/owner/history 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/nft/nft-ownership/get-nft-owners-by-collection.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/nft/owners 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/nft/nft-transfers/get-nft-transfers-by-collection.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/nft/transfers 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/nft/overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Overview" 3 | --- 4 | -------------------------------------------------------------------------------- /api-reference/web3-api/token/market-data/get-token-price-history.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/token/price/history 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/token/market-data/get-token-price.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/token/price 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/token/token-holders/get-token-holders.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/token/holders 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/token/token-holders/get-top-token-holders.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/token/top-holders 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/token/token-metadata/get-token-metadata.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/token/metadata 3 | --- -------------------------------------------------------------------------------- /api-reference/web3-api/token/token-transfers/get-token-transfers-by-contract.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /v1/token/transfers 3 | --- -------------------------------------------------------------------------------- /api-reference/webhook-api/activate-webhook.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: post /webhooks/{webhook_id}/activate 3 | --- -------------------------------------------------------------------------------- /api-reference/webhook-api/create-webhook.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: post /webhooks 3 | --- -------------------------------------------------------------------------------- /api-reference/webhook-api/deactivate-webhook.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: post /webhooks/{webhook_id}/deactivate 3 | --- -------------------------------------------------------------------------------- /api-reference/webhook-api/delete-webhook.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: delete /webhooks/{webhook_id} 3 | --- -------------------------------------------------------------------------------- /api-reference/webhook-api/get-all-webhooks.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /webhooks 3 | --- -------------------------------------------------------------------------------- /api-reference/webhook-api/get-webhook.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: get /webhooks/{webhook_id} 3 | --- -------------------------------------------------------------------------------- /api-reference/webhook-api/update-webhook.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | openapi: patch /webhooks/{webhook_id} 3 | --- -------------------------------------------------------------------------------- /catalog/Arbitrum/Abstracted.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Abstracted' 3 | --- 4 | 5 | ## 1.arbitrum.token_metas 6 | ### Table Description 7 | Token metadata in the context of blockchain and cryptocurrencies typically refers to the set of data that describes the characteristics and details of a particular token. This metadata can include information such as the token's name, symbol, total supply, decimal precision, and other details relevant to its function and identity on the blockchain. It's essentially the descriptive data that gives context and identity to a token, distinguishing it from other tokens within the same blockchain ecosystem. Metadata is crucial for understanding the nature and purpose of a token, especially in applications like wallets, exchanges, and decentralized applications (dApps) where users interact with various types of tokens. 8 | ### Column Descriptions 9 | 10 |
11 | 18 |
19 | 20 | ### Table Sample 21 | 22 |
23 | 30 |
31 | -------------------------------------------------------------------------------- /catalog/Arbitrum/Decoded.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Decoded' 3 | --- 4 | ## 1. arbitrum.trace_calls_decoded 5 | ### Table Description 6 | The arbitrum.trace_calls_decoded table provides a comprehensive and human-readable view of the internal transactions and function calls within the Ethereum blockchain. By decoding trace calls, this table enables easier understanding and analysis of the complex interactions and operations that occur during transaction execution. 7 | ### Column Descriptions 8 | 9 |
10 | 17 |
18 | 19 | ### Table Sample 20 | 21 |
22 | 29 |
30 | ## 2. arbitrum.transaction_logs_decoded 31 | ### Table Description 32 | The arbitrum.transaction_logs_decoded table contains decoded logs from Ethereum transactions, providing a human-readable view of the events emitted by smart contracts. Logs are essential for understanding the actions and state changes that occur during the execution of smart contracts. By decoding these logs, the table offers a more accessible and detailed perspective on blockchain activities. 33 | ### Column Descriptions 34 | 35 |
36 | 43 |
44 | 45 | ### Table Sample 46 | 47 |
48 | 55 |
-------------------------------------------------------------------------------- /catalog/Arbitrum/Overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: '☆ Overview' 3 | --- 4 | 5 | Arbitrum is a Layer 2 scaling solution for Ethereum, designed to improve the performance and reduce the costs associated with decentralized applications (DApps) on the Ethereum network. Launched by Offchain Labs, Arbitrum enhances Ethereum’s scalability while maintaining its security and decentralization. By using rollup technology, Arbitrum enables faster and cheaper transactions, making it an attractive platform for developers and users alike. 6 | ### The Major Features of the Arbitrum Blockchain 7 | 8 | 1. **Scalability**: Arbitrum significantly increases the scalability of Ethereum by aggregating multiple transactions into a single batch, which is then processed off-chain before being committed to the Ethereum main chain. This rollup technique reduces the load on the Ethereum network, allowing for thousands of transactions per second while maintaining low latency. 9 | 10 | 2. **Low Fees**: By processing transactions off-chain and only recording the final state on the Ethereum main chain, Arbitrum drastically reduces transaction fees. This cost efficiency makes it more affordable for users and developers to interact with decentralized applications, fostering greater adoption and usage. 11 | 12 | 3. **EVM Compatibility**: Arbitrum is fully compatible with the Ethereum Virtual Machine (EVM), enabling developers to deploy their existing Ethereum-based smart contracts and DApps on Arbitrum with minimal modifications. This compatibility ensures a seamless transition for developers and allows them to leverage Ethereum’s extensive ecosystem of tools and libraries. 13 | -------------------------------------------------------------------------------- /catalog/Avalanche/Abstracted.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Abstracted' 3 | --- 4 | 5 | ## 1.arbitrum.token_metas 6 | ### Table Description 7 | Token metadata in the context of blockchain and cryptocurrencies typically refers to the set of data that describes the characteristics and details of a particular token. This metadata can include information such as the token's name, symbol, total supply, decimal precision, and other details relevant to its function and identity on the blockchain. It's essentially the descriptive data that gives context and identity to a token, distinguishing it from other tokens within the same blockchain ecosystem. Metadata is crucial for understanding the nature and purpose of a token, especially in applications like wallets, exchanges, and decentralized applications (dApps) where users interact with various types of tokens. 8 | ### Column Descriptions 9 | 10 |
11 | 18 |
19 | 20 | ### Table Sample 21 | 22 |
23 | 30 |
31 | -------------------------------------------------------------------------------- /catalog/Avalanche/Decoded.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Decoded' 3 | --- 4 | ## 1. avalanche.trace_calls_decoded 5 | ### Table Description 6 | The avalanche.trace_calls_decoded table provides a comprehensive and human-readable view of the internal transactions and function calls within the Ethereum blockchain. By decoding trace calls, this table enables easier understanding and analysis of the complex interactions and operations that occur during transaction execution. 7 | ### Column Descriptions 8 | 9 |
10 | 17 |
18 | 19 | ### Table Sample 20 | 21 |
22 | 29 |
30 | ## 2. avalanche.transaction_logs_decoded 31 | ### Table Description 32 | The avalanche.transaction_logs_decoded table contains decoded logs from Ethereum transactions, providing a human-readable view of the events emitted by smart contracts. Logs are essential for understanding the actions and state changes that occur during the execution of smart contracts. By decoding these logs, the table offers a more accessible and detailed perspective on blockchain activities. 33 | ### Column Descriptions 34 | 35 |
36 | 43 |
44 | 45 | ### Table Sample 46 | 47 |
48 | 55 |
-------------------------------------------------------------------------------- /catalog/Avalanche/Overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: '☆ Overview' 3 | --- 4 | 5 | Avalanche is a decentralized platform designed to support the creation and deployment of highly scalable and customizable blockchain networks and decentralized applications (DApps). Launched in 2020 by Ava Labs, Avalanche aims to provide high throughput, low latency, and low transaction fees, addressing some of the key limitations faced by earlier blockchain networks. 6 | ### The Major Features of the Avalanche Blockchain 7 | 8 | 1. **High Throughput and Low Latency**: Avalanche is designed to handle thousands of transactions per second with sub-second finality. This high throughput and low latency make it suitable for a wide range of applications, from financial services to gaming and beyond. Avalanche's consensus protocol, Avalanche Consensus, is a novel approach that ensures quick and secure agreement among nodes. 9 | 10 | 2. **Customizable Blockchains**: Avalanche allows developers to create custom blockchain networks, known as subnets, tailored to specific applications and use cases. These subnets can have their own rulesets, virtual machines, and economic models, providing flexibility and customization that cater to the needs of different projects. This modularity enables the creation of highly specialized blockchain networks. 11 | 12 | 3. **Interoperability**: Avalanche is designed to be highly interoperable, allowing assets and data to move seamlessly between different subnets and external blockchain networks. The Avalanche-X framework provides tools and protocols to facilitate cross-chain communication, ensuring that assets can be transferred securely and efficiently across various blockchain ecosystems. -------------------------------------------------------------------------------- /catalog/BSC/Abstracted.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Abstracted' 3 | --- 4 | ## 14. bsc.token_metas 5 | ### Table Description 6 | Token metadata in the context of blockchain and cryptocurrencies typically refers to the set of data that describes the characteristics and details of a particular token. This metadata can include information such as the token's name, symbol, total supply, decimal precision, and other details relevant to its function and identity on the blockchain. It's essentially the descriptive data that gives context and identity to a token, distinguishing it from other tokens within the same blockchain ecosystem. Metadata is crucial for understanding the nature and purpose of a token, especially in applications like wallets, exchanges, and decentralized applications (dApps) where users interact with various types of tokens. 7 | ### Column Descriptions 8 | 9 |
10 | 17 |
18 | 19 | ### Table Sample 20 | 21 |
22 | 29 |
30 | -------------------------------------------------------------------------------- /catalog/BSC/Decoded.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Decoded' 3 | --- 4 | ## 1. bsc.trace_calls_decoded 5 | 6 | ### Table Description 7 | The bsc.trace_calls_decoded table provides a comprehensive and human-readable view of the internal transactions and function calls within the Ethereum blockchain. By decoding trace calls, this table enables easier understanding and analysis of the complex interactions and operations that occur during transaction execution. 8 | ### Column Descriptions 9 | 10 |
11 | 18 |
19 | 20 | ### Table Sample 21 | 22 |
23 | 30 |
31 | 32 | ## 2. bsc.transaction_logs_decoded 33 | ### Table Description 34 | The bsc.transaction_logs_decoded table contains decoded logs from Ethereum transactions, providing a human-readable view of the events emitted by smart contracts. Logs are essential for understanding the actions and state changes that occur during the execution of smart contracts. By decoding these logs, the table offers a more accessible and detailed perspective on blockchain activities. 35 | ### Column Descriptions 36 | 37 |
38 | 45 |
46 | 47 | ### Table Sample 48 | 49 |
50 | 57 |
-------------------------------------------------------------------------------- /catalog/Base/Abstracted.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Abstracted' 3 | --- 4 | 5 | ## 1.base.token_metas 6 | ### Table Description 7 | Token metadata in the context of blockchain and cryptocurrencies typically refers to the set of data that describes the characteristics and details of a particular token. This metadata can include information such as the token's name, symbol, total supply, decimal precision, and other details relevant to its function and identity on the blockchain. It's essentially the descriptive data that gives context and identity to a token, distinguishing it from other tokens within the same blockchain ecosystem. Metadata is crucial for understanding the nature and purpose of a token, especially in applications like wallets, exchanges, and decentralized applications (dApps) where users interact with various types of tokens. 8 | ### Column Descriptions 9 | 10 |
11 | 18 |
19 | 20 | ### Table Sample 21 | 22 |
23 | 30 |
31 | -------------------------------------------------------------------------------- /catalog/Base/Decoded.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Decoded' 3 | --- 4 | 5 | ## 1. base.trace_calls_decoded 6 | ### Table Description 7 | The base.trace_calls_decoded table provides a comprehensive and human-readable view of the internal transactions and function calls within the Ethereum blockchain. By decoding trace calls, this table enables easier understanding and analysis of the complex interactions and operations that occur during transaction execution. 8 | ### Column Descriptions 9 | 10 |
11 | 18 |
19 | 20 | ### Table Sample 21 | 22 |
23 | 30 |
31 | ## 2. base.transaction_logs_decoded 32 | ### Table Description 33 | The base.transaction_logs_decoded table contains decoded logs from Ethereum transactions, providing a human-readable view of the events emitted by smart contracts. Logs are essential for understanding the actions and state changes that occur during the execution of smart contracts. By decoding these logs, the table offers a more accessible and detailed perspective on blockchain activities. 34 | ### Column Descriptions 35 | 36 |
37 | 44 |
45 | 46 | ### Table Sample 47 | 48 |
49 | 56 |
-------------------------------------------------------------------------------- /catalog/Base/Overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: '☆ Overview' 3 | --- 4 | 5 | Base is a Layer 2 scaling solution built on top of the Ethereum blockchain, designed to enhance scalability, reduce transaction costs, and provide a robust environment for decentralized applications (DApps). Developed to address the limitations of Ethereum's main chain, Base utilizes advanced rollup technology to offer fast, secure, and cost-effective transactions while maintaining the security and decentralization of the Ethereum network. 6 | ### The Major Features of the Arbitrum Blockchain 7 | 8 | 1. **Scalability**: Base significantly increases Ethereum's scalability by aggregating multiple transactions into a single batch processed off-chain, which is then committed to the Ethereum main chain. This rollup technique allows Base to handle thousands of transactions per second, reducing congestion and improving network performance. 9 | 10 | 2. **Low Fees**: By processing transactions off-chain and recording only the final state on the Ethereum main chain, Base substantially reduces transaction fees. This cost efficiency makes blockchain interactions more affordable for users and developers, encouraging broader adoption and usage of decentralized applications. 11 | 12 | 3. **EVM Compatibility**: Base is fully compatible with the Ethereum Virtual Machine (EVM), enabling developers to deploy their existing Ethereum-based smart contracts and DApps on Base with minimal modifications. This compatibility ensures a seamless transition for developers and allows them to leverage Ethereum’s extensive ecosystem of tools and libraries. 13 | -------------------------------------------------------------------------------- /catalog/Blast/Overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: '☆ Overview' 3 | --- 4 | 5 | Blast is a decentralized blockchain platform designed to offer high scalability, security, and low transaction costs, making it an ideal environment for developing and deploying decentralized applications (DApps). Leveraging advanced consensus mechanisms and innovative architecture, Blast aims to overcome the limitations of traditional blockchain networks while providing a seamless and efficient user experience. 6 | 7 | ### The Major Features of the Blast Blockchain 8 | 9 | 1. **High Scalability**: Blast is built to handle a large volume of transactions with high throughput, enabling it to process thousands of transactions per second. This scalability ensures that the network can support a growing number of users and applications without experiencing congestion or delays. 10 | 11 | 2. **Low Fees**: One of Blast's key advantages is its low transaction fees. By optimizing its consensus protocol and network architecture, Blast minimizes the cost of transactions, making it more accessible for users and developers. This cost efficiency encourages broader adoption and usage of decentralized applications on the Blast network. 12 | 13 | 3. **Interoperability**: Blast supports interoperability with other blockchain networks, allowing for seamless asset transfers and data sharing across different chains. This cross-chain compatibility enhances the functionality of the Blast ecosystem, providing users with a more integrated and versatile blockchain experience. 14 | -------------------------------------------------------------------------------- /catalog/Ethereum/Abstracted.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Abstracted' 3 | --- 4 | 5 | ## 1.ethereum.token_metas 6 | ### Table Description 7 | Token metadata in the context of blockchain and cryptocurrencies typically refers to the set of data that describes the characteristics and details of a particular token. This metadata can include information such as the token's name, symbol, total supply, decimal precision, and other details relevant to its function and identity on the blockchain. It's essentially the descriptive data that gives context and identity to a token, distinguishing it from other tokens within the same blockchain ecosystem. Metadata is crucial for understanding the nature and purpose of a token, especially in applications like wallets, exchanges, and decentralized applications (dApps) where users interact with various types of tokens. 8 | ### Column Descriptions 9 | 10 |
11 | 18 |
19 | 20 | ### Table Sample 21 | 22 |
23 | 30 |
31 | 32 | ## 2.ethereum.onchain_trades 33 | ### Table Description 34 | The onchain_trades table records all transfer events on Ethereum, including both ERC-20 token transfers and native ETH transfers. This dataset enables users to track on-chain transactions in real time and is particularly useful for monitoring large transactions and analyzing token movements. 35 | ### Column Descriptions 36 | 37 |
38 | 45 |
46 | 47 | ### Table Sample 48 | 49 |
50 | 57 |
58 | -------------------------------------------------------------------------------- /catalog/Ethereum/Overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: '☆ Overview' 3 | --- 4 | 5 | Ethereum blockchain is a decentralized platform capable of executing smart contracts and decentralized applications (DApps). It was introduced by Vitalik Buterin in 2015 and is more general and flexible compared to Bitcoin's blockchain. The core of Ethereum is its virtual machine, the Ethereum Virtual Machine (EVM), which can execute Turing-complete scripts, allowing developers to create and deploy smart contracts. 6 | 7 | ### The Major Features of the Ethereum Blockchain 8 | 9 | 1. **Smart Contracts**: Smart contracts are self-executing contracts with predefined rules and conditions, running on the Ethereum blockchain. Once the conditions are met, the contract's execution is irreversible, ensuring transparency and trust. Smart contracts enable complex decentralized applications, such as decentralized finance (DeFi) platforms and non-fungible token (NFT) marketplaces. The automation and immutability of these contracts are core advantages of blockchain applications. 10 | 11 | 2. **Decentralized Applications (DApps)**: Ethereum supports the development and deployment of decentralized applications, which run on the blockchain without being controlled by a single entity. This makes applications more transparent and secure, while also reducing the risk of single points of failure due to centralized control. Developers can leverage Ethereum's tools and frameworks to create innovative decentralized solutions. The widespread application of DApps spans various sectors, including financial services, supply chain management, and identity verification, showcasing the versatility and innovative potential of the Ethereum platform. 12 | -------------------------------------------------------------------------------- /catalog/Fantom/Overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: '☆ Overview' 3 | --- 4 | 5 | Fantom is a decentralized, high-performance blockchain platform designed to overcome the limitations of previous generations of blockchain networks. Launched in 2019 by the Fantom Foundation, Fantom aims to provide a scalable, secure, and efficient environment for decentralized applications (DApps) and enterprise use cases. 6 | ### The Major Features of the Fantom Blockchain 7 | 8 | 1. **High Performance**: Fantom boasts high throughput and fast transaction finality, processing thousands of transactions per second with confirmation times of around 1 second. This performance is enabled by its unique consensus mechanism, Lachesis, a leaderless, asynchronous Byzantine Fault Tolerant (aBFT) protocol that ensures fast and secure consensus without compromising decentralization. 9 | 10 | 2. **Scalability**: Fantom is designed to be highly scalable, capable of supporting a large number of transactions and users without network congestion. Its architecture allows for the creation of multiple blockchains, each with its own specific use case and ruleset, which can interact with each other seamlessly. This modularity provides a scalable environment for diverse applications. 11 | 12 | 3. **Interoperability**: Fantom supports interoperability with other blockchain networks, enabling seamless asset and data transfer between Fantom and external blockchains. This is facilitated by Fantom’s cross-chain bridges and standardized communication protocols, ensuring efficient and secure interactions between different blockchain ecosystems. 13 | ### Data catalog 14 | 15 | 16 | 17 | Fantom Raw, unprocessed data on the Fantom chain, including blocks, transactions, and logs. 18 | 19 | -------------------------------------------------------------------------------- /catalog/Labels/Abstracted.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Abstracted' 3 | --- 4 | 5 | ## 1.labels.addresses 6 | ### Table Description 7 | Labels datasets attaches rich address and entity metadata to every address you query. No more blind spots—just clean, structured, and instantly usable identity data for your dApps, dashboards, and analytics tools. 8 | ### Column Descriptions 9 | 10 |
11 | 18 |
19 | 20 | ### Table Sample 21 | 22 |
23 | 30 |
-------------------------------------------------------------------------------- /catalog/Labels/Overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: '☆ Overview' 3 | --- 4 | 5 | Labels datasets attaches rich address and entity metadata to every address you query. No more blind spots—just clean, structured, and instantly usable identity data for your dApps, dashboards, and analytics tools. 6 | ### The Major Features of the Labels 7 | 8 | 1. **Decode counterparties on the fly**: Enrich every transaction with who’s behind the address. 9 | 10 | 2. **Avoid costly mistakes**: Labels help users avoid sending funds to shady or incorrect addresses. 11 | 12 | 3. **Faster builds**: Whether you're creating explorers, dashboards, or DeFi monitors, this saves hours of manual mapping. 13 | 14 | 4. **Plug-and-play**: Query once, get labeled data instantly—no need to build your own tagging system. 15 | 16 | ## Supported Chains 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 |
Chain
Blast
Fantom
Avalanche
Flare
Bnb
Base
Bsc
Mantle
Linea
Solana
Arbitrum
Optimism
Tron
Bitcoin
Polygon
Gnosis
74 | -------------------------------------------------------------------------------- /catalog/Merlin/Overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: '☆ Overview' 3 | --- 4 | 5 | Merlin is a cutting-edge blockchain platform designed to provide high scalability, security, and efficiency, making it an ideal environment for developing and deploying decentralized applications (DApps). Leveraging advanced consensus mechanisms and innovative architecture, Merlin aims to overcome the limitations of traditional blockchain networks while providing a seamless and efficient user experience. 6 | ### The Major Features of the Blast Blockchain 7 | 8 | 1. **High Scalability**: Merlin is built to handle a large volume of transactions with high throughput, enabling it to process thousands of transactions per second. This scalability ensures that the network can support a growing number of users and applications without experiencing congestion or delays. 9 | 10 | 2. **Low Fees**: One of Merlin’s key advantages is its low transaction fees. By optimizing its consensus protocol and network architecture, Merlin minimizes the cost of transactions, making it more accessible for users and developers. This cost efficiency encourages broader adoption and usage of decentralized applications on the Merlin network. 11 | 12 | 3. **Security**: Merlin employs robust security measures to ensure the integrity and safety of the network. Utilizing advanced cryptographic techniques and a secure consensus mechanism, Merlin provides strong protection against attacks and operational faults, maintaining a reliable and secure environment for DApps and transactions. 13 | 14 | Interoperability: Merlin supports interoperability with other blockchain networks, allowing for seamless asset transfers and data sharing across different chains. This cross-chain compatibility enhances the functionality of the Merlin ecosystem, providing users with a more integrated and versatile blockchain experience. 15 | ### Data catalog 16 | 17 | 18 | 19 | Merlin Raw, unprocessed data on the Merlin chain, including blocks, transactions, and logs. 20 | 21 | -------------------------------------------------------------------------------- /catalog/Optimism/Abstracted.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Abstracted' 3 | --- 4 | 5 | ## 1.optimism.token_metas 6 | ### Table Description 7 | Token metadata in the context of blockchain and cryptocurrencies typically refers to the set of data that describes the characteristics and details of a particular token. This metadata can include information such as the token's name, symbol, total supply, decimal precision, and other details relevant to its function and identity on the blockchain. It's essentially the descriptive data that gives context and identity to a token, distinguishing it from other tokens within the same blockchain ecosystem. Metadata is crucial for understanding the nature and purpose of a token, especially in applications like wallets, exchanges, and decentralized applications (dApps) where users interact with various types of tokens. 8 | ### Column Descriptions 9 | 10 |
11 | 18 |
19 | 20 | ### Table Sample 21 | 22 |
23 | 30 |
31 | -------------------------------------------------------------------------------- /catalog/Optimism/Decoded.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Decoded' 3 | --- 4 | ## 1. optimism.trace_calls_decoded 5 | ### Table Description 6 | The optimism.trace_calls_decoded table provides a comprehensive and human-readable view of the internal transactions and function calls within the Ethereum blockchain. By decoding trace calls, this table enables easier understanding and analysis of the complex interactions and operations that occur during transaction execution. 7 | ### Column Descriptions 8 | 9 |
10 | 17 |
18 | 19 | ### Table Sample 20 | 21 |
22 | 29 |
30 | ## 2. optimism.transaction_logs_decoded 31 | ### Table Description 32 | The optimism.trace_calls_decoded table provides a comprehensive and human-readable view of the internal transactions and function calls within the Ethereum blockchain. By decoding trace calls, this table enables easier understanding and analysis of the complex interactions and operations that occur during transaction execution. 33 | ### Column Descriptions 34 | 35 |
36 | 43 |
44 | 45 | ### Table Sample 46 | 47 |
48 | 55 |
56 | -------------------------------------------------------------------------------- /catalog/Optimism/Overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: '☆ Overview' 3 | --- 4 | 5 | Optimism is a Layer 2 scaling solution for Ethereum, designed to enhance the scalability and reduce the transaction costs of decentralized applications (DApps) on the Ethereum network. Developed by the Optimism Foundation, Optimism leverages optimistic rollup technology to achieve faster and cheaper transactions while maintaining the security and decentralization of the Ethereum main chain. 6 | ### The Major Features of the Optimism Blockchain 7 | 8 | 1. **Scalability**: Optimism significantly improves the scalability of Ethereum by using optimistic rollups, which aggregate multiple transactions into a single batch processed off-chain. This technique allows Optimism to handle thousands of transactions per second, reducing congestion and enhancing the overall performance of the network. 9 | 10 | 2. **Low Fees**: By processing transactions off-chain and only recording the final state on the Ethereum main chain, Optimism dramatically reduces transaction fees. This cost efficiency makes it more accessible for users and developers to interact with decentralized applications, promoting greater adoption and usage. 11 | 12 | 3. **EVM Compatibility**: Optimism is fully compatible with the Ethereum Virtual Machine (EVM), enabling developers to deploy their existing Ethereum-based smart contracts and DApps on Optimism with minimal modifications. This compatibility ensures a seamless transition for developers and allows them to leverage Ethereum’s extensive ecosystem of tools and libraries. -------------------------------------------------------------------------------- /catalog/OtherEvm/Atleta_Olympia.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Atleta Olympia' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- EVM-native modular execution layer 7 | 8 | Atleta Network is an EVM-native modular execution layer for wide sports applications adoption, with Atleta universal circuit and friendly interface. 9 | 10 | ### The MetaData of the Atleta Olympia Blockchain 11 | 12 | **Twitter Link**: https://x.com/Atleta_Network 13 | 14 | **Tags**: Infra, Layer1, Modular 15 | 16 | ### Blobs Column Descriptions 17 | 18 |
19 | 26 |
27 | 28 | ### Table Blobs Sample 29 | 30 |
31 | 38 |
39 | 40 | ### Transaction logs Column Descriptions 41 | 42 |
43 | 50 |
51 | 52 | ### Transaction logs Sample 53 | 54 |
55 | 62 |
63 | 64 | ### Transactions Column Descriptions 65 | 66 |
67 | 74 |
75 | 76 | ### Transactions Sample 77 | 78 |
79 | 86 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Automata_Testnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Automata Testnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- DAO research and -deployment company 7 | 8 | Automata Labs is a DAO research and deployment company. Their goal is to realize on-chain DAOs for cryptocurrencies and Web3. 9 | 10 | ### The MetaData of the Automata Testnet Blockchain 11 | 12 | **Twitter Link**: https://x.com/AutomataFinance 13 | 14 | **Tags**: Software Development 15 | 16 | ### Blobs Column Descriptions 17 | 18 |
19 | 26 |
27 | 28 | ### Table Blobs Sample 29 | 30 |
31 | 38 |
39 | 40 | ### Transaction logs Column Descriptions 41 | 42 |
43 | 50 |
51 | 52 | ### Transaction logs Sample 53 | 54 |
55 | 62 |
63 | 64 | ### Transactions Column Descriptions 65 | 66 |
67 | 74 |
75 | 76 | ### Transactions Sample 77 | 78 |
79 | 86 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/BEVM_Mainnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'BEVM Mainnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- EVM-compatible Bitcoin L2 7 | 8 | BEVM is a decentralized EVM-compatible Bitcoin L2 that uses BTC as Gas. It allows all DApps which can run in the Ethereum ecosystem to operate on Bitcoin L2. 9 | 10 | ### The MetaData of the BEVM Mainnet Blockchain 11 | 12 | **Twitter Link**: https://x.com/BTClayer2 13 | 14 | **Tags**: Infra, Layer2, Bitcoin Ecosystem 15 | 16 | ### Blobs Column Descriptions 17 | 18 |
19 | 26 |
27 | 28 | ### Table Blobs Sample 29 | 30 |
31 | 38 |
39 | 40 | ### Transaction logs Column Descriptions 41 | 42 |
43 | 50 |
51 | 52 | ### Transaction logs Sample 53 | 54 |
55 | 62 |
63 | 64 | ### Transactions Column Descriptions 65 | 66 |
67 | 74 |
75 | 76 | ### Transactions Sample 77 | 78 |
79 | 86 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/BEVM_Testnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'BEVM Testnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- EVM-compatible Bitcoin L2 7 | 8 | BEVM is a decentralized EVM-compatible Bitcoin L2 that uses BTC as Gas. It allows all DApps which can run in the Ethereum ecosystem to operate on Bitcoin L2. 9 | 10 | ### The MetaData of the BEVM Testnet Blockchain 11 | 12 | **Twitter Link**: https://x.com/BTClayer2 13 | 14 | **Tags**: Infra, Layer2, Bitcoin Ecosystem 15 | 16 | ### Blobs Column Descriptions 17 | 18 |
19 | 26 |
27 | 28 | ### Table Blobs Sample 29 | 30 |
31 | 38 |
39 | 40 | ### Transaction logs Column Descriptions 41 | 42 |
43 | 50 |
51 | 52 | ### Transaction logs Sample 53 | 54 |
55 | 62 |
63 | 64 | ### Transactions Column Descriptions 65 | 66 |
67 | 74 |
75 | 76 | ### Transactions Sample 77 | 78 |
79 | 86 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Crab_Network.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Crab Network' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- P2E idle game 7 | 8 | Crabada is a Player-to-Environment idle game set in a world occupied by fierce hermit crabs called Crabada. Players can earn in-game currencies, CRA, CRAM, and TUS, through mining, looting, breeding their crabs, or staking tokens. 9 | 10 | ### The MetaData of the Crab Network Blockchain 11 | 12 | **Twitter Link**: https://x.com/playcrabada 13 | 14 | **Documentation**: https://docs.crabada.com/ 15 | 16 | **Tags**: Gaming 17 | 18 | ### Blobs Column Descriptions 19 | 20 |
21 | 28 |
29 | 30 | ### Table Blobs Sample 31 | 32 |
33 | 40 |
41 | 42 | ### Transaction logs Column Descriptions 43 | 44 |
45 | 52 |
53 | 54 | ### Transaction logs Sample 55 | 56 |
57 | 64 |
65 | 66 | ### Transactions Column Descriptions 67 | 68 |
69 | 76 |
77 | 78 | ### Transactions Sample 79 | 80 |
81 | 88 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/DOS_Chain.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'DOS Chain' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- All-in-one NFT publishing platform 7 | 8 | DOSI is an all-in-one NFT publishing platform, powered by LINE and LINE Blockchain. It is designed for everyone, and welcomes brands from all around the world to create an NFT storefront and interact with their fans globally. 9 | 10 | ### The MetaData of the DOS Chain Blockchain 11 | 12 | **Twitter Link**: https://x.com/DOSI_official 13 | 14 | **Tags**: NFT, NFT marketplace 15 | 16 | ### Blobs Column Descriptions 17 | 18 |
19 | 26 |
27 | 28 | ### Table Blobs Sample 29 | 30 |
31 | 38 |
39 | 40 | ### Transaction logs Column Descriptions 41 | 42 |
43 | 50 |
51 | 52 | ### Transaction logs Sample 53 | 54 |
55 | 62 |
63 | 64 | ### Transactions Column Descriptions 65 | 66 |
67 | 74 |
75 | 76 | ### Transactions Sample 77 | 78 |
79 | 86 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Dodao.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Dodao' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- Web3 developers studio 7 | 8 | DoDao is a studio consists of developers who all have experience working on academy websites and creating free DeFi content. Past partners include: Aave, Project Serum, ENS, Balancer, and Compound. 9 | 10 | ### The MetaData of the Dodao Blockchain 11 | 12 | **Twitter Link**: https://x.com/dodao_io 13 | 14 | **Tags**: Software Development 15 | 16 | ### Blobs Column Descriptions 17 | 18 |
19 | 26 |
27 | 28 | ### Table Blobs Sample 29 | 30 |
31 | 38 |
39 | 40 | ### Transaction logs Column Descriptions 41 | 42 |
43 | 50 |
51 | 52 | ### Transaction logs Sample 53 | 54 |
55 | 62 |
63 | 64 | ### Transactions Column Descriptions 65 | 66 |
67 | 74 |
75 | 76 | ### Transactions Sample 77 | 78 |
79 | 86 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Form_Testnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Form Testnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- The sovereign network for onchain creations 7 | 8 | Forma is a purpose-built blockchain for fully onchain 9 | creations built on Astria with Celestia underneat. 10 | 11 | ### The MetaData of the Form Testnet Blockchain 12 | 13 | **Twitter Link**: https://x.com/Formachain 14 | 15 | **Tags**: Infra, Creator Economy 16 | 17 | ### Blobs Column Descriptions 18 | 19 |
20 | 27 |
28 | 29 | ### Table Blobs Sample 30 | 31 |
32 | 39 |
40 | 41 | ### Transaction logs Column Descriptions 42 | 43 |
44 | 51 |
52 | 53 | ### Transaction logs Sample 54 | 55 |
56 | 63 |
64 | 65 | ### Transactions Column Descriptions 66 | 67 |
68 | 75 |
76 | 77 | ### Transactions Sample 78 | 79 |
80 | 87 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Forma.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Forma' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- The sovereign network for onchain creations 7 | 8 | Forma is a purpose-built blockchain for fully onchain 9 | creations built on Astria with Celestia underneat. 10 | 11 | ### The MetaData of the Forma Blockchain 12 | 13 | **Twitter Link**: https://x.com/Formachain 14 | 15 | **Tags**: Infra, Creator Economy 16 | 17 | ### Blobs Column Descriptions 18 | 19 |
20 | 27 |
28 | 29 | ### Table Blobs Sample 30 | 31 |
32 | 39 |
40 | 41 | ### Transaction logs Column Descriptions 42 | 43 |
44 | 51 |
52 | 53 | ### Transaction logs Sample 54 | 55 |
56 | 63 |
64 | 65 | ### Transactions Column Descriptions 66 | 67 |
68 | 75 |
76 | 77 | ### Transactions Sample 78 | 79 |
80 | 87 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Forma_Sketchpad.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Forma Sketchpad' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- The sovereign network for onchain creations 7 | 8 | Forma is a purpose-built blockchain for fully onchain 9 | creations built on Astria with Celestia underneat. 10 | 11 | ### The MetaData of the Forma Sketchpad Blockchain 12 | 13 | **Twitter Link**: https://x.com/Formachain 14 | 15 | **Tags**: Infra, Creator Economy 16 | 17 | ### Blobs Column Descriptions 18 | 19 |
20 | 27 |
28 | 29 | ### Table Blobs Sample 30 | 31 |
32 | 39 |
40 | 41 | ### Transaction logs Column Descriptions 42 | 43 |
44 | 51 |
52 | 53 | ### Transaction logs Sample 54 | 55 |
56 | 63 |
64 | 65 | ### Transactions Column Descriptions 66 | 67 |
68 | 75 |
76 | 77 | ### Transactions Sample 78 | 79 |
80 | 87 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Fuse_Mainnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Fuse Mainnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- Blockchain as a service platform 7 | 8 | Fuse Charge is a Blockchain-as-a-Service platform that enables businesses and professional developers to easily integrate payments powered by the Fuse Network blockchain into their products via simple APIs. 9 | 10 | ### The MetaData of the Fuse Mainnet Blockchain 11 | 12 | **Tags**: Technology Solutions 13 | 14 | ### Blobs Column Descriptions 15 | 16 |
17 | 24 |
25 | 26 | ### Table Blobs Sample 27 | 28 |
29 | 36 |
37 | 38 | ### Transaction logs Column Descriptions 39 | 40 |
41 | 48 |
49 | 50 | ### Transaction logs Sample 51 | 52 |
53 | 60 |
61 | 62 | ### Transactions Column Descriptions 63 | 64 |
65 | 72 |
73 | 74 | ### Transactions Sample 75 | 76 |
77 | 84 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Fuse_Sparknet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Fuse Sparknet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- Blockchain as a service platform 7 | 8 | Fuse Charge is a Blockchain-as-a-Service platform that enables businesses and professional developers to easily integrate payments powered by the Fuse Network blockchain into their products via simple APIs. 9 | 10 | ### The MetaData of the Fuse Sparknet Blockchain 11 | 12 | **Tags**: Technology Solutions 13 | 14 | ### Blobs Column Descriptions 15 | 16 |
17 | 24 |
25 | 26 | ### Table Blobs Sample 27 | 28 |
29 | 36 |
37 | 38 | ### Transaction logs Column Descriptions 39 | 40 |
41 | 48 |
49 | 50 | ### Transaction logs Sample 51 | 52 |
53 | 60 |
61 | 62 | ### Transactions Column Descriptions 63 | 64 |
65 | 72 |
73 | 74 | ### Transactions Sample 75 | 76 |
77 | 84 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/GUNZ_Testnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'GUNZ Testnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- AAA game studio 7 | 8 | Gunzilla Games is a game developer currently working on Off The Grid (OTG), a cyberpunk Battle Royale 2.0. 9 | 10 | ### The MetaData of the GUNZ Testnet Blockchain 11 | 12 | **Twitter Link**: https://x.com/GunzillaGames 13 | 14 | **Tags**: Gaming, Studio 15 | 16 | ### Blobs Column Descriptions 17 | 18 |
19 | 26 |
27 | 28 | ### Table Blobs Sample 29 | 30 |
31 | 38 |
39 | 40 | ### Transaction logs Column Descriptions 41 | 42 |
43 | 50 |
51 | 52 | ### Transaction logs Sample 53 | 54 |
55 | 62 |
63 | 64 | ### Transactions Column Descriptions 65 | 66 |
67 | 74 |
75 | 76 | ### Transactions Sample 77 | 78 |
79 | 86 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Kakarot_Sepolia.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Kakarot Sepolia' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- EVM-compatible ZK-Rollup 7 | 8 | Kakarot is a zkEVM written in Cairo. It aims to allow users to leverage the scaling benefits of validity rollups while maintaining compatibility with the Ethereum ecosystem. Therefore, Kakarot can be used to run Ethereum smart contracts on Starknet. 9 | 10 | ### The MetaData of the Kakarot Sepolia Blockchain 11 | 12 | **Twitter Link**: https://x.com/KakarotZkEvm 13 | 14 | **Tags**: Infra, Layer2, ZK 15 | 16 | ### Blobs Column Descriptions 17 | 18 |
19 | 26 |
27 | 28 | ### Table Blobs Sample 29 | 30 |
31 | 38 |
39 | 40 | ### Transaction logs Column Descriptions 41 | 42 |
43 | 50 |
51 | 52 | ### Transaction logs Sample 53 | 54 |
55 | 62 |
63 | 64 | ### Transactions Column Descriptions 65 | 66 |
67 | 74 |
75 | 76 | ### Transactions Sample 77 | 78 |
79 | 86 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Karak_Sepolia.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Karak Sepolia' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- Ethereum L2 7 | 8 | Karak is the risk management infrastructure for digital assets that is a secure, low-cost, risk-aware Ethereum L2 built to secure the next billion users. 9 | 10 | ### The MetaData of the Karak Sepolia Blockchain 11 | 12 | **Twitter Link**: https://x.com/Karak_Network 13 | 14 | **Tags**: Infra, Layer2 15 | 16 | ### Blobs Column Descriptions 17 | 18 |
19 | 26 |
27 | 28 | ### Table Blobs Sample 29 | 30 |
31 | 38 |
39 | 40 | ### Transaction logs Column Descriptions 41 | 42 |
43 | 50 |
51 | 52 | ### Transaction logs Sample 53 | 54 |
55 | 62 |
63 | 64 | ### Transactions Column Descriptions 65 | 66 |
67 | 74 |
75 | 76 | ### Transactions Sample 77 | 78 |
79 | 86 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Lambda_Chain_Mainnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Lambda Chain Mainnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- Decentralized storage network 7 | 8 | Lambda is a public blockchain with decentralized data storage technology. 9 | 10 | ### The MetaData of the Lambda Chain Mainnet Blockchain 11 | 12 | **Twitter Link**: https://twitter.com/Lambdaim 13 | 14 | **Documentation**: https://www.lambda.im/doc/Lambda-Economic-White-Paper.pdf 15 | 16 | **Tags**: Infra, Layer1, Storage Network 17 | 18 | ### Blobs Column Descriptions 19 | 20 |
21 | 28 |
29 | 30 | ### Table Blobs Sample 31 | 32 |
33 | 40 |
41 | 42 | ### Transaction logs Column Descriptions 43 | 44 |
45 | 52 |
53 | 54 | ### Transaction logs Sample 55 | 56 |
57 | 64 |
65 | 66 | ### Transactions Column Descriptions 67 | 68 |
69 | 76 |
77 | 78 | ### Transactions Sample 79 | 80 |
81 | 88 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Lambda_Chain_Testnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Lambda Chain Testnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- Decentralized storage network 7 | 8 | Lambda is a public blockchain with decentralized data storage technology. 9 | 10 | ### The MetaData of the Lambda Chain Testnet Blockchain 11 | 12 | **Twitter Link**: https://twitter.com/Lambdaim 13 | 14 | **Documentation**: https://www.lambda.im/doc/Lambda-Economic-White-Paper.pdf 15 | 16 | **Tags**: Infra, Layer1, Storage Network 17 | 18 | ### Blobs Column Descriptions 19 | 20 |
21 | 28 |
29 | 30 | ### Table Blobs Sample 31 | 32 |
33 | 40 |
41 | 42 | ### Transaction logs Column Descriptions 43 | 44 |
45 | 52 |
53 | 54 | ### Transaction logs Sample 55 | 56 |
57 | 64 |
65 | 66 | ### Transactions Column Descriptions 67 | 68 |
69 | 76 |
77 | 78 | ### Transactions Sample 79 | 80 |
81 | 88 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Memo_Smart_Chain_Mainnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Memo Smart Chain Mainnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- Create & Collect to Earn in Real World 7 | 8 | Memoworld is a Web3 application, focusing on connecting users to the offline world. Everyone can record their footprints and life experiences using NFTs. 9 | 10 | ### The MetaData of the Memo Smart Chain Mainnet Blockchain 11 | 12 | **Twitter Link**: https://x.com/memoworld_xyz 13 | 14 | **Tags**: NFT 15 | 16 | ### Blobs Column Descriptions 17 | 18 |
19 | 26 |
27 | 28 | ### Table Blobs Sample 29 | 30 |
31 | 38 |
39 | 40 | ### Transaction logs Column Descriptions 41 | 42 |
43 | 50 |
51 | 52 | ### Transaction logs Sample 53 | 54 |
55 | 62 |
63 | 64 | ### Transactions Column Descriptions 65 | 66 |
67 | 74 |
75 | 76 | ### Transactions Sample 77 | 78 |
79 | 86 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Mint_Mainnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Mint Mainnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- NFT mint aggregator 7 | 8 | mint.fun is an NFT mint aggregator that shows users every project that is currently minting, ranked by popularity, so they don't have to search across various websites, Twitter, Discord, and group chats to figure out what to mint. It is built by the team at Context. 9 | 10 | ### The MetaData of the Mint Mainnet Blockchain 11 | 12 | **Twitter Link**: https://x.com/mintdotfun 13 | 14 | **Tags**: NFT, NFT Tools 15 | 16 | ### Blobs Column Descriptions 17 | 18 |
19 | 26 |
27 | 28 | ### Table Blobs Sample 29 | 30 |
31 | 38 |
39 | 40 | ### Transaction logs Column Descriptions 41 | 42 |
43 | 50 |
51 | 52 | ### Transaction logs Sample 53 | 54 |
55 | 62 |
63 | 64 | ### Transactions Column Descriptions 65 | 66 |
67 | 74 |
75 | 76 | ### Transactions Sample 77 | 78 |
79 | 86 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Mint_Testnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Mint Testnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- NFT mint aggregator 7 | 8 | mint.fun is an NFT mint aggregator that shows users every project that is currently minting, ranked by popularity, so they don't have to search across various websites, Twitter, Discord, and group chats to figure out what to mint. It is built by the team at Context. 9 | 10 | ### The MetaData of the Mint Testnet Blockchain 11 | 12 | **Twitter Link**: https://x.com/mintdotfun 13 | 14 | **Tags**: NFT, NFT Tools 15 | 16 | ### Blobs Column Descriptions 17 | 18 |
19 | 26 |
27 | 28 | ### Table Blobs Sample 29 | 30 |
31 | 38 |
39 | 40 | ### Transaction logs Column Descriptions 41 | 42 |
43 | 50 |
51 | 52 | ### Transaction logs Sample 53 | 54 |
55 | 62 |
63 | 64 | ### Transactions Column Descriptions 65 | 66 |
67 | 74 |
75 | 76 | ### Transactions Sample 77 | 78 |
79 | 86 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/OP_Celestia_Raspberry.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'OP Celestia Raspberry' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- NFT marketplace 7 | 8 | OpenSea is an NFT marketplace for discovering, collecting, and selling NFTs. 9 | 10 | ### The MetaData of the OP Celestia Raspberry Blockchain 11 | 12 | **Twitter Link**: https://x.com/opensea 13 | 14 | **Blog URL**: https://opensea.io/blog 15 | 16 | **Documentation**: https://docs.opensea.io/ 17 | 18 | **Tags**: NFT, NFT marketplace 19 | 20 | ### Blobs Column Descriptions 21 | 22 |
23 | 30 |
31 | 32 | ### Table Blobs Sample 33 | 34 |
35 | 42 |
43 | 44 | ### Transaction logs Column Descriptions 45 | 46 |
47 | 54 |
55 | 56 | ### Transaction logs Sample 57 | 58 |
59 | 66 |
67 | 68 | ### Transactions Column Descriptions 69 | 70 |
71 | 78 |
79 | 80 | ### Transactions Sample 81 | 82 |
83 | 90 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/OP_Mainnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'OP Mainnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- NFT marketplace 7 | 8 | OpenSea is an NFT marketplace for discovering, collecting, and selling NFTs. 9 | 10 | ### The MetaData of the OP Mainnet Blockchain 11 | 12 | **Twitter Link**: https://x.com/opensea 13 | 14 | **Blog URL**: https://opensea.io/blog 15 | 16 | **Documentation**: https://docs.opensea.io/ 17 | 18 | **Tags**: NFT, NFT marketplace 19 | 20 | ### Blobs Column Descriptions 21 | 22 |
23 | 30 |
31 | 32 | ### Table Blobs Sample 33 | 34 |
35 | 42 |
43 | 44 | ### Transaction logs Column Descriptions 45 | 46 |
47 | 54 |
55 | 56 | ### Transaction logs Sample 57 | 58 |
59 | 66 |
67 | 68 | ### Transactions Column Descriptions 69 | 70 |
71 | 78 |
79 | 80 | ### Transactions Sample 81 | 82 |
83 | 90 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Opal_testnet_by_Unique.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Opal testnet by Unique' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- DEX Liquidity protocol 7 | 8 | Opal is the DEX liquidity protocol on Ethereum that enhances Dexs liquidity through the introduction of Omnipools, and its $GEM token plays a central role in the governance of the protocol. 9 | 10 | ### The MetaData of the Opal testnet by Unique Blockchain 11 | 12 | **Twitter Link**: https://x.com/OpalDeFi 13 | 14 | **Tags**: DeFi, DEX 15 | 16 | ### Blobs Column Descriptions 17 | 18 |
19 | 26 |
27 | 28 | ### Table Blobs Sample 29 | 30 |
31 | 38 |
39 | 40 | ### Transaction logs Column Descriptions 41 | 42 |
43 | 50 |
51 | 52 | ### Transaction logs Sample 53 | 54 |
55 | 62 |
63 | 64 | ### Transactions Column Descriptions 65 | 66 |
67 | 74 |
75 | 76 | ### Transactions Sample 77 | 78 |
79 | 86 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Open_Campus_Codex.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Open Campus Codex' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- NFT marketplace 7 | 8 | OpenSea is an NFT marketplace for discovering, collecting, and selling NFTs. 9 | 10 | ### The MetaData of the Open Campus Codex Blockchain 11 | 12 | **Twitter Link**: https://x.com/opensea 13 | 14 | **Blog URL**: https://opensea.io/blog 15 | 16 | **Documentation**: https://docs.opensea.io/ 17 | 18 | **Tags**: NFT, NFT marketplace 19 | 20 | ### Blobs Column Descriptions 21 | 22 |
23 | 30 |
31 | 32 | ### Table Blobs Sample 33 | 34 |
35 | 42 |
43 | 44 | ### Transaction logs Column Descriptions 45 | 46 |
47 | 54 |
55 | 56 | ### Transaction logs Sample 57 | 58 |
59 | 66 |
67 | 68 | ### Transactions Column Descriptions 69 | 70 |
71 | 78 |
79 | 80 | ### Transactions Sample 81 | 82 |
83 | 90 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/RSS3_VSL_Sepolia_Testnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'RSS3 VSL Sepolia Testnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- Open Information Layer 7 | 8 | RSS3 is the Open Information Layer, structuring open information for social, search, and AI. RSS3's mission is to construct the Open Web by enhancing the free flow of Open Information. 9 | 10 | ### The MetaData of the RSS3 VSL Sepolia Testnet Blockchain 11 | 12 | **Twitter Link**: https://x.com/rss3_ 13 | 14 | **Blog URL**: https://blog.rss3.io/ 15 | 16 | **Tags**: Social, AI 17 | 18 | ### Blobs Column Descriptions 19 | 20 |
21 | 28 |
29 | 30 | ### Table Blobs Sample 31 | 32 |
33 | 40 |
41 | 42 | ### Transaction logs Column Descriptions 43 | 44 |
45 | 52 |
53 | 54 | ### Transaction logs Sample 55 | 56 |
57 | 64 |
65 | 66 | ### Transactions Column Descriptions 67 | 68 |
69 | 76 |
77 | 78 | ### Transactions Sample 79 | 80 |
81 | 88 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Swan_Proxima_Testnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Swan Proxima Testnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- Bitcoin financial services firm 7 | 8 | Swan is a Bitcoin financial services firm on a mission to help people stack Bitcoin, for the long term, in every investment vehicle possible. 9 | 10 | ### The MetaData of the Swan Proxima Testnet Blockchain 11 | 12 | **Twitter Link**: https://x.com/Swan 13 | 14 | **LinkedIn**: https://www.linkedin.com/company/swanbitcoin/ 15 | 16 | **Tags**: CeFi, Asset Management（CeFi） 17 | 18 | ### Blobs Column Descriptions 19 | 20 |
21 | 28 |
29 | 30 | ### Table Blobs Sample 31 | 32 |
33 | 40 |
41 | 42 | ### Transaction logs Column Descriptions 43 | 44 |
45 | 52 |
53 | 54 | ### Transaction logs Sample 55 | 56 |
57 | 64 |
65 | 66 | ### Transactions Column Descriptions 67 | 68 |
69 | 76 |
77 | 78 | ### Transactions Sample 79 | 80 |
81 | 88 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Swan_Saturn_Testnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Swan Saturn Testnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- Bitcoin financial services firm 7 | 8 | Swan is a Bitcoin financial services firm on a mission to help people stack Bitcoin, for the long term, in every investment vehicle possible. 9 | 10 | ### The MetaData of the Swan Saturn Testnet Blockchain 11 | 12 | **Twitter Link**: https://x.com/Swan 13 | 14 | **LinkedIn**: https://www.linkedin.com/company/swanbitcoin/ 15 | 16 | **Tags**: CeFi, Asset Management（CeFi） 17 | 18 | ### Blobs Column Descriptions 19 | 20 |
21 | 28 |
29 | 30 | ### Table Blobs Sample 31 | 32 |
33 | 40 |
41 | 42 | ### Transaction logs Column Descriptions 43 | 44 |
45 | 52 |
53 | 54 | ### Transaction logs Sample 55 | 56 |
57 | 64 |
65 | 66 | ### Transactions Column Descriptions 67 | 68 |
69 | 76 |
77 | 78 | ### Transactions Sample 79 | 80 |
81 | 88 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/TAPROOT_Mainnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'TAPROOT Mainnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- Bitcoin-focused Ordinals project 7 | 8 | Taproot Wizards is a Bitcoin-focused Ordinals project that was inspired by the original Bitcoin wizard Reddit meme from a decade ago. 9 | 10 | ### The MetaData of the TAPROOT Mainnet Blockchain 11 | 12 | **Twitter Link**: https://x.com/TaprootWizards 13 | 14 | **LinkedIn**: https://www.linkedin.com/company/taprootwizards 15 | 16 | **Tags**: Ordinals, Bitcoin Ecosystem 17 | 18 | ### Blobs Column Descriptions 19 | 20 |
21 | 28 |
29 | 30 | ### Table Blobs Sample 31 | 32 |
33 | 40 |
41 | 42 | ### Transaction logs Column Descriptions 43 | 44 |
45 | 52 |
53 | 54 | ### Transaction logs Sample 55 | 56 |
57 | 64 |
65 | 66 | ### Transactions Column Descriptions 67 | 68 |
69 | 76 |
77 | 78 | ### Transactions Sample 79 | 80 |
81 | 88 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/UPB_CRESCDI_Testnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'UPB CRESCDI Testnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- Crypto trading platform with grade automated trading bots 7 | 8 | UpBots is a crypto trading platform that brings institutional-grade automated trading bots, social copy trading, and other advanced trading tools built on the blockchain to retail investors. 9 | 10 | ### The MetaData of the UPB CRESCDI Testnet Blockchain 11 | 12 | **Twitter Link**: https://x.com/UpBots 13 | 14 | **Tags**: Tools, Trading robot 15 | 16 | ### Blobs Column Descriptions 17 | 18 |
19 | 26 |
27 | 28 | ### Table Blobs Sample 29 | 30 |
31 | 38 |
39 | 40 | ### Transaction logs Column Descriptions 41 | 42 |
43 | 50 |
51 | 52 | ### Transaction logs Sample 53 | 54 |
55 | 62 |
63 | 64 | ### Transactions Column Descriptions 65 | 66 |
67 | 74 |
75 | 76 | ### Transactions Sample 77 | 78 |
79 | 86 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Vitruveo_Mainnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Vitruveo Mainnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- Decentralized ecosystem for creators 7 | 8 | Vitruveo is a decentralized ecosystem for creators. Launching Blockchain Protocol, Early Adopter Rewards, Innovative dApps, On-chain Licensing & more. 9 | 10 | ### The MetaData of the Vitruveo Mainnet Blockchain 11 | 12 | **Twitter Link**: https://x.com/vitruveochain 13 | 14 | **Tags**: Creator Economy 15 | 16 | ### Blobs Column Descriptions 17 | 18 |
19 | 26 |
27 | 28 | ### Table Blobs Sample 29 | 30 |
31 | 38 |
39 | 40 | ### Transaction logs Column Descriptions 41 | 42 |
43 | 50 |
51 | 52 | ### Transaction logs Sample 53 | 54 |
55 | 62 |
63 | 64 | ### Transactions Column Descriptions 65 | 66 |
67 | 74 |
75 | 76 | ### Transactions Sample 77 | 78 |
79 | 86 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/Vitruveo_Testnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Vitruveo Testnet' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- Decentralized ecosystem for creators 7 | 8 | Vitruveo is a decentralized ecosystem for creators. Launching Blockchain Protocol, Early Adopter Rewards, Innovative dApps, On-chain Licensing & more. 9 | 10 | ### The MetaData of the Vitruveo Testnet Blockchain 11 | 12 | **Twitter Link**: https://x.com/vitruveochain 13 | 14 | **Tags**: Creator Economy 15 | 16 | ### Blobs Column Descriptions 17 | 18 |
19 | 26 |
27 | 28 | ### Table Blobs Sample 29 | 30 |
31 | 38 |
39 | 40 | ### Transaction logs Column Descriptions 41 | 42 |
43 | 50 |
51 | 52 | ### Transaction logs Sample 53 | 54 |
55 | 62 |
63 | 64 | ### Transactions Column Descriptions 65 | 66 |
67 | 74 |
75 | 76 | ### Transactions Sample 77 | 78 |
79 | 86 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/XR_Sepolia.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'XR Sepolia' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- AI Powered trading expert insights platform 7 | 8 | XRADERS is a AI crypto insights platform that empower investors to make informed decision making by curated expert's insights. 9 | 10 | ### The MetaData of the XR Sepolia Blockchain 11 | 12 | **Twitter Link**: https://x.com/xraders_xyz 13 | 14 | **Tags**: Tools 15 | 16 | ### Blobs Column Descriptions 17 | 18 |
19 | 26 |
27 | 28 | ### Table Blobs Sample 29 | 30 |
31 | 38 |
39 | 40 | ### Transaction logs Column Descriptions 41 | 42 |
43 | 50 |
51 | 52 | ### Transaction logs Sample 53 | 54 |
55 | 62 |
63 | 64 | ### Transactions Column Descriptions 65 | 66 |
67 | 74 |
75 | 76 | ### Transactions Sample 77 | 78 |
79 | 86 |
-------------------------------------------------------------------------------- /catalog/OtherEvm/re.al.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 're.al' 3 | icon: "database" 4 | iconType: "light" 5 | --- 6 | -- Tokenized RWAs L2 7 | 8 | re.al is a permissionless L2 for tokenized RWAs. Built on Arbitrum Orbit. 9 | 10 | ### The MetaData of the re.al Blockchain 11 | 12 | **Twitter Link**: https://x.com/real_rwa 13 | 14 | **Documentation**: https://docs.re.al/ 15 | 16 | **Tags**: Infra, Layer2, RWA 17 | 18 | ### Blobs Column Descriptions 19 | 20 |
21 | 28 |
29 | 30 | ### Table Blobs Sample 31 | 32 |
33 | 40 |
41 | 42 | ### Transaction logs Column Descriptions 43 | 44 |
45 | 52 |
53 | 54 | ### Transaction logs Sample 55 | 56 |
57 | 64 |
65 | 66 | ### Transactions Column Descriptions 67 | 68 |
69 | 76 |
77 | 78 | ### Transactions Sample 79 | 80 |
81 | 88 |
-------------------------------------------------------------------------------- /catalog/Polygon/Abstracted.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Abstracted' 3 | --- 4 | 5 | ## 1.polygon.token_metas 6 | ### Table Description 7 | Token metadata in the context of blockchain and cryptocurrencies typically refers to the set of data that describes the characteristics and details of a particular token. This metadata can include information such as the token's name, symbol, total supply, decimal precision, and other details relevant to its function and identity on the blockchain. It's essentially the descriptive data that gives context and identity to a token, distinguishing it from other tokens within the same blockchain ecosystem. Metadata is crucial for understanding the nature and purpose of a token, especially in applications like wallets, exchanges, and decentralized applications (dApps) where users interact with various types of tokens. 8 | ### Column Descriptions 9 | 10 |
11 | 18 |
19 | 20 | ### Table Sample 21 | 22 |
23 | 30 |
31 | -------------------------------------------------------------------------------- /catalog/Polygon/Decoded.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Decoded' 3 | --- 4 | ## 1.polygon.trace_calls_decoded 5 | ### Table Description 6 | The polygon.trace_calls_decoded table provides a comprehensive and human-readable view of the internal transactions and function calls within the Ethereum blockchain. By decoding trace calls, this table enables easier understanding and analysis of the complex interactions and operations that occur during transaction execution. 7 | ### Column Descriptions 8 | 9 |
10 | 17 |
18 | 19 | ### Table Sample 20 | 21 |
22 | 29 |
30 | ## 2.polygon.transaction_logs_decoded 31 | ### Table Description 32 | The polygon.transaction_logs_decoded table contains decoded logs from Ethereum transactions, providing a human-readable view of the events emitted by smart contracts. Logs are essential for understanding the actions and state changes that occur during the execution of smart contracts. By decoding these logs, the table offers a more accessible and detailed perspective on blockchain activities. 33 | ### Column Descriptions 34 | 35 |
36 | 43 |
44 | 45 | ### Table Sample 46 | 47 |
48 | 55 |
-------------------------------------------------------------------------------- /catalog/Polygon/Overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: '☆ Overview' 3 | --- 4 | 5 | Polygon, formerly known as Matic Network, is a decentralized platform designed to improve the scalability and usability of Ethereum while retaining its core values of decentralization and security. Launched in 2017, Polygon offers a framework for building and connecting Ethereum-compatible blockchain networks, providing solutions for scalability issues through sidechains and Layer 2 solutions. 6 | ### The Major Features of the Polygon Blockchain 7 | 8 | 1. **Scalability**: Polygon enhances the scalability of Ethereum by providing a framework for building and connecting multiple Layer 2 solutions and sidechains. These solutions help offload transactions from the Ethereum main chain, reducing congestion and improving transaction speeds. Polygon's architecture allows for thousands of transactions per second, significantly higher than Ethereum's native capacity. 9 | 10 | 2. **Interoperability**: Polygon facilitates interoperability between different blockchain networks, allowing assets and data to move seamlessly across chains. This cross-chain compatibility is achieved through a set of standardized protocols that ensure secure and efficient communication between connected networks. The interoperability features enable developers to create more versatile and interconnected decentralized applications. 11 | 12 | 3. **Security**: Polygon leverages the security of the Ethereum network while adding its own security measures to ensure the integrity and safety of its sidechains and Layer 2 solutions. By using Ethereum's robust consensus mechanism and additional security protocols, Polygon ensures that its network remains secure and resilient against attacks. -------------------------------------------------------------------------------- /catalog/Price/Overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: '☆ Overview' 3 | --- 4 | 5 | We provide token price data across 8 blockchains for over 8,000 tokens, offering both real-time and historical price tracking. This dataset allows users to access the latest token prices as well as historical price trends for deeper analysis. 6 | ### The Major Features of the Token Price 7 | 8 | 1. **Freshness**: Updated hourly to reflect market changes. 9 | 10 | 2. **Querying**: Retrieve the most recent price for any supported token. 11 | 12 | 3. **Use Case**: Ideal for applications needing current token prices (e.g., dashboards, price tracking). 13 | 14 | ## Supported Chains 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 |
Chain
Ethereum
Polygon
BSC
Avalanche
Arbitrum One
Optimism
Base
zkSync
48 | -------------------------------------------------------------------------------- /catalog/Sui/Overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: '☆ Overview' 3 | --- 4 | 5 | Sui is a decentralized blockchain platform designed to deliver high performance, scalability, and security, making it an ideal choice for developing and deploying decentralized applications (DApps). Leveraging innovative consensus mechanisms and advanced architecture, Sui aims to overcome the limitations of traditional blockchain networks while providing a seamless and efficient user experience. 6 | ### The Major Features of the Sui Blockchain 7 | 8 | 1. **High Performance**: Sui is built to handle a high volume of transactions with low latency, enabling it to process thousands of transactions per second. This high throughput ensures that the network can support a growing number of users and applications without experiencing congestion or delays. 9 | 10 | 2. **Scalability**: Sui's architecture is designed to be highly scalable, capable of supporting a large number of transactions and users simultaneously. This scalability is achieved through advanced consensus protocols and network optimization, ensuring that Sui can meet the demands of various decentralized applications. 11 | 12 | 3. **Security**: Sui employs robust security measures to ensure the integrity and safety of the network. Utilizing advanced cryptographic techniques and a secure consensus mechanism, Sui provides strong protection against attacks and operational faults, maintaining a reliable and secure environment for DApps and transactions. 13 | 14 | 4. Interoperability: Sui supports interoperability with other blockchain networks, allowing for seamless asset transfers and data sharing across different chains. This cross-chain compatibility enhances the functionality of the Sui ecosystem, providing users with a more integrated and versatile blockchain experience. -------------------------------------------------------------------------------- /catalog/Ton/Overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: '☆ Overview' 3 | --- 4 | 5 | TON (The Open Network) is a decentralized blockchain platform initially developed by the Telegram team and now maintained by the TON Foundation. Designed to offer high performance, scalability, and security, TON aims to support a wide range of decentralized applications (DApps) and services while providing a seamless user experience. 6 | ### The Major Features of the TON Blockchain 7 | 8 | 1. **High Performance**: TON is designed to handle a high volume of transactions with low latency, capable of processing thousands of transactions per second. This high throughput ensures that the network can support a growing number of users and applications without experiencing congestion or delays. 9 | 10 | 2. **Scalability**: TON employs a multi-chain architecture, known as sharding, to enhance its scalability. This approach allows the network to process multiple transactions simultaneously across different shards, ensuring that TON can efficiently scale to meet the demands of various decentralized applications. 11 | 12 | 3. **Security**: TON utilizes robust security measures to ensure the integrity and safety of the network. By employing advanced cryptographic techniques and a secure consensus mechanism, TON provides strong protection against attacks and operational faults, maintaining a reliable and secure environment for DApps and transactions. 13 | 14 | ### Quick Start 15 | 16 | - [Data Cloud](https://docs.chainbase.com/platform/features/datacloud/overview#quickstart) 17 | -------------------------------------------------------------------------------- /catalog/Tron/Overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: '☆ Overview' 3 | --- 4 | 5 | TRON is a decentralized blockchain platform designed to create a free, global digital content entertainment system with distributed storage technology. Launched in 2017 by Justin Sun, TRON aims to remove intermediaries by allowing content creators to publish, store, and own data freely and to be compensated directly by consumers. TRON's high throughput and scalability make it suitable for developing decentralized applications (DApps) and supporting a wide range of blockchain-based use cases. 6 | 7 | ### The Major Features of the TRON Blockchain 8 | 9 | 1. **High Throughput**: TRON's blockchain architecture enables high throughput, with the ability to process up to 2,000 transactions per second. This high capacity supports a broad range of decentralized applications and ensures that the network can handle high demand without congestion. 10 | 11 | 2. **Scalability**: TRON is designed to be highly scalable, capable of supporting a large user base and numerous transactions simultaneously. Its scalable infrastructure makes it suitable for hosting large-scale DApps and decentralized services. 12 | 13 | 3. **Decentralized Applications (DApps)**: TRON provides a robust environment for the development and deployment of decentralized applications. Developers can create a wide range of DApps, leveraging TRON's scalable and high-performance blockchain. The TRON ecosystem supports various DApps, including games, social media, and financial services, fostering innovation and growth. 14 | -------------------------------------------------------------------------------- /catalog/Tron/Raw.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Raw' 3 | --- 4 | ## 1. tron.stable_coin_transfers 5 | ### Table Description 6 | Stablecoin transfers refer to the movement of stablecoins, which are cryptocurrencies designed to maintain a stable value by pegging their price to a reserve asset or a basket of assets. Stablecoins are commonly used in the cryptocurrency space for trading, remittances, and as a store of value due to their price stability. Stablecoin transfers can be tracked on the blockchain, providing transparency and auditability of transactions. These transfers can involve sending stablecoins between users, wallets, exchanges, or smart contracts, and the details of each transfer are recorded on the blockchain for verification and analysis. 7 | 8 | ### Column Descriptions 9 | 10 |
11 | 18 |
19 | 20 | ### Table Sample 21 | 22 |
23 | 30 |
-------------------------------------------------------------------------------- /catalog/zkSync/Abstracted.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Abstracted' 3 | --- 4 | 5 | ## 1.zksync.token_metas 6 | ### Table Description 7 | Token metadata in the context of blockchain and cryptocurrencies typically refers to the set of data that describes the characteristics and details of a particular token. This metadata can include information such as the token's name, symbol, total supply, decimal precision, and other details relevant to its function and identity on the blockchain. It's essentially the descriptive data that gives context and identity to a token, distinguishing it from other tokens within the same blockchain ecosystem. Metadata is crucial for understanding the nature and purpose of a token, especially in applications like wallets, exchanges, and decentralized applications (dApps) where users interact with various types of tokens. 8 | ### Column Descriptions 9 | 10 |
11 | 18 |
19 | 20 | ### Table Sample 21 | 22 |
23 | 30 |
31 | -------------------------------------------------------------------------------- /catalog/zkSync/Decoded.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Decoded' 3 | --- 4 | 5 | ## 1. zkSync.trace_calls_decoded 6 | ### Table Description 7 | The zksync.trace_calls_decoded table provides a comprehensive and human-readable view of the internal transactions and function calls within the Ethereum blockchain. By decoding trace calls, this table enables easier understanding and analysis of the complex interactions and operations that occur during transaction execution. 8 | ### Column Descriptions 9 | 10 |
11 | 18 |
19 | 20 | ### Table Sample 21 | 22 |
23 | 30 |
31 | ## 2. zkSync.transaction_logs_decoded 32 | ### Table Description 33 | The zksync.transaction_logs_decoded table contains decoded logs from Ethereum transactions, providing a human-readable view of the events emitted by smart contracts. Logs are essential for understanding the actions and state changes that occur during the execution of smart contracts. By decoding these logs, the table offers a more accessible and detailed perspective on blockchain activities. 34 | ### Column Descriptions 35 | 36 |
37 | 44 |
45 | 46 | ### Table Sample 47 | 48 |
49 | 56 |
-------------------------------------------------------------------------------- /catalog/zkSync/Overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: '☆ Overview' 3 | --- 4 | 5 | zkSync is a Layer 2 scaling solution for Ethereum, designed to provide high throughput and low transaction costs while maintaining the security and decentralization of the Ethereum network. Developed by Matter Labs, zkSync leverages zk-rollup technology to offer fast and cost-effective transactions, making it a powerful platform for decentralized applications (DApps). 6 | ### The Major Features of the zkSync Blockchain 7 | 8 | 1. Scalability: zkSync significantly enhances Ethereum's scalability by bundling multiple transactions into a single batch, which is then processed off-chain before being committed to the Ethereum main chain. This zk-rollup technique allows zkSync to handle thousands of transactions per second, reducing congestion and improving overall network performance. 9 | 10 | 2. Low Fees: By processing transactions off-chain and only recording the final state on the Ethereum main chain, zkSync dramatically reduces transaction fees. This cost efficiency makes blockchain interactions more affordable for users and developers, promoting greater adoption and usage of decentralized applications. 11 | 12 | 3. EVM Compatibility: zkSync is fully compatible with the Ethereum Virtual Machine (EVM), enabling developers to deploy their existing Ethereum-based smart contracts and DApps on zkSync with minimal modifications. This compatibility ensures a seamless transition for developers and allows them to leverage Ethereum’s extensive ecosystem of tools and libraries. -------------------------------------------------------------------------------- /contributing/cips.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Chainbase Improvement Proposals (CIPs)' 3 | sidebarTitle: 'CIPs' 4 | --- 5 | 6 | Chainbase Improvement Proposals (CIPs) outline standards for the Chainbase network. These include core protocol specifications, client APIs, and contract standards. Network upgrades are discussed separately in the Chainbase CIPs repository. 7 | 8 | ## Contributing 9 | - Review CIPs: Familiarize yourself with the process by reading CIPs. 10 | - Clone the Repository: Start by cloning our CIPs repository. 11 | - Submit Your CIP: Use the provided template to draft your proposal and submit a Pull Request to the CIPs repository. 12 | 13 | ## CIP Status Terms 14 | - Idea: Preliminary concept, not yet formally tracked. 15 | - Draft: First tracked stage, properly formatted and submitted. 16 | - Review: Ready for peer review. 17 | - Last: Final review stage, typically lasting 30 days. 18 | - Final: Established as a standard, only updated for corrections. 19 | - Stagnant: Inactive for 6+ months, can be reactivated. 20 | - Withdrawn: Proposal has been withdrawn and cannot be reused. 21 | - Living: Continuously updated, never final (e.g., CIP-1). 22 | 23 | ## Meta 24 | Processes or changes affecting Chainbase development, requiring community consensus. 25 | 26 | ## Informational 27 | Guidelines or information for the Chainbase community, not proposing new features. 28 | 29 | For more details, visit our CIP documentation and guidelines. -------------------------------------------------------------------------------- /contributing/governance.mdx: -------------------------------------------------------------------------------- 1 | Chainbase embraces a governance model based on rough consensus and running code. Changes are driven by proposals, community buy-in, and the implementation of running code. The consensus process involves different stakeholders: 2 | 3 | 1. **Workers** - Provides blockchain data 4 | 2. **Developers** - Build and create manuscripts 5 | 3. **Consumers** - Pay $C query data network 6 | 4. **Delegators** - Delegate $C to worker & secure the network 7 | 8 | This model avoids rigid structures, voting, or official roles, promoting action, diversity of viewpoints, and decentralization. Most changes follow the CIP (Chainbase Improvement Proposal) process. -------------------------------------------------------------------------------- /contributing/overview.mdx: -------------------------------------------------------------------------------- 1 | At Chainbase, we welcome and appreciate contributions of all sizes from the community. Thanks to the efforts of over 50 core contributors and tens of thousands of developers, our network and protocols have grown and improved significantly. 2 | 3 | Your contributions, no matter how big or small, make a difference. Let's build something great together! 4 | 5 | ## Documentation 6 | Welcome to the central hub for all documents. If you have any feedback, we encourage you to contribute by opening an issue or creating a pull request at [docs.chainbase.com](https://docs.chainbase.com) . 7 | 8 | 9 | ## Community 10 | [Website](https://chainbase.com) - Official website (https://chainbase.com) . 11 | 12 | [X (Twitter)](https://x.com/ChainbaseHQ) - Any updates and announcements about Chainbase. 13 | 14 | [Discord](https://discord.gg/chainbase) - Public chat for developer support. 15 | 16 | [Github](https://github.com/chainbase-labs) - Code and Proposal Discussion. -------------------------------------------------------------------------------- /core-concepts/architecture/co_processor_layer.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Co-processor Layer' 3 | --- 4 | 5 | # **Introduction** 6 | 7 | 🌐 Chainbase realized early on that with the widespread application of blockchain technology, different application scenarios would generate a large amount of diverse data. Extracting value from these isolated and varied data sets is a challenging problem. 8 | 9 | ✨ Pre-set data sets cannot meet the customized needs of developers. We need to open up modular and composable stack capabilities to fully unleash developers' creativity. This creativity will transform into knowledge, which is why we need a Co-processor Layer. This will allow a large number of developers to collaborate around the Chainbase Network, accumulating knowledge and generating collective intelligence. 10 | 11 | # **What is the Co-Processor Layer?** 12 | 13 | ![death spiral](../../images/co-processor-layer.png) 14 | 15 | The Co-Processor Layer of the Chainbase Network is a component designed to facilitate user collaboration in contributing data processing and AI expert knowledge. Its main functions include: 16 | 17 | 1. **Knowledge Contribution**: Users can contribute their expertise in data processing and specialized task models to the Co-Processor Layer. This collaborative environment harnesses collective intelligence to enhance the network's capabilities. 18 | 2. **Assetization of Knowledge**: Contributions in the Co-Processor Layer are transformed into assets. This layer manages the distribution, circulation, and trading of these assets, ensuring contributors are rewarded for their knowledge and efforts. 19 | 3. **\$C Token Ecosystem**: The Co-Processor Layer revolves around the $C token, which is integral to the network's incentive structure. It facilitates payments, settlements, staking, and governance, creating a vibrant and dynamic ecosystem. -------------------------------------------------------------------------------- /core-concepts/glossary.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Glossary' 3 | --- 4 | 5 | ## Common Terms 6 | 7 | - ⚗️**Alchemist** - a developer or technical contributor who creates, manipulates, or alters manuscripts. 8 | - 📜**Manuscript** - an executable that runs on the Chainbase Virtual Machine (CVM). Manuscripts define the standard schema that different data sources need to follow when converting into datasets. 9 | - ⚙️**Chainbase Virtual Machine (CVM)** - a virtual execution environment, complete with interface, that allows for the execution of sophisticated data queries. 10 | - 💾**Data Set -** a structured collection of aggregated, validated, and indexed data comprised of data tables and stored in the Chainbase Warehouse. 11 | - 🏭**Chainbase Warehouse** - a storeplace for all pre-built datasets on the Data Platform. 12 | - 💽**Data Network** - the intersection of CVM/Eigenlayer AVS (execution), IBC, ABCI++, and CometBFT (consensus), with a proprietary Data Availability Layer composed of roll ups/network participants. 13 | - 💿**Data Platform** - the suite of developer tools which allow streamlined access to information available on the Data Network. 14 | - 🤖**TheiaChat** - an AI agent, based on Theia, offering streamlined access point to the data network with built-in knowledge bases. 15 | - 🗺️**Theia** - the proprietary Crypto World Model which uses causal reasoning on crypto patterns to create verifiable reasoning chains on crypto data. -------------------------------------------------------------------------------- /core-concepts/manuscript/QuickStart/prerequisites.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "1. Install GUI" 3 | --- 4 | 5 | # 1. Mansucript GUI Installation 6 | 7 | Download GUI binary for latest release, run: 8 | ``` 9 | curl -fsSL https://github.com/chainbase-labs/manuscript-core/raw/main/install-gui.sh | bash 10 | ``` 11 | 12 | 13 | # 2. Mansucript Requirements 14 | ### Docker 15 | Ensure that Docker is properly installed and functional on your system, as it is essential for the Manuscript environment setup. Docker enables deployment and management of isolated containers required by Manuscript's ecosystem. For detailed installation instructions, please refer to the [Docker documentation](https://docs.docker.com/get-started/get-docker/). 16 | 17 | ### Docker Compose 18 | Alongside Docker, Docker Compose is required and should be correctly installed and configured. Docker Compose enables the orchestration of multi-container applications, making it easier to deploy and manage Manuscript's dependencies. For setup guidance, refer to the [Docker Compose documentation](https://docs.docker.com/compose/install/). 19 | 20 | ### Linux Environment 21 | Manuscript is designed for compatibility with Linux environments only. Ensure that you have access to a Linux-compatible system, such as macOS, CentOS, or Fedora. either directly or through a Linux-based container setup in Docker, to proceed with the installation and operation of Manuscript. 22 | 23 | # 3. Checking for Requirements 24 | On a native Linux system, you can use the `uname -a` command to obtain information about your Linux distribution. 25 | 26 | If you are not using a native Linux system and need a Linux environment through Docker, you can check if Docker is installed by following these steps: 27 | 28 | 1.Open a terminal or command prompt. 29 | 30 | 2.Run the following command to verify that Docker is installed and operational: 31 | ``` 32 | docker --version 33 | docker compose version 34 | ``` 35 | -------------------------------------------------------------------------------- /core-concepts/manuscript/QuickStart/run_manuscript.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "3. Run a manuscript" 3 | --- 4 | 5 | ## Deploy Target 6 | 7 | ### 1. 📗 Local 8 | You can use our GUI tool to quickly deploy Manuscript locally. 9 | ![manuscript_deploy.png](../../../images/manuscripts/manuscript_deploy.png) 10 | 11 | ### 2. 📚 Network 12 | We are about to launch the Chainbase network Manuscript environment, allowing users to deploy Manuscript directly to the Chainbase network. 13 | 14 | 15 | ## Deployment Options 16 | There are three ways to deploy your Manuscript: 17 | 18 | ### 1. 🚗 Using the GUI Tool 19 | Edit and deploy your Manuscript directly within the GUI. This is the most straightforward and efficient method. 20 | 21 | ### 2. 🚌 Using Docker Compose 22 | Copy the docker-compose file from the [Manuscript-Core](https://github.com/chainbase-labs/manuscript-core/tree/main/examples) repository to deploy it locally. 23 | 24 | ### 3. 🚅 Using Manuscript-Lib (Coming Soon) 25 | Deploy your Manuscript with a single click through the Manuscript-Lib browser. 26 | 27 | -------------------------------------------------------------------------------- /core-concepts/manuscript/quick_start.mdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/core-concepts/manuscript/quick_start.mdx -------------------------------------------------------------------------------- /developers/explorers.mdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/developers/explorers.mdx -------------------------------------------------------------------------------- /developers/faucet.mdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/developers/faucet.mdx -------------------------------------------------------------------------------- /developers/getting_started.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Getting Started' 3 | --- 4 | 5 | ## Coming soon -------------------------------------------------------------------------------- /developers/manuscripts.mdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/developers/manuscripts.mdx -------------------------------------------------------------------------------- /developers/open_apis.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Open APIs' 3 | --- 4 | 5 | ## Public Available RPC Endpoints 6 | ### Testnet 7 | | **Address** | **Maintainer** | 8 | |-------------------|--------------------------| 9 | | https://testnet.s.chainbase.com | [Altlayer](https://www.altlayer.io/) | 10 | | https://chainbase-testnet-public.s.chainbase.com | [Chainbase](https://www.chainbase.com/) | 11 | | [Sign up and start for free (Zan)](https://zan.top/home/node-service) | [Zan](https://zan.top/) | -------------------------------------------------------------------------------- /developers/smart_contracts.mdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/developers/smart_contracts.mdx -------------------------------------------------------------------------------- /developers/testnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Co-processor Layer Testnet' 3 | --- 4 | 5 | ## Overview 6 | The [Co-processor Layer](/core-concepts/architecture/co_processor_layer) is building a community-driven collaborative layer for data developers, aimed at continuously unlocking and enhancing the value of crypto data. Built on the advanced [OP stack](https://docs.optimism.io/stack/getting-started) architecture and integrated with the innovative [Superchain](https://app.optimism.io/superchain/) ecosystem, it ensures efficient, scalable, and secure data processing and management. 7 | 8 | ## Info 9 | | **Parameter** | Value | 10 | |-------------------|--------------------------| 11 | | **Network Name** | Chainbase Network testnet | 12 | | **Rollup Stack Type** | OP Stack | 13 | | **Settlement Layer** | Sepolia Testnet | 14 | | **Chain ID** | 2233 | 15 | | **Currency Symbol** | ETH | 16 | | **Explorer** | https://testnet.explorer.chainbase.com/ | 17 | | **Bridge** | https://testnet.bridge.chainbase.com/ | 18 | 19 | ## Guide 20 | 1. Add the Chainbase Network testnet to your wallet via the [Rollup Info Page](https://rollup-info.altlayer.io/enough-fog-compact/chainbase_testnet). 21 | 2. Bridge your Sepolia Testnet ETH to the Chainbase Network testnet using the [bridge interface](https://testnet.bridge.chainbase.com/). 22 | **Note:** Get Sepolia Testnet ETH from [sepoliafaucet.com](https://sepoliafaucet.com/) or [sepoliafaucet.io](https://www.sepoliafaucet.io/). 23 | 3. After initiating the deposit, wait about 1 minute for it to complete. Then, you can start deploying your contracts on the Chainbase Network testnet. 24 | -------------------------------------------------------------------------------- /developers/tools_&_sdks.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Tools & SDKs' 3 | --- 4 | 5 | ## Coming soon -------------------------------------------------------------------------------- /developers/wallet_integration.mdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/developers/wallet_integration.mdx -------------------------------------------------------------------------------- /essentials/code.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Code Blocks' 3 | description: 'Display inline code and code blocks' 4 | icon: 'code' 5 | --- 6 | 7 | ## Basic 8 | 9 | ### Inline Code 10 | 11 | To denote a `word` or `phrase` as code, enclose it in backticks (`). 12 | 13 | ``` 14 | To denote a `word` or `phrase` as code, enclose it in backticks (`). 15 | ``` 16 | 17 | ### Code Block 18 | 19 | Use [fenced code blocks](https://www.markdownguide.org/extended-syntax/#fenced-code-blocks) by enclosing code in three backticks and follow the leading ticks with the programming language of your snippet to get syntax highlighting. Optionally, you can also write the name of your code after the programming language. 20 | 21 | ```java HelloWorld.java 22 | class HelloWorld { 23 | public static void main(String[] args) { 24 | System.out.println("Hello, World!"); 25 | } 26 | } 27 | ``` 28 | 29 | ````md 30 | ```java HelloWorld.java 31 | class HelloWorld { 32 | public static void main(String[] args) { 33 | System.out.println("Hello, World!"); 34 | } 35 | } 36 | ``` 37 | ```` 38 | -------------------------------------------------------------------------------- /essentials/images.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Images and Embeds' 3 | description: 'Add image, video, and other HTML elements' 4 | icon: 'image' 5 | --- 6 | 7 | 11 | 12 | ## Image 13 | 14 | ### Using Markdown 15 | 16 | The [markdown syntax](https://www.markdownguide.org/basic-syntax/#images) lets you add images using the following code 17 | 18 | ```md 19 | ![title](/path/image.jpg) 20 | ``` 21 | 22 | Note that the image file size must be less than 5MB. Otherwise, we recommend hosting on a service like [Cloudinary](https://cloudinary.com/) or [S3](https://aws.amazon.com/s3/). You can then use that URL and embed. 23 | 24 | ### Using Embeds 25 | 26 | To get more customizability with images, you can also use [embeds](/writing-content/embed) to add images 27 | 28 | ```html 29 | 30 | ``` 31 | 32 | ## Embeds and HTML elements 33 | 34 | 44 | 45 |
46 | 47 | 48 | 49 | Mintlify supports [HTML tags in Markdown](https://www.markdownguide.org/basic-syntax/#html). This is helpful if you prefer HTML tags to Markdown syntax, and lets you create documentation with infinite flexibility. 50 | 51 | 52 | 53 | ### iFrames 54 | 55 | Loads another HTML page within the document. Most commonly used for embedding videos. 56 | 57 | ```html 58 | 59 | ``` 60 | -------------------------------------------------------------------------------- /essentials/navigation.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Navigation' 3 | description: 'The navigation field in mint.json defines the pages that go in the navigation menu' 4 | icon: 'map' 5 | --- 6 | 7 | The navigation menu is the list of links on every website. 8 | 9 | You will likely update `mint.json` every time you add a new page. Pages do not show up automatically. 10 | 11 | ## Navigation syntax 12 | 13 | Our navigation syntax is recursive which means you can make nested navigation groups. You don't need to include `.mdx` in page names. 14 | 15 | 16 | 17 | ```json Regular Navigation 18 | "navigation": [ 19 | { 20 | "group": "Getting Started", 21 | "pages": ["quickstart"] 22 | } 23 | ] 24 | ``` 25 | 26 | ```json Nested Navigation 27 | "navigation": [ 28 | { 29 | "group": "Getting Started", 30 | "pages": [ 31 | "quickstart", 32 | { 33 | "group": "Nested Reference Pages", 34 | "pages": ["nested-reference-page"] 35 | } 36 | ] 37 | } 38 | ] 39 | ``` 40 | 41 | 42 | 43 | ## Folders 44 | 45 | Simply put your MDX files in folders and update the paths in `mint.json`. 46 | 47 | For example, to have a page at `https://yoursite.com/your-folder/your-page` you would make a folder called `your-folder` containing an MDX file called `your-page.mdx`. 48 | 49 | 50 | 51 | You cannot use `api` for the name of a folder unless you nest it inside another folder. Mintlify uses Next.js which reserves the top-level `api` folder for internal server calls. A folder name such as `api-reference` would be accepted. 52 | 53 | 54 | 55 | ```json Navigation With Folder 56 | "navigation": [ 57 | { 58 | "group": "Group Name", 59 | "pages": ["your-folder/your-page"] 60 | } 61 | ] 62 | ``` 63 | 64 | ## Hidden Pages 65 | 66 | MDX files not included in `mint.json` will not show up in the sidebar but are accessible through the search bar and by linking directly to them. 67 | -------------------------------------------------------------------------------- /favicon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/favicon.png -------------------------------------------------------------------------------- /images/aquamarine-roadmap.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/aquamarine-roadmap.png -------------------------------------------------------------------------------- /images/avs-design-01.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/avs-design-01.png -------------------------------------------------------------------------------- /images/avs-design-02.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/avs-design-02.png -------------------------------------------------------------------------------- /images/catalog/blocks.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/catalog/blocks.png -------------------------------------------------------------------------------- /images/catalog/contract_decoded.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/catalog/contract_decoded.png -------------------------------------------------------------------------------- /images/catalog/contracts.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/catalog/contracts.png -------------------------------------------------------------------------------- /images/catalog/decoded.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/catalog/decoded.jpg -------------------------------------------------------------------------------- /images/catalog/decoded02.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/catalog/decoded02.jpg -------------------------------------------------------------------------------- /images/catalog/decoded_ton_query.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/catalog/decoded_ton_query.png -------------------------------------------------------------------------------- /images/catalog/docs-blobs.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/catalog/docs-blobs.png -------------------------------------------------------------------------------- /images/catalog/ton-decoded-search.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/catalog/ton-decoded-search.png -------------------------------------------------------------------------------- /images/chainbase_litepaper.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/chainbase_litepaper.jpg -------------------------------------------------------------------------------- /images/chainbase_litepaper_kr.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/chainbase_litepaper_kr.jpg -------------------------------------------------------------------------------- /images/checks-passed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/checks-passed.png -------------------------------------------------------------------------------- /images/co-processor-layer.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/co-processor-layer.png -------------------------------------------------------------------------------- /images/consensus-layer-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/consensus-layer-1.png -------------------------------------------------------------------------------- /images/da-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/da-1.png -------------------------------------------------------------------------------- /images/da-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/da-2.png -------------------------------------------------------------------------------- /images/da-3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/da-3.png -------------------------------------------------------------------------------- /images/da-4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/da-4.png -------------------------------------------------------------------------------- /images/da-5.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/da-5.png -------------------------------------------------------------------------------- /images/data-processing-based-on-avs.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/data-processing-based-on-avs.png -------------------------------------------------------------------------------- /images/dual-chain-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/dual-chain-1.png -------------------------------------------------------------------------------- /images/dual-staking-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/dual-staking-1.png -------------------------------------------------------------------------------- /images/dual-staking-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/dual-staking-2.png -------------------------------------------------------------------------------- /images/faq/how_to_get_api_key.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/faq/how_to_get_api_key.gif -------------------------------------------------------------------------------- /images/introducing_banner.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/introducing_banner.jpeg -------------------------------------------------------------------------------- /images/manuscript_01.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/manuscript_01.png -------------------------------------------------------------------------------- /images/manuscript_02.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/manuscript_02.png -------------------------------------------------------------------------------- /images/manuscripts/manuscript_datasets.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/manuscripts/manuscript_datasets.png -------------------------------------------------------------------------------- /images/manuscripts/manuscript_debug_01.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/manuscripts/manuscript_debug_01.png -------------------------------------------------------------------------------- /images/manuscripts/manuscript_debug_02.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/manuscripts/manuscript_debug_02.png -------------------------------------------------------------------------------- /images/manuscripts/manuscript_deploy.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/manuscripts/manuscript_deploy.png -------------------------------------------------------------------------------- /images/manuscripts/manuscript_github.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/manuscripts/manuscript_github.png -------------------------------------------------------------------------------- /images/manuscripts/manuscript_gui.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/manuscripts/manuscript_gui.png -------------------------------------------------------------------------------- /images/manuscripts/manuscript_yaml.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/manuscripts/manuscript_yaml.png -------------------------------------------------------------------------------- /images/manuscripts/zone.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/manuscripts/zone.png -------------------------------------------------------------------------------- /images/manuscripts_overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/manuscripts_overview.png -------------------------------------------------------------------------------- /images/overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/overview.png -------------------------------------------------------------------------------- /images/role.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/role.png -------------------------------------------------------------------------------- /images/tokenomic.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/tokenomic.png -------------------------------------------------------------------------------- /images/zircon-roadmap.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/images/zircon-roadmap.png -------------------------------------------------------------------------------- /introduction.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: Introduction 3 | description: 'Welcome to the home of your new documentation' 4 | --- 5 | 6 | ## Setting up 7 | 8 | The first step to world-class documentation is setting up your editing environments. 9 | 10 | 11 | 16 | Get your docs set up locally for easy development 17 | 18 | 23 | Preview your changes before you push to make sure they're perfect 24 | 25 | 26 | 27 | ## Make it yours 28 | 29 | Update your docs to your brand and add valuable content for the best user conversion. 30 | 31 | 32 | 37 | Customize your docs to your company's colors and brands 38 | 39 | 44 | Automatically generate endpoints from an OpenAPI spec 45 | 46 | 51 | Build interactive features and designs to guide your users 52 | 53 | 58 | Check out our showcase of our favorite documentation 59 | 60 | 61 | -------------------------------------------------------------------------------- /introduction/faqs.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'FAQs' 3 | --- 4 | 5 | 6 | ## What are all the ways I can get involved? 7 | 8 | - Use our [Data Platform](https://console.chainbase.com/register) 9 | - Join our [Data Network](https://chainbase.mintlify.app/introduction/networks/overview) 10 | - Use our AI Agent 11 | - Write a [Manuscript](https://chainbase.mintlify.app/core-concepts/manuscript) 12 | - Join our [Discord](https://chainbase.com/discord) 13 | 14 | ## When testnet? When mainnet? When token? 15 | 16 | Soon! Be sure to follow us on [X](https://x.com/ChainbaseHQ) for latest updates. 17 | 18 | ## Is Chainbase open source? 19 | 20 | Chainbase is in the process of open-sourcing all user-facing products and services; for the most up-to-date, you can take a look at our github repository here: https://github.com/chainbase-labs 21 | 22 | ## Will Chainbase work for smart contracts? 23 | 24 | No! Chainbase does not execute contracts - it is specifically for making data accessible both on and off-chain. Rather than writing smart contracts, developers can execute sophisticated data processing using [manuscripts](https://chainbase.mintlify.app/core-concepts/manuscript#overview). 25 | 26 | ## Will I need to know Solidity to write manuscripts? 27 | 28 | No! Most manuscripts are written in [SQL](https://chainbase.mintlify.app/core-concepts/manuscript#gpl). With [GPL](https://chainbase.mintlify.app/core-concepts/manuscript#gpl), you can write manuscripts in Typescript, Solidity, even Python. 29 | 30 | ## Who can I reach out to for more help? 31 | 32 | For more help, Join our Discord or reach out to our DevRel, [KagemniKarimu](https://x.com/kagemnikarimu) -------------------------------------------------------------------------------- /introduction/litepaper.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Litepaper' 3 | --- 4 | 5 | 6 | 7 | 8 | English Litepaper 9 | 10 | 11 |

12 | 13 | Download: Chainbase: The Decentralized Omnichain Data Network for Open AGI Economy 14 | 15 |

16 | 17 | 18 | 19 | Korean Litepaper 20 | 21 | 22 |

23 | 24 | 다운로드: Chainbase: 오픈 AGI 경제를 위한 탈중앙화 옴니체인 데이터 네트워크 25 | 26 |

27 | 28 | -------------------------------------------------------------------------------- /introduction/networks/benefits.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Benefits' 3 | --- 4 | 5 | ## Coming soon -------------------------------------------------------------------------------- /introduction/networks/delegators.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Delegators" 3 | --- 4 | 5 | ## Delegators 6 | 7 | Delegators enhance the economic security of the network by staking their tokens to validators and operators. The Chainbase network uses a dual staking mechanism, where delegators can choose to stake `$ETH (or $LST)` and `$C`. 8 | 9 | ### Staking Tokens 10 | 11 | Delegators can stake their tokens to support validators and operators, contributing to the network's security and stability. 12 | 13 | 1. **Choose Tokens**: Decide whether to stake `$ETH (or $LST)` or `$C`. 14 | 2. **Select Validators/Operators**: Choose the validators and operators you want to support. 15 | 3. **Stake Tokens**: Use the staking interface to delegate your tokens to the selected validators and operators. 16 | 17 | ### Earning Rewards 18 | 19 | By staking tokens, delegators earn a share of the rewards earned by the validators and operators they support. 20 | for details refer to [tokenomics](/introduction/tokenomics) 21 | 22 | ### Community and Support 23 | 24 | Join the Chainbase delegator discord to collaborate with other delegators, share knowledge, and get support. 25 | -------------------------------------------------------------------------------- /introduction/networks/operators.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Operators' 3 | --- 4 | 5 | ## Operators 6 | 7 | Operators play a crucial role in the network by providing the necessary computational resources for the execution layer, ensuring the smooth operation of data processing tasks. Operators are rewarded in a manner akin to proof-of-work, with greater workloads demanding higher hardware requirements. 8 | 9 | ### Becoming an Operator 10 | 11 | To become an operator in the Chainbase network, follow these steps: 12 | 13 | 1. **Register**: Register as an operator on the Holesky testnet or the mainnet of the Eigenlayer smart contract. This will register your Ethereum public key with the Eigenlayer smart contract. Follow the instructions on [Eigenlayer](https://docs.eigenlayer.xyz/eigenlayer/operator-guides/operator-installation). 14 | 2. **Set Up Infrastructure**: Ensure you have the necessary hardware and software infrastructure to support the network's computational requirements. 15 | 3. **Run Node Software**: Install and run the Chainbase node software to start participating in the network. 16 | 17 | ### Responsibilities 18 | 19 | Operators are responsible for maintaining and managing the computational infrastructure required for data processing tasks. 20 | 21 | 1. **Infrastructure Management**: Maintain and manage the hardware and software infrastructure to ensure efficient operation. 22 | 2. **Data Processing**: Process and execute data query requests submitted by data developers. 23 | 24 | ### Earning Rewards 25 | 26 | Operators earn rewards based on the quality and quantity of data processing services they provide. The network incentivizes operators to maintain and optimize their computing resources. 27 | for details refer to [tokenomics](../tokenomics.mdx). 28 | 29 | ### Community and Support 30 | 31 | Join the Chainbase discord operators channel to collaborate with other operators, share knowledge, and get support. -------------------------------------------------------------------------------- /node/configuration.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Configuration" 3 | --- 4 | ## Coming soon -------------------------------------------------------------------------------- /node/introduction.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Introduction" 3 | --- 4 | 5 | 6 | As the Chainbase Network enters the testnet phase, network nodes will be open for participation 7 | 8 | 9 | ## What is a Chainbase Network Node? 10 | 11 | A Chainbase Network node is an operator running the Chainbase Network node software and playing an active role in the network. The nodes in the Chainbase Network are divided into two roles: Operator and Validator. 12 | 13 | ### 1. Operator 14 | 15 | Operators play a crucial role in the network by providing the necessary computational resources for the execution layer, ensuring the smooth operation of data processing tasks. The Operator Node constructs the Eigenlayer AVS. As the Chainbase Network testnet phase prepares to launch, we will open up participation for Operators, inviting interested users to join. 16 | 17 | ### 2. Validator 18 | 19 | Validators play a key role in maintaining the security and consensus of the network. They are responsible for ensuring data integrity and maintaining network stability. The Validator Node is constructed based on the Cosmos SDK, using the CometBFT and DPoS consensus mechanisms. As the Chainbase Network testnet phase prepares to launch, we will open up participation for Validators, inviting interested users to join. 20 | 21 | ## How to Participate as a Chainbase Network Node? 22 | 23 | If you are interested in becoming an Operator or Validator for the Chainbase Network, please contact the Chainbase Network team for more information and guidance. We look forward to your participation in advancing the Chainbase Network. -------------------------------------------------------------------------------- /node/mainnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Join Mainnet' 3 | --- 4 | 5 | ## Coming soon -------------------------------------------------------------------------------- /node/testnet.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Join Testnet' 3 | --- 4 | 5 | ## Coming soon -------------------------------------------------------------------------------- /node/validator.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Run a Validator' 3 | --- 4 | 5 | ## Coming soon -------------------------------------------------------------------------------- /pdf/Chainbase_litepaper.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/pdf/Chainbase_litepaper.pdf -------------------------------------------------------------------------------- /pdf/Chainbase_litepaper_KR.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chainbase-labs/chainbase-docs/fc4a6d8d395dff6b3adf0576d58485b8c3eb6a8e/pdf/Chainbase_litepaper_KR.pdf -------------------------------------------------------------------------------- /platform/apis/data-cloud-v1.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Data Cloud v1" 3 | --- 4 | -------------------------------------------------------------------------------- /platform/apis/data-cloud-v2.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Data Cloud v2(Alpha)" 3 | --- 4 | -------------------------------------------------------------------------------- /platform/apis/data-sync.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Data Sync" 3 | --- 4 | -------------------------------------------------------------------------------- /platform/apis/predefined-apis.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Predefined APIs" 3 | --- 4 | -------------------------------------------------------------------------------- /platform/apis/quickstart.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Quickstart" 3 | --- 4 | -------------------------------------------------------------------------------- /platform/apis/rpc-nodes.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "RPC Nodes" 3 | --- 4 | -------------------------------------------------------------------------------- /platform/datasets/data-catalog.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Data Catalog" 3 | url: "/catalog/overview" 4 | --- 5 | -------------------------------------------------------------------------------- /platform/faqs/faq.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "FAQs" 3 | --- 4 | 5 | ## Account 6 | 7 | ### 1. How to get API key? 8 | 9 | ![death spiral](../../images/faq/how_to_get_api_key.gif) 10 | 11 | ### 2. What is the QPS in the Chainbase Console? 12 | 13 | You can find more information in [pricing](https://chainbase.com/pricing) 14 | 15 | ## APIs 16 | 17 | ### 1. What is Custom API, and how can I get access to Custom API? Are there any difference with Task API? 18 | 19 | * [Task API](/platform/features/api/sql-api/datacloud-task-api): Asynchronous real-time requests with high data freshness (less concurrency scenarios). 20 | * [Custom API](/platform/features/api/sql-api/datacloud-custom-api): High concurrency and low latency (with slightly reduced data freshness, at least 5 minutes). 21 | 22 | Custom API is not available for all users. Please contact us for more information. 23 | -------------------------------------------------------------------------------- /platform/features/api/log-explorer.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Log Explorer" 3 | --- 4 | -------------------------------------------------------------------------------- /platform/features/api/sql-api/datacloud-api-classic.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Data Cloud API (Deprecated)" 3 | --- 4 | 5 | 6 | ❗️ Warning 7 | 8 | The feature will be discontinued and no longer available on [ 2024-12-31 ] 9 | 10 | Recommend using our latest version of the [DataCloud API.](/platform/features/api/sql-api/datacloud-task-api) 11 | 12 | 13 | 14 | 📘 Don’t have an API key? 15 | 16 | Go to [console.chainbase.com](https://console.chainbase.com/) to create an account and a new API key. 17 | 18 | 19 | ## What is Data Cloud? 20 | 21 | The Chainbase Data Cloud lets you run your low-latency queries through an endpoint to leverage all our indexed datasets for your custom needs. Chainbase's [Data Cloud](/platform/datasets/overview) is a fully managed online data warehouse service for Web3 developers. Developers can query the data warehouse through the **API** to access our datasets with zero infra cost. And the **Data Cloud**'s scalable, distributed analytical data engine and intelligent data modeling allow you to query terabytes of data **in seconds**. 22 | 23 | ## Quickstart 24 | 25 | Query the hashes of the last 3,000 blocks in Ethereum and the number of transactions in each block: 26 | 27 | ```bash 28 | curl -X "POST" "https://api.chainbase.online/v1/dw/query" \ 29 | -H 'X-API-KEY: YOUR-API-KEY ' \ 30 | -H 'Content-Type: application/json; charset=utf-8' \ 31 | -d $'{ 32 | "query": "select number, transactions_count from ethereum.blocks order by number desc limit 3000;" 33 | }' 34 | ``` 35 | 36 | If there are more than 1000 rows, you need to paginate through the`task_id` and `page` to get all the results: 37 | 38 | ```bash 39 | curl -X "POST" "https://api.chainbase.online/v1/dw/query" \ 40 | -H 'X-API-KEY: YOUR-API-KEY ' \ 41 | -H 'Content-Type: application/json; charset=utf-8' \ 42 | -d $'{ 43 | "task_id": "xxxxxxxxxxxxxxxxxxxxx", 44 | "page": 2 45 | }' 46 | ``` 47 | 48 | ## API Reference 49 | 50 | If you want to know more details on the endpoint and optional parameters, check out: 51 | 52 | - [SQL API (Classic)](/api-reference/sql-api/data-cloud-sql-query) 53 | -------------------------------------------------------------------------------- /platform/features/api/sql-api/datacloud-custom-api.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Data Cloud Custom API (Alpha)" 3 | description: "A data request method supporting high-concurrency scenarios." 4 | --- 5 | 6 | The Custom API functionality is designed to offer an efficient and reliable data processing solution, by automatically updating and persistently storing users' SQL query results according to a predetermined schedule in a relational database engineered to handle high concurrency and high throughput demands. This strategy, by sacrificing a certain degree of data real-time accuracy, achieves optimization in reducing response time and enhancing the number of requests processed. Compared to our Task API, the distinctiveness of the Custom API functionality lies in its less stringent requirement for data immediacy. 7 | 8 | - **Task API**: Asynchronous real-time requests with high data freshness (less concurrency scenarios). 9 | - **Custom API**: High concurrency and low latency (with slightly reduced data freshness,at least 5 minutes). 10 | 11 | ![](https://files.readme.io/507a0b7-image.png) 12 | 13 | ![](https://files.readme.io/1398f86-image.png) 14 | 15 | ![](https://files.readme.io/a0204dd-image.png) 16 | 17 | ![](https://files.readme.io/a5ea53e-image.png) 18 | 19 | ![](https://files.readme.io/df39799-image.png) 20 | 21 | ![](https://files.readme.io/8e2ecb8-image.png) 22 | 23 | ![](https://files.readme.io/218aafc-image.png) 24 | -------------------------------------------------------------------------------- /platform/features/api/sql-api/datacloud-task-api.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Data Cloud Task API (Alpha)" 3 | --- 4 | 5 | **Unified Datasets** 6 | 7 | Users can now explore and query across three layers of datasets - Raw, Decoded, and Abstracted - within DataCloud. 8 | 9 | 10 | 11 | **Parameterized Queries** 12 | 13 | With our new Parameterized Queries feature, users can now craft more dynamic and customized SQL queries. 14 | 15 | 16 | 17 | 18 | **Task API** 19 | 20 | Our Task API enable seamless integration with a wide range of applications, ensuring continuous access to the latest data. 21 | 22 | 23 | 24 | 25 | ## API Reference 26 | 27 | If you want to know more details on the endpoint and optional parameters, check out: 28 | 29 | - [SQL API (Alpha)](/api-reference/sql-api/execute-queries) 30 | -------------------------------------------------------------------------------- /platform/features/api/sql-api/overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Overview" 3 | --- 4 | 5 | 6 | 📘 Don’t have an API key? 7 | 8 | Go to [console.chainbase.com](https://console.chainbase.com/) to create an account and a new API key. 9 | 10 | 11 | ## What is SQL API? 12 | 13 | The Chainbase SQL API lets you run your low-latency queries through an endpoint to leverage all our indexed datasets for your custom needs. 14 | 15 | The SQL API is powered by Chainbase's [Data Cloud](/platform/features/datacloud/overview), a fully managed online data warehouse service for Web3 developers. Developers can query the data warehouse through the **SQL API** to access our datasets with zero infra cost. And the **Data Cloud**'s scalable, distributed analytical data engine and intelligent data modeling allow you to query terabytes of data **in seconds**. 16 | -------------------------------------------------------------------------------- /platform/features/decoding-contracts.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Decoding Contracts" 3 | --- 4 | -------------------------------------------------------------------------------- /platform/overview.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Overview" 3 | --- 4 | 5 | Welcome to Chainbase Data Platform docs. All-in-one web3 data infrastructure for indexing, transforming, and utilizing large-scale on-chain data. 6 | 7 | ## What is Chainbase Data Platform? 8 | 9 | Chainbase Data Platform is an all-in-one data infrastructure for Web3 that allows you to index, transform, and utilize large-scale on-chain data. It is a platform that provides a suite of tools and services to help you build, manage, and scale your Web3 applications. 10 | 11 | By leveraging enriched on-chain data and streaming computing technologies across one data infrastructure, Chainbase Data Platform automates the indexing and querying of blockchain data, enabling developers to accomplish complex data tasks with ease. 12 | 13 | ## Products & Features 14 | 15 | ### API - Indexed Data 16 | 17 | Chainbase Data Platform provides a powerful API that allows you to access indexed data from the blockchain. The API is designed to be easy to use and provides a wide range of features to help you get the data you need. 18 | 19 | ### Datasets 20 | 21 | Chainbase Data Platform supports a wide range of raw, decoded, and abstracted datasets for you to build next-level apps with cutting-edge protocols today and tomorrow. 22 | 23 | ### Data Cloud 24 | 25 | Data Cloud lets you run your low-latency queries through an endpoint to leverage all our indexed datasets for your custom needs. 26 | 27 | ### Data Sync - Stream data to your backend 28 | 29 | With Data Sync, you can stream the data you need into your own infrastructure in real-time, and then use it to build powerful applications. 30 | -------------------------------------------------------------------------------- /platform/pricing/pricing.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Pricing" 3 | url: "https://platform.chainbase.com/pricing" 4 | --- 5 | -------------------------------------------------------------------------------- /platform/support.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Support" 3 | url: "https://chainbase.com/help" 4 | --- 5 | -------------------------------------------------------------------------------- /snippets/snippet-intro.mdx: -------------------------------------------------------------------------------- 1 | One of the core principles of software development is DRY (Don't Repeat 2 | Yourself). This is a principle that apply to documentation as 3 | well. If you find yourself repeating the same content in multiple places, you 4 | should consider creating a custom snippet to keep your content in sync. 5 | -------------------------------------------------------------------------------- /style.css: -------------------------------------------------------------------------------- 1 | footer div:last-child a{ 2 | display: none; 3 | } 4 | 5 | th, td { 6 | border: 1px solid #ccc; /* 每个单元格的边框颜色为浅灰色 */ 7 | padding: 8px 12px !important; 8 | } 9 | 10 | th p, td p { 11 | margin: 0px !important; 12 | } 13 | -------------------------------------------------------------------------------- /theia/Developers/Open-APIs.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Open APIs' 3 | --- 4 | 5 | *This model is currently in its early stages and is not yet open to the public. If you want to experience it, please [click here](https://chainbase.com/contact) to apply and contact us.* 6 | -------------------------------------------------------------------------------- /theia/Resources/FAQs.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'FAQs' 3 | --- 4 | 5 | ## Coming soon -------------------------------------------------------------------------------- /theia/Resources/Roadmap.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Roadmap' 3 | --- 4 | 5 | Theia is the next-generation crypto world model that provides foundation knowledge and AI capability for the web3 era. To achieve this goal, the roadmap details the path to more intelligent, secure and transparent Theia model. 6 | 7 | ## Phase 1: Theia Demo Online 8 | 9 | 📅 June 20, 2024, 12:25:00 PM +UTC 10 | 11 | To let every crypto participator touch the crypto intelligence of Theia, we first open the interactive demo for Theia. It connects users with crypto knowledge in an exciting way - talk to Theia and get what you want. 12 | 13 | ## Phase 2: Theia Agent Ecosystem 14 | 15 | 📅 August 1, 2024, 12:25:00 PM +UTC 16 | 17 | **1. Knowledge Construction and Theia Expert Model (Agent)** 18 | 19 | We will create and expand the "Crypto Patterns" (i.e., expert and AI knowledge database) with community contributions and provide an interface to build Theia Agent Expert and any users can upload their own prompts (expert experiences) through this interface. Once reviewed by us, the agent can run on our model and interact with the Chainbase Network. 20 | 21 | **2. Marketplace** 22 | 23 | Open the marketplace for the agents built in Phase Two, allowing any Chainbase user to select specific agents from the marketplace to serve specific goals. 24 | 25 | ## Phase 3: Continuous Model Tuning and Patterns Accumulation 26 | 27 | To continuously increase the Theia intelligence, we will fine-tune our model periodically, and encourage the community to enrich the "crypto patterns". 28 | -------------------------------------------------------------------------------- /theia/Resources/Whitepaper.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Thesis' 3 | --- 4 | 5 | ## Coming soon -------------------------------------------------------------------------------- /theia/World_model/welcome.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Welcome' 3 | --- 4 | 5 | Chainbase is building an crypto world model, Theia, which is designed to learn blockchain data and realize simulation and reasoning of the native blockchain environment. Agents built based on it can effectively understand, predict and interact with the blockchain. 6 | 7 | Chainbase assembled a team led by a professor in the field of AI to build the model to support native crypto applications, including AI crypto games, DeFi, security, social, asset management, and more. 8 | 9 | ## What is Crypto World Model? 10 | 11 | The crypto world is built on massive and rapidly growing blockchain data, which contains an abundance of knowledge and underlying opportunities. Chainbase continually extracts, records, and organizes this data, summarizing it for downstream users. However, a significant and persistent challenge is that the vast "dark knowledge" within crypto data cannot be effectively organized solely through traditional databases and limited human effort. Accessing and interpreting this knowledge easily and conveniently remains a challenge for crypto participants. --------------------------------------------------------------------------------