See it in action: DIVA Testnet
This is a Blockchain implementation using Practical Byzantine Fault Tolerance (PBFT) in combination with Proof-of-Stake (PoS) as a consensus algorithm. It is therefore a "Weighted Practical Byzantine Fault Tolerance" consensus.
This is a fully anonymous ("Privacy-By-Design"), very lightweight, fast, low-energy and permissionless blockchain.
The load of the PBFT consensus is network bound. The chain gets built by "communication" instead of "computation". Therefore many messages are crossing the network.
The peers in the network communicate over I2P. 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.
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 proposal: each peer in the network may anytime propose a transaction, by sending it to the network. Per round, each peer can only add one own transaction.
- Voting: each peer receiving a proposal may send a vote to the network. Such a vote represents an agreement of a peer with a specific stack of proposals. Each peer can vote only once per stack.
- Creation of a new block: as soon as consensus (2/3 of the network peers) is reached through voting for a specific stack of proposals, peers will create the new block.
Divachain supports two API's: a) an HTTP REST API running by default on port 17468 b) a broadcasting websocket running by default on port 17468
In a nutshell: use the REST API to write transaction proposals to the chain or use the REST API to read status information from the chain. Use the websocket to get live updates.
To create a docker based local environment use the project https://github.com/diva-exchange/diva-dockerized.
The configuration can be controlled using environment variables.
Set to 1 to skip bootstrapping.
Default: 0
URL to a entrypoint in the network, like http://diva.i2p.
Default: (empty)
Default: 127.0.0.1
Default: 17468 REST API as documented below (API Endpoints).
Default: 17469 Websocket Feed, broadcasting block data to its listeners.
Default: IP
Default: 4445
Default: IP
Default: 7656
Default: as IP above
Default: 7656
Default: 7655
Default: 127.0.0.1
Default: 17468
Default: 127.0.0.1
Default: 17470
Default: 127.0.0.1
Default: I2P_SAM_LISTEN_UDP_PORT
Interval, in milliseconds, to build and maintain the P2P the network (connect to peers, if needed).
Minimum: 1000
Maximum: 30000
Default: Minimum
Minimum: 1000
Maximum: 60000
Default: 5000
Maximum number of blocks of synchronization message might contain. Must not exceed API_MAX_QUERY_SIZE.
Minimum: 10
Maximum: 100
Default: Minimum
Number of blocks kept in memory (cache).
Minimum: 100
Maximum: 1000
Default: Maximum
Number of blocks which can be queried through the API.
Minimum: 10
Maximum: 100
Default: Maximum
Returns an object containing the version, the license and the public key of the peer.
Returns the network participants. If stake is given and greater than zero, only network participants with a stake greater-or-equal than the given threshold will be returned.
Search states using a search string. If no search string is given, it returns the last API_MAX_QUERY_SIZE states.
Example: http://url-divachain-api/state/search/DivaExchange:OrderBook:BTC_ETH
Remark: Not more than API_MAX_QUERY_SIZE states can be requested at once.
Get a specific state from the local state database. The local state database is a key/values storage and represents a well-defined set of current states.
Example: http://url-divachain-api/state/decision:DivaExchange:Auction:BTC_ETH
Get the stack (queue) of local transactions.
Get the current transactions in the pool.
Get the current votes in the pool.
Get the genesis block.
Get the latest block on the chain.
Get a specific block on the given height.
Example: http://url-divachain-api/block/10 will return the block on height 10.
Error handling: If a block is not yet available, 404 (Not Found) will be returned.
Get all blocks between height "from" (inclusive) and height "to" (inclusive). If "to" is not yet available, the blocks until the current height will be returned.
Example: http://url-divachain-api/blocks/10/19/ will return 10 blocks (block 10 until 19, if all blocks are already available).
Example: http://url-divachain-api/blocks will return the latest API_MAX_QUERY_SIZE blocks (at most).
Error handling: 404 (Not Found) will be returned.
Remark: Not more than API_MAX_QUERY_SIZE blocks can be requested at once.
Get a specific page of the blockchain, starting at the current height (reverse order). If size is not given, it will return API_MAX_QUERY_SIZE blocks or less.
Example: http://url-divachain-api/blocks/page/1/5 will return the last 5 or less blocks of the chain.
Remark: Not more than API_MAX_QUERY_SIZE blocks can be requested at once.
Search blocks using a search string. If no search string is given, it returns the last API_MAX_QUERY_SIZE blocks.
Example: http://url-divachain-api/blocks/search/XMR will return the latest blocks containing the string XMR.
Remark: Not more than API_MAX_QUERY_SIZE blocks can be requested at once.
Get a well-defined transaction.
Error handling: 404 (Not Found) will be returned if the transaction is not available.
Submit a new transaction proposal to the network. The body must contain an array of commands.
Example of such a transaction proposal, containing two commands:
[
{ seq: 1, command: 'data', ns: 'test:data', d: 'data-1' },
{ seq: 2, command: 'data', ns: 'test:data', d: 'data-2' },
]
Internal: part of an automated process.
Request to join the network.
Send this GET request to any remote peer in the network which is online. This remote peer will later - in some seconds or even minutes - send back an independent GET request to the local /challenge/ endpoint.
Internal: part of an automated process.
TBD.
Internal: part of an automated process.
Response will contain the signed token. Verify the response with the public key of the remote peer.
This endpoint is part of an automated process.
Get a well-defined number of blocks starting from {height} (including). See NETWORK_SYNC_SIZE.
If a local I2P test environment is wanted, start the local testnet container:
docker-compose -f test/local-i2p-testnet.yml up -d
Unit tests can be executed using:
npm run test
Unit tests contain functional tests and will create some blocks within the local storage.
To stop the local I2P test environment (and purge all data):
docker-compose -f test/local-i2p-testnet.yml down --volumes
To lint the code, use
npm run lint
On DIVA.EXCHANGE you'll find various options to get in touch with the team.
Talk to us via Telegram (English or German).
Your donation goes entirely to the project. Your donation makes the development of DIVA.EXCHANGE faster.
XMR: 42QLvHvkc9bahHadQfEzuJJx4ZHnGhQzBXa8C9H3c472diEvVRzevwpN7VAUpCPePCiDhehH4BAWh8kYicoSxpusMmhfwgx
BTC: 3Ebuzhsbs6DrUQuwvMu722LhD8cNfhG1gs
Awesome, thank you!