Skip to content
Validator Network Permissioning Decentralised Application
JavaScript CSS HTML Makefile Dockerfile
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
public
src
.gitignore
Dockerfile
LICENSE
Makefile
README.md
package-lock.json
package.json
readme.md
setupTests.js
truffle.js

README.md

Validator Dapp on the live network Autonity network

drawing

To run the application

Clone the repo

  • install Metamask and create an account
  • press the icon of the current network name and choose Custom RPC
  • add the RPC endpoint for your Autonity network to the new RPC URL field and press Save
  • npm install
  • npm start

Please note: MetaMask is having issues running on Firefox. This bug was reported back in August and we're awaiting a fix. Until then please use Chrome.

The frontend will load on http://localhost:3000/

Validator: General

A network needs at least four validators to function properly and the Autonity network needs a deployed governance contract. The validator governance is based on the Soma contract.

The Validator DApp has many similarities with how the Observer DApp is implemented and their underlying smart contracts. The Observer is based on a P2P permissioning contract (Glienicke) while the Validator contract is aimed to govern validators.

The similarities and differences of these two network permissioning contracts can be summarised as follows:

Similarities

  • Both are smart-contract based permission contracts with functions to add and remove nodes
  • Both implement an interface which makes it possible to use a custom protocol
  • Both implement an interface which allows or denies a peer connection to a network

Differences

  • Glienicke is the initial permissioning for a peer to participate and interact with a network
  • Soma is permissioning for peers to participate in the consensus mechanism
  • An observer node (in the Glienicke set) isn't necessary a validator (in the Soma set) but a validator is always an observer (if a node is in the Soma set it is also in the Glienicke set)

Validator: Main components

The main two functions are: (1) add a Validator and (2) remove an existing Validator. In both cases, the identifier used is the enode address. These are found in Validators.js. By utilising either function, Metamask is triggered and brings the user to the payment window.

In the validator contract (Soma.json), the network address can be found. Note that the network addresses for the Observer and Validator DApp are distinct.

Validator: Miscellaneous

Interactions with smart contracts are facilitated with the library Drizzle to make it easer to write DApp UIs. The loading button (and other alternatives) can be found at loading.io.

You can’t perform that action at this time.