Skip to main content

Technical Architecture

Cuptobit’s vision is to solve the Web3 Data Gap is a configurable data framework that allows for

  • Democratically creating and managing network system entities
  • Service level agreement (SLA) between the providers and consumers of data
  • Multi-level network data agglomeration allowing to balance security, authenticity, persistency, and speed
  • Democratization of the data management process
  • Transparency and traceability of data provenance
  • Free data market
  • A voting system allows for assessing and strengthening the validity of a vote.

Solutions​

To actualize the envisioned future of bridging the Web3 chasm, the Cuptobit network is building a number of components that make up the DeData infrastructure. This includes

  • The Cuptobit Network Pallet & API

  • Dynamically & Statically Sized networks

  • Democracy Pallet

  • An Enhanced Voting System

  • Dynamic NFTs & Data Marketplace.

  • The Cuptobit Network Pallet & API

The Cuptobit Network nodes are validated by the blockchain bridge to network. Our API allows us to save to a Postgres database the results of calls to built-in or custom endpoints.

The aim of Cyptobit Network is to create a configurable network to give users a sense of assurance and responsibility to the consumer about selected choices. The creators of a data feed of the network can specify what their networks are and which algorithms they are using so the consumers of this feed can freely choose if they want to consume the data with the full knowledge of their choice. Systemizing knowledge and dividing networks into modules can enhance security and manage user expectancies.

Network System Manifest​

Given that the Cyptobit Network will be a Multi-level network Data agglomeration, a procedure is required to keep track of ownership, source of data, and other pertinent information. Keeping track of who owns the data, where the data comes from, when it was collected, and which algorithm was used to treat it can be recorded in this manifest that can be published with each block. This implies that the data sources are known before the feed is published in the primary network.