Comparison with Other Projects
Curious readers may wonder about the differences between Band Protocol and other oracle projects available in the market. We cover the major points in this section.
This information is based on whitepapers and publicly available materials. If you are a developer working on one of the projects and would like to provide direct feedback, please reach out to us at email@example.com.
|Intuitive & Instant query processing|
|No third party point of failure|
|Payment in native currency|
|Support multiple data types|
|Dedicated token for each data type|
|Support multiple blockchains|
Decentralized Oracle: Whether the protocol is decentralized and permissionless. An open protocol must allow Anyone to participate in data provision through a transparant rule and there must be an open market for data providers driven by token economics.
Intuitive and Instance Query Processing: Whether a data query to the protocol is intuitive and instant. Querying data should be as simple as a cross-contract function call that returns data within the same transaction. Several protocols use callback approach, which is both complicated to interact and adds delay that hurts user experience.
No Third Party Point of Failure: Whether the protocol is designed to function without reliance on third party services (such as CoinMarketCap or CryptoCompare for price feeds).
Payment in Native Currency: Whether data consumers can pay in platform's native token (ETH in case of Ether) or must use the protocol's native token. Using protocol native token, while creates a use case for token, may hinder network adoption since the consumers must maintain another token in their ecosystems.
Support Multiple Data Types: Whether the protocol is designed to support more than just one specific type of data.
Dedicated Token for Each Data Type: Whether the protocol has an indepedent token for each different data type. Having dedicated tokens helps aligned the incentive of all token holders to curate good data and makes bribing more difficult since bad dataset is strictly tied to token value.
Support Multiple Blockchains: Whether the protocol is fundamentally designed to run mutually on multiple blockchains, with economic design to bolster security across those chains.