πŸ’ΎFinality

In order to establish a reliable and consensus-driven infrastructure provisioning system within the Viper Network, the selection of a distributed, secure, and immutable database accessible to all participants is crucial. Therefore, the blockchain database structure, specifically the implementation of Tendermint Core, was chosen.

The security model of the Finality Storage layer revolves around the concept of Proof of Stake. Every registered Node in the network becomes part of a Validator Set, which enables a weighted, pseudo-random, deterministic selection for the role of Block Producer. The selected Block Producer is responsible for producing the next block in the chain. As each block is validated by every peer in the network, Block Producers have no incentive to produce invalid blocks. Any attempt to do so would result in punishment according to the applicable monetary policy and network protocol rules.

By utilizing Tendermint Core and implementing a robust Proof of Stake mechanism, Viper Network ensures the trustworthiness and reliability of its infrastructure, promoting a secure and consensus-driven environment for all participants.

Transactions

The Viper Network operates on a foundation where the Finality Storage serves as the authoritative and immutable record for all participants. It serves as the singular source of truth within the network. To contribute to this shared state, participants are required to submit transactions through a standardized and versioned interface to Nodes. These transactions are then propagated by the Nodes and ultimately incorporated into blocks by the Block Producers. To contribute to this shared state, participants engage in various types of transactions. These transaction types include:

  1. Staking Transaction:

  • Participants initiate staking transactions to solidify their engagement in the network, committing a specific token amount above 10000 in native tokens

  • This commitment establishes an active role, granting participants defined privileges and responsibilities within the network.

  1. Unstaking Transaction:

  • Conversely, unstaking transactions enable participants to reclaim their staked tokens when they choose to discontinue active participation after a lock-in period of 21 days.

  • This mechanism offers flexibility, allowing participants to manage their involvement in the network dynamically.

  1. Token Transfer Transaction:

  • This transaction type facilitates the smooth transfer of native tokens among network participants, fostering efficient peer-to-peer transactions.

  • Participants can securely exchange value within the network, contributing to the seamless functioning of the ecosystem.

  1. Report Card Transaction:

  • This transaction type is utilized at the conclusion of a session to generate a comprehensive report card by utilizing reliability, availability, and latency scores calculated for servicers.

  • The report includes the Merkle root of the of test results, ensuring the integrity and authenticity of the data.

  • Accompanied by a signature and a nonce to verify the legitimacy of the report, confirming it was generated by a valid Fisherman belonging to a specific session.

  • The transaction is submitted along with a Merkle proof and a pseudo-randomly selected leaf, which are later used in the "verify transaction".

  1. Commit Transaction:

  • Initiated by participants to assert ownership or rights over specific rewards by submitting a commit transaction for the work completed.

  • Generates a root for the proofs, serving as evidence of the completed tasks, and submits it to the chain.

  • Ensures participants can access their entitled benefits or holdings within the network, promoting fairness and transparency.

  1. Verify Transaction:

  • Involves retrieving both commit and report card data for a particular servicer within a specific session.

  • Generates the Merkle proofs and leaves for the commit and report card respectively and submits it to the chain.

  • The transaction is later handled by validating the Merkle proof against previously submitted Merkle roots of both the commit and report card, ensuring data consistency and integrity.

  • It then verifies the Fisherman's signature against the report and scores, ensuring authenticity and reliability and the client's signature against the proof of the relay.

  • Validators confirm the validity of the transaction, after which tokens are minted to the address of the servicer proportionally to the volume of relays served and the performance score.

  • Updates the global report card maintained for the servicer, reflecting the latest performance metrics.

Transaction Cost

In the Viper Network, transaction costs play a pivotal role in deterring spam and ensuring the judicious use of network resources. These costs are predefined and subject to adjustment through parameters set within the protocol, offering flexibility and adaptability to evolving network conditions. Managed through decentralized autonomous organization (DAO) governance, these parameters can be modified as needed, allowing for dynamic adjustments that align with the network's monetary policies and protocol guidelines. By imposing transaction costs, the network discourages excessive and frivolous transactions, promoting responsible behaviour among participants. Utilizing native cryptocurrency tokens to cover these costs ensures efficient resource allocation while reinforcing network integrity and stability. This mechanism not only maintains the integrity of the Finality Storage but also contributes to overall reliability and performance, enhancing the network's capacity to support its growing ecosystem.

Last updated