Merge pull request #113 from DataHighway-DHX/jeff/updateTable

Jeff/update table

MAINTENANCE.md

@@ -9,20 +9,26 @@ in the DataHighway Developer Hub).
 
 2. Updating diagrams
 
-Most of the original diagrams that are included in the original v1.0.0 whitepaper were generated with Visual Paradigm, whose source file is .vpd format, and then converted to an image that was stored in the ./assets/images folder and embedded in the generated whitepaper. However some of the diagrams were modified by the MXC marketing team, and these have been included in the updated version [v1.1.0 whitepaper](https://github.com/DataHighway-DHX/documentation/releases). Note that the latest version that has been released is stored into ./v1/whitepaper (at the time of writing it includes v1.1.0). If you need to update any of the diagrams then please coordinate with the MXC marketing team.
+Most of the original diagrams that are included in the original v1.0.0 whitepaper were generated with Visual Paradigm, whose source file is .vpd format, and then converted to an image that was stored in the ./assets/images folder and embedded in the generated whitepaper. However some of the diagrams were modified by the MXC marketing team, and these were included in previous version [v1.1.0 whitepaper](https://github.com/DataHighway-DHX/documentation/releases). If you need to update any of the diagrams then please coordinate with the MXC marketing team.
 
-3. Run the following to create a new release in PDF format. Replace `v1` below with the desired version:
+3. Run the following to create a new release in PDF format. Replace `v1.2.0` below with the desired version:
 
 ```
-nvm use v10.16.0
-npm i md-to-pdf &&
-mkdir ./v1 &&
+nvm use v10.16.0 &&
+npm install &&
 node ./node_modules/.bin/md-to-pdf ./docs/whitepaper.md \
   --config-file ./config.json \
-  ./v1/whitepaper.pdf
+  ./docs/whitepaper.pdf &&
+mkdir -p ./versions/v1.2.0 &&
+cp ./docs/whitepaper.pdf ./versions/v1.2.0/whitepaper.pdf
 ```
 
-Important: If you get an error, check if it actually generated the PDF changes correctly in either ./docs/whitepaper.pdf or ./v1/whitepaper.pdf, and use the one that worked.
+Note: It is important to use Node.js v10.16.0 and version simonhaenisch/md-to-pdf#v2.7.0 otherwise you will get an error like `ListrError: Something went wrong`). If there are issues running the following, then run `npm init &&
+npm install --save simonhaenisch/md-to-pdf#v2.7.0`.
+
+Important: Check it generated the latest PDF to reflect the Markdown changes you made correctly in ./docs/whitepaper.pdf and the copy of it ./versions/v1.2.0/whitepaper.pdf.
+
+External links may reference the static location of the latest whitepaper in ./docs/whitepaper.pdf. A copy of each version is stored in a directory with the version name to make it easier for users to find older versions. 
 
 Note: `headerIds` must be `true` in config.json otherwise TOC links do not work.
 

config.json

@@ -1,6 +1,6 @@
 {
   "stylesheet": [
-    "../style.css"
+    "./style.css"
   ],
   "css": "body { } .dh-logo-readme,.download-whitepaper { display: none; } .pdf-only { display: block; } .pretty-link-colored { font-weight: 400; color: #00aaff !important; }",
   "body_class": "markdown-body",

docs/whitepaper.md

@@ -27,11 +27,11 @@ page -->
 
 <div class="margin-sm"></div>
 
-<span class="language-options" style='font-style: italic;'><span class="download-whitepaper">Read this in other languages:</span> <a href="https://raw.githubusercontent.com/DataHighway-DHX/documentation/master/docs/whitepaper.md" class="download-whitepaper" style="font-weight: 400; color: #00aaff !important;">English</a> <a href="https://raw.githubusercontent.com/DataHighway-DHX/documentation/master/docs/whitepaper.ko.md" class="download-whitepaper pretty-link-colored">한국어</a> <a href="https://raw.githubusercontent.com/DataHighway-DHX/documentation/master/docs/whitepaper.ja.md" class="download-whitepaper pretty-link-colored">日本語</a> <a href="https://raw.githubusercontent.com/DataHighway-DHX/documentation/master/docs/whitepaper.zh-cn.md" class="download-whitepaper pretty-link-colored">简体中文</a> <a href="https://raw.githubusercontent.com/DataHighway-DHX/documentation/master/docs/whitepaper.zh-tw.md" class="download-whitepaper pretty-link-colored">正體中文</a></span>
+<span class="language-options" style='font-style: italic;'><span class="download-whitepaper">Read this in other languages:</span> <a href="https://raw.githubusercontent.com/DataHighway-DHX/documentation/master/docs/whitepaper.pdf" class="download-whitepaper" style="font-weight: 400; color: #00aaff !important;">English</a> <a href="https://raw.githubusercontent.com/DataHighway-DHX/documentation/master/docs/whitepaper.ko.md" class="download-whitepaper pretty-link-colored">한국어</a> <a href="https://raw.githubusercontent.com/DataHighway-DHX/documentation/master/docs/whitepaper.ja.md" class="download-whitepaper pretty-link-colored">日本語</a> <a href="https://raw.githubusercontent.com/DataHighway-DHX/documentation/master/docs/whitepaper.zh-cn.md" class="download-whitepaper pretty-link-colored">简体中文</a> <a href="https://raw.githubusercontent.com/DataHighway-DHX/documentation/master/docs/whitepaper.zh-tw.md" class="download-whitepaper pretty-link-colored">正體中文</a></span>
 <!-- https://en.wikipedia.org/wiki/List_of_ISO_639-2_codes -->
 <br />
 <span class="btn-download-wrapper">
-    <a href="https://raw.githubusercontent.com/DataHighway-DHX/documentation/master/v1/whitepaper.pdf" class="btn-download button-color-1">DOWNLOAD WHITEPAPER</a>
+    <a href="https://raw.githubusercontent.com/DataHighway-DHX/documentation/master/docs/whitepaper.pdf" class="btn-download button-color-1">DOWNLOAD WHITEPAPER</a>
 </span>
 <br /><br />
 
@@ -946,6 +946,50 @@ The DH's Cash Flow Statement reports for a period of time how changes in the Fin
 
 <div class="page-break"></div>
 
+#### Financial Procedures
+
+* DataHighway's Mainnet (Westlake) was launched in April 2021 to achieve the roadmap milestone date mentioned in the DataHighway Whitepaper.
+
+* DataHighway's Mainnet current assets include 30,000,000 DHX in the DHX DAO Treasury's Unlocked Reserves with hex 0x6d6f646c70792f74727372790000000000000000000000000000000000000000
+
+* DataHighway is currently using its Harbour Testnet to resolve Mainnet issues such as:
+	* Unusually large payouts to the initial validator set
+	* Removal of Sudo and replacement with on-chain DHX DAO governance
+
+* DataHighway currently supports Sudo. Sudo needs to be replaced with on-chain governance
+
+* DataHighway does not yet support on-chain governance required for the DHX DAO
+
+* Supernodes requested DHX tokens so they could distribute DHX tokens to their users that had participated in DHX Mining
+
+* DataHighway tested that Sudo transfers worked using Supernode accounts and appeared in the Subscan block explorer
+
+* DataHighway used the Sudo module to distribute the requested DHX tokens from the DHX DAO Treasury's Unlocked Reserves account to those Supernode accounts
+
+* Sudo was used to distribute DHX to Supernode accounts with these transactions:
+
+	* https://datahighway.subscan.io/extrinsic/665594-1
+	* https://datahighway.subscan.io/extrinsic/665623-1
+	* https://datahighway.subscan.io/extrinsic/665644-1
+	* https://datahighway.subscan.io/extrinsic/665661-1
+	* https://datahighway.subscan.io/extrinsic/665694-1
+	* https://datahighway.subscan.io/extrinsic/665713-1
+	* https://datahighway.subscan.io/extrinsic/665728-1
+
+* Supernode accounts refused to acknowledge receipt of the DHX tokens that were sent to them from the Treasury account using Sudo and they informed the DataHighway that the reason for this is because their systems do not support parsing Sudo transactions
+
+* DataHighway does not want to use Sudo any further without establishing a Multisig pallet. 
+
+* DataHighway's community-governed DHX DAO will need to decide via on-chain governance whether to flag those funds as lost or whether to fork the DataHighway blockchain if the relevant Supernodes decide not to return the DHX tokens to the Treasury account. In the interim the DHX DAO will add those transactions as Liabilites in its Financial Model. In the future the DHX DAO would need to add to its Liabilities reimbursing the transaction fee to the relevant Supernodes when they return the tokens. DataHighway is of the understanding that Supernodes should be able to return DHX tokens to the Treasury independent of whether their systems support parsing Sudo transactions. 
+
+* DataHighway would need to send DHX tokens to Supernode accounts via a Proxy account from the Treasury account for them to recognise the transactions. The Proxy account must be controlled via a Multisig.
+
+* DataHighway is currently of the understanding that the DHX token is a cryptocurrency like BTC or DAI and is therefore neither a security or utility token. Since the DataHighway's on-chain governance has not yet been tested as being ready to be used, human involvement with Sudo is necessary to move the project forward. 
+
+* DataHighway is actually capable of executing on-chain governance, so it may already be considered a DAO to an extent that has no registered offices, directors or employees, and it may not even be recognised as its own legal person. The DHX DAO's human involvement should become limited as the DHX DAO's operation, management and control becomes automated, and decisions are by on-chain voting. Since it may be considered a DAO it has been recognised by the DataHighway that the DHX token may trigger securities regulations and laws. DataHighway is contacting legal firms that have have prior DAO experience since in when Sudo is removed the DHX token holders will be controlling minutes and approving decisions of the DAOs' operations.
+
+<div class="page-break"></div>
+
 ## Mining
 
 ### Benefits