In order to limit the time span in which a document can be altered (modified or removed), Diavgeia will be forced to store a log in the Bitcoin Network, at predefined time intervals. It is obvious that smaller time intervals imply more transparency, as the government keeps more logs. That said, let’s assume Diavgeia is forced to keep a log each day. The following procedure takes place:

  1. Diavgeia gathers all .n3 decisions that have not been included in the last log. These documents are organized into a Merkle Tree.
  2. Diavgeia gets the root of the Merkle tree and signs it. Diavgeia commits the signed root of the Merkle Tree as proof of burn transaction to the Bitcoin Network.
  3. After the confirmation of the transaction, it publishes:
    • The merkle tree (that is the order of the documents). This is crucial, because citizens should be able to verify that the root of the merkle tree is valid.
    • The Bitcoin Address / transaction.

Then, citizens and government institutions can verify their acts and be sure that their decisions will remain immutable over time.

Diavgeia Redefined implements a Hierarchical Deterministic wallet and that means that for each proof of burn transaction, a new public address will be generated. Thus, Diavgeia should also publish once its Master Public Key in its website, as citizens should be able to track every single transaction that is made.

For installation instructions and more information, see this github link.