Website | Whitepaper | Lightpaper | Chat
Dispatch is a new distributed ledger protocol built on three core principles
● The Dispatch protocol is scalable.
Using our own DAPoS consensus, Dispatch achieves high transaction throughput, with no transaction fees.
● Dispatch is backwards-compatible with Ethereum smart-contracts and the Ethereum Virtual Machine (EVM).
Dispatch uses a modified version of the EVM, and is compatible with most Dapps currently under development.
● Dispatch handles lots of data.
Most business logic involves data too big to fit in a shared ledger. Dispatch extends the functionality of Ethereum smart-contracts to support big data access off-chain, what we now call artifacts.
Dispatch maximizes the customizable properties of Dapps on our chain, and will become the de-facto platform for Dapps.
Dispatch does not give developers strict rules. Encoding data as artifacts with smart-contracts allows developers to write their own logic per application, including their cryptography, data structures, access models, and more. Dispatch will allow storage and access to data, as well as integrated off-chain computation.
Storage and computation are the core elements of the Dispatch protocol, in order to be scalable and fast enough to handle the needs of any business.
Scalability
Dispatch enables companies to build data-intensive business logic on a public ledger without sacrificing speed or security. The Dispatch protocol uses Delegated Asynchronous Proof of Stake (DAPoS), a novel consensus algorithm, which handles orders of magnitude more transactions than most blockchains. DAPoS transactions are validated by elected delegates and recorded by elected learners. Valid transactions are gossipped. Invalid transactions are dropped. Unlike regular blockchains, where the tx/sec is bounded by tx/block x blocks/sec, DAPoS is bound by the hardware of the delegates and how fast they can validate transactions.
Delegated Asynchronous Proof of Stake
Dispatch enables companies to build data-intensive business logic on a public ledger without sacrificing speed or security. The Dispatch ledger is built with a new form of consensus called Delegated Asynchronous Proof-of-Stake (DAPoS) for both business and moral reasons. By migrating to a DAPoS mode of transaction validation, the costs associated with writing transactions to the blockchain fall dramatically. Transaction times can be brought down to nearly a single second, and unlike regular blockchains, where the tx/sec is bound by tx/block x blocks/sec, DAPoS is bound by the hardware of the delegates and how fast they can validate transactions. High throughput and low costs of DAPoS make the usability of Dapps much more practical for businesses. Additionally, DAPoS uses significantly less energy than traditional consensus methods.
The Dispatch Virtual Machine (DVM)
The Dispatch protocol is backwards compatible with Ethereum smart-contracts. The Dispatch Virtual Machine (DVM), is a modification of the EVM, built to support access to off-chain artifacts. The DVM allows the creation and execution of stateful programs using the ledger’s shared state, just like the EVM. The DVM adds artifact primitives and read/write opcodes to enable smart-contracts that support interactions with off-chain data. The DVM enables Dapp developers to build data-intensive business logic into smart-contracts.
The Dispatch Artifact Network
Off-chain data is stored with our network of farmers in the Dispatch Artifact Network (DAN). The DAN operates on a number of protocols like Kademlia DHT for Artifact discovery, Proof-of Replication (PoRep) to resist Sybil attacks, Proof-of-Retrievability (PoR) to ensure availability of Artifacts, and Make-it-Happen (MiH) protocol for efficient transfers of Artifacts.
Artifacts
Dispatch introduces a new class of information: Artifacts, stored in the DAN. The DAN is composed of uploaders, farmers, and downloaders, each with an identical copy of the shared ledger, but holding a various number of different artifacts. Below is a flow diagram of an Artifact’s life cycle.
The flow of a Dispatch Artifact starts when the uploader publishes a smart-contract containing a hash of the Artifact, and rules for accessing it (1). Hashing the file reduces the amount of data written to the shared ledger, and keeps the Artifact itself unknown to other nodes in the network. Rules for accessing the Artifact can be based on time, price, user group, oracles, etc. Once the smart contract is published to the shared ledger (2), anyone can request the Artifact from the uploader. Downloaders will know they received the right Artifact when the hash of what they received matches the one in the shared ledger.
Uploaders pay farmers to serve encrypted copies of their Artifacts (3) to service more downloaders, and to mitigate downtime. Farmers are compensated for their storage as well as their bandwidth. When a downloader wants an Artifact (4), they can check their Kademlia DHT (5) to find the closest available farmer (6). When downloading an encrypted Artifact from a farmer (7), the downloader will still need the much smaller encryption key from the uploader.
Specs:
DAPoS Consensus
Token name: Divvy
Tx speed: Incredibly fast (10,000+ transactions per-second in normal conditions. 100,000 TPS in perfect conditions)
No transaction fees
Roadmap:
Tokenomics:
Dispatch Tokens are the core currency of the Dispatch Network. They are the underlying economic value unit which allows interactions between Farmers, Uploaders, and Downloaders. 18bn Dispatch tokens will be minted.
Building on Dispatch
Several large projects are already building to transition to Dispatch at launch. As Dispatch’s DVM is backwards compatible with EVM, developers can start building their proof-of-concept on Ethereum before the mainnet launch of Dispatch.
The extended development roadmap includes an Ethereum to Dispatch smart-contract transfer tool. The tool will move the contract and its state to the more scalable Dispatch chain in a hard-fork fashion. Please contact our team if you are interested in building on or transitioning to Dispatch.
Official Channels:
|
Jump to:
|
