DAST CHAIN

DAST architecture is based on a combined consensus algorithm and a scalable architecture without the use of sharding to ensure highest speeds without any loss in security.

The backend of the network consists of nodes that can be builders, validators and witnesses. All the nodes are randomly selected each session for a task, so any node can be a builder, validator or witness, depending on the session label it receives.

To ensure the highest level of security, a minimum of 143 nodes are required to be active at all times. This will allow an unbreakable pool of nodes to choose from for the current session, and will also allow idle nodes to exchange validated block hash and headers, keeping an index of blocks, positions and locations.

The network also consists of 23 servers that are used for frontend, services, aggregation, hooks, data, leverage, atomic routes, messaging routes.

The servers use DAST Chain technology to interact with DAST Chain, but are not part of the network and do not influence the node network in any way. They are a data aggregator and convertor, to prepare blockchain data for usage and to make it readable.

Data in the DAST Chain is stored in multiple outer/inner index versioned and timestamped databases that sync across the nodes and a versioned indexes database that holds all indexes and is replicating on all existing nodes.

OIIVT databases replicate on block generation on the nodes that hold governance for the current session, and replicate to all the other nodes on Idle Time Notification (ITN).

Replication on ITN ensures resource planning stability and does not interfere with current session block generation, thus decreasing the systems load and used resources.

ITN is a timeframe notification sent by idle nodes. Nodes and their resources are used for block generation only when selected for governance.

VI database has a version number consisting of an unsigned 64-bit integer. At each version i, the database contains (iS_i, S_i, I_i) representing initial ledger state iS, last ledger state S and index id I.

Validators can respond to client queries about the ledger history at both current and previous versions and can query a ledger state.

DAST Chain uses the DAST Protocol. A set of links between VI, OIIVT and event blocks form a DAG based on the DAST Protocol. Event blocks contain information on session events, index IDs of previous events and timestamps.

Current RPoS (Reputation Proof of Stake) tagged node can manipulate the VI and arrange indexes based on timestamps.

Witnesses and validators check for authentication on events and for identical transactions. If identical transactions are detected, the one with the smallest timestamp is validated. Event order is arranged by builders.

Also, current RPoS tagged nodes can generate new sidechannels or payment channels, depending on the user’s request.

Sidechannels and payment channels handle multiple transactions before adding the final result to the main blockchain. They are tagged depending on their usage and consensus template for each sidechain and payment channel is applied reading the same tag smart contract.