Dappy specifications
  • Introduction
  • Specs and web standards
    • Name system
    • Authorized characters for names / IDNA
  • Sections specific to browser and web applications
    • Cookies
    • Cross-origin resource sharing (CORS)
    • TLS / encrypted traffic only and HSTS
    • Content Security Policy (CSP)
  • Glossary
    • Dappy Network and network members (or agents)
    • Co-resolution
    • Dappy protocol
    • Dappy browser
    • Traditional or regular web browsers
    • IP application
    • Dapp
Powered by GitBook
On this page

Was this helpful?

  1. Glossary

Co-resolution

PreviousDappy Network and network members (or agents)NextDappy protocol

Last updated 3 years ago

Was this helpful?

A co-resolution (or multi-request, or trustless lookup mechanism) is the operation that a client performs when he queries at least two members of a given Dappy network to read something from the blockchain. It is the main operation at the core of the dappy paradigm.

By doing a multi-request instead of a unique client-server request, a client is able to read from a public database that he does not have locally (the state of a blockchain), without having to trust any single entity. Multi-requests in Dappy are a sort of trustless remote database query mechanism.

When a client receives response from a multi-request (ex: AAAAABA), he can apply arbitrary consensus rules to accept or reject the result (sometimes called synchrony constraints also). The client may require 100%, 90% or 80% of identical responses. He may also require that a maximum of 2 groups of different answers.

Example: In all releases of dappy, the list of the names is recovered by asking all the members of the Dappy network and requiring 100% accuracy (all the responses must be the same).

The library is currently the library that handles the co-resolution and reconciliation, it is used by dappy browser (web browser) and dappy lookup (node JS).

bees JS