A New Mental Model for Web3

All blockchain technologies can be grouped into two segments.

Segment 1: Blockchains are State Machines

Blockchains are deterministic finite state automata, which know only their current state, an acceptable set of states, and the state transition function. A blockchain's entire state is contained as its ledger.

Segment 2: Everything else is a Data Abstraction

To expand blockchain capabilities (and enable DeFi, DeSci, GameFi), we employ intermediaries like bridges, oracles, and indexers. These trusted intermediaries manage nondeterministic data processes that a deterministic state machine cannot.

For any action in web3 beyond state transition, users and builders must choose from the intermediaries available, accept the outlined constraints of their specialized process, adopt their tenants, and pay their toll.

i.e. Bridges bring transaction data cross-chain. You must accept their version of synthetic, wrapped, or minted tokens, trust their security, and pay their fee.

Concordance Solves for Data Abstraction

We propose Convoy; a new protocol for arbitrary data abstraction.

This protocol removes intermediaries who facilitate processes of data abstraction, and allow for both objective and subjective data-dependent applications to run fully on-chain.

How

We abstract data through an interface, for any arbitrary data processes. Users and builders can define their own on-chain processes.

Our protocol optimizes data compression, and secure package transfer, and enables responsive I/O from the client.

Why

Blockchain shouldn't be an afterthought in application design.

We build with blockchain integration in mind.

Developers need tools, not constraints, to develop the best blockchain-based technology possible.

Developers should focus on enabling the solutions they want using blockchain instead of fighting with infrastructure, compromising on the features they can create, or making appchains, sidechains, or rollups that fragment liquidity and compromise strong security.

Blockchain should be trustless.

The core of web3 is permissionless, trustless compute.

Developers should not have to rely on intermediaries to facilitate transactions.

Give users transparency and control over their data.

Users should know what happens to their data when they provide it as required on the internet.