||2 days ago|
|bin||4 days ago|
|blockstore||2 months ago|
|dist||2 months ago|
|docker||2 days ago|
|genesis||2 weeks ago|
|keys||3 weeks ago|
|log||2 months ago|
|src||2 days ago|
|state||4 weeks ago|
|test||4 days ago|
|test-performance||2 days ago|
|.editorconfig||2 months ago|
|.eslintrc.json||2 months ago|
|.gitignore||2 months ago|
|.mocharc.json||2 months ago|
|.nycrc.json||2 months ago|
|.prettierrc.json||2 months ago|
|CODE_OF_CONDUCT.md||2 months ago|
|LICENSE||2 months ago|
|README.md||2 days ago|
|package-lock.json||2 days ago|
|package.json||2 days ago|
|tsconfig.json||4 weeks ago|
A blockchain implementation using PBFT (practical byzantine fault tolerance) as a consensus algorithm.
This is a fully anonymous ("Privacy-By-Design"), very lightweight, fast, low-energy and permissionless blockchain.
A PBFT consensus is very much network bound. The chain gets built by "communication" instead of "computation". Therefore lots of messages are crossing the network.
The peers in the network communicate via websockets. The peers build the tunnels between each other using a secure and efficient "Challenge/Auth" process based on regular asymmetric keys (public/private keys). "Sodium" gets used as the single crypto library - so all crypto-related code is based on solid, very well tested and proven code.
Architecture / Flow
The network itself is permission- and leaderless. Each peer in the network represents a round-based state machine. Each round produces a block. The blocks do have a variable size and blocks are produced on demand.
- New block proposal: each peer in the network may anytime propose a bundle of transactions, by transmitting 1-n own signed transactions to the network.
- Each peer receiving such a proposal may transmit its vote to the network. If a peer also has own transactions it adds his own transactions to the proposal first and re-transmits the proposal to the network. Per round, each peer can only add one stack of own transactions.
- As soon as a peer in the network detects that 2/3 of the whole network have voted for a specific proposal, it issues a commit message and broadcasts it to the network.
- As soon as 2/3 of the network have issued commit messages, peers starting to issue confirm messages. The new block gets written to the chain.
- A new round starts.
Create Your Local Environment
Important: docker-compose (>v1.24.1) is required. Check with
To create a meaningful local environment, several divachain nodes must be created and started. This is done by creating your local docker-compose file.
To create a basic local docker-compose YML file and a matching genesis block (JSON), use
After the script has been executed, the created YML file is located here:
and the corresponding genesis block (JSON) is located here:
Now you can start your local environment:
sudo docker-compose -f docker/build/build-testnet.yml up -d
Afterwards the default number of divachain nodes will be started, check this by using:
sudo docker ps
Access the local API of any divachain node, like:
The local IP address
172.20.72.151 is the default IP address of the first node (see created YML file). Use environment variables during the build process to change the default values.
To stop your local environment, use:
sudo docker-compose -f docker/build/build-testnet.yml down
To stop and purge all data within your local environment, use:
sudo docker-compose -f docker/build/build-testnet.yml down --volumes
Create an I2P-based Local Environment
To create an I2P-based local docker-compose YML file, use
The script needs elevated privileges, since it needs to start I2P docker containers. Therefore the script will ask for the root password.
The script creates - same procedure as above - a YML file including all I2P containers and the applicable genesis block.
Start and stop the environment using docker-compose (see above).
Important: if the volumes are purged, the environment must be rebuilt!
The configuration can be controlled using environment variables.
Maximum number of blocks kept in memory.
Between 7 and 64 peers.
Between 2 minutes and 10 minutes (120'000ms and 600'000ms).
Interval, in milliseconds, to refresh the network (connect to peers, if needed).
Default: 5 * NETWORK_REFRESH_INTERVAL_MS
Timeout, in milliseconds, after authorisation fails.
Interval, in milliseconds, to ping the peers in the network.
Default: 2 * NETWORK_SIZE * NETWORK_PING_INTERVAL_MS
Interval, in milliseconds, to clean up the network environment (like gossiping data).
Number of blocks a blockchain can get behind before synchronisation is triggered.
Default: 10 Maximum number of blocks of synchronization message might contain. Must not exceed NETWORK_MAX_BLOCKS_IN_MEMORY.
Whether to log all network traffic (very verbose). Set to 1 to enable verbose logging.
Interval, in milliseconds, to check whether the block pool is stale.
How to Run Unit Tests
Unit tests can be executed using:
npm run test
Unit tests contain functional tests and will create some blocks within the local storage. The underlying network (like I2P) must be configured properly (the configuration is Work-In-Progress).
To lint the code, use
npm run lint
Contact the Developers
On DIVA.EXCHANGE you'll find various options to get in touch with the team.
Talk to us via Telegram https://t.me/diva_exchange_chat_de (English or German).
Your donation goes entirely to the project. Your donation makes the development of DIVA.EXCHANGE faster.
Awesome, thank you!