Note that signallying is where user does not have to lock their tokens for a period of time to discourage monopolization, they just have to indicate that they have the tokens and we will sample them over the period.

I just tried to join the linked discord https://discordapp.com/invite/t3mQAZ, but only got 'invitation invalid'.
Perhaps it expired?

Update: just found a working link https://discordapp.com/invite/KGTbv9Z under https://dev.datahighway.com/docs/en/whitepaper#questions
Is this the correct one? Should I update via pr?

Fix issue that was raised in the old repo https://github.com/DataHighway-DHX/whitepaper/issues/2

Currently the link to "Download Whitepaper" is ugly plain text and doesn't incentivize users to click it as a call to action should

Fix issue that was raised in old repo https://github.com/DataHighway-DHX/whitepaper/issues/5

Reference: https://mxc.atlassian.net/browse/MMD-1279

Reference https://anaelleltd.github.io/polkadotjs-guide/4.governance.html#content

DHX-165

See below screenshot, the two buttons don't wrap to next line on large screen sizes. It should wrap like it does on mxc.wiki

• Fix so it no longer sends the generated docs to website/translated_docs/, as currently in this PR #97 is automated from Crowdin using Jeff's account and is currently generating the following (where is either ja, ko, zh-CN, zh-TW):
  website/translated_docs//getting_started/...
  website/translated_docs//tutorials/...
• Delete PR #97
• Modify the crowdin.yml configuration
• Create a specific Github account for the Crowdin integration so it doesn't go through Jeff's account

References:

• https://docusaurus.io/docs/i18n/crowdin
• https://mxc.atlassian.net/browse/MMD-1278

It's shown both here:

https://dev.datahighway.com/docs/en/whitepaper#financial-procedures

and here:

https://dev.datahighway.com/docs/en/whitepaper#financial-procedures-1

Reference
https://mxc.atlassian.net/browse/MMD-1288
https://mxc.atlassian.net/browse/MMD-906

Fix issue that was raised in old repo https://github.com/DataHighway-DHX/whitepaper/issues/6

Fix issue that was raised in old repo https://github.com/DataHighway-DHX/whitepaper/issues/4

In order for the Docusaurus-generated Table of Contents to turn into a hamburger menu on smaller viewports as shown below, it is necessary to show the left sidebar, but doing so takes up a lot of space on the left side of the screen.

So we need to figure out how to apply styles only to a specific page (the "Whitepaper" page only).
Since we're using Docusaurus, which generates static sites, we don't have access to the window object to conditionally apply styles depending on the current page.

A solution is that we can actually use the HTML <style> tag in specific Markdown files, where we can use media queries to only hide the left sidebar on that Whitepaper page on larger screensizes, but not on smaller screen sizes since we need it in the DOM so we can show the hamburger menu, and we also don't want to hide the left sidebar on any other page.

Fix issue that was raised in the old repo https://github.com/DataHighway-DHX/whitepaper/issues/10

Source:

• assets/imagesdiagram-datahighway-ux-sketch.jpg

Original Visual Paradigm Source:

• visualization_brainstorm

Fix this issue that was raised in the old repo https://github.com/DataHighway-DHX/whitepaper/issues/7

404 - Not Found

• [d7d9a7] LoRaWAN Backend Interface Specification
• [7c63ac] MXC's Data Economy Whitepaper
• [c63390] MXC SMB Whitepaper
• [b26ba7] Aura
• [7fd55a] NPoS
• [0ec873] Substrate Executing Privileged Functions
• [fa094e] Polkadot Token Economics Payment Details
• [903282] Parity Proof of Authority (PoA) Chains
• [b05a57] Polkadot Token Economics Relay Chain Transaction Fees

Only accessible with permission

• [6fe50e] MXC Roaming Presentation by Aslan on 6th August 2019 including Activation Passive Roaming

Styles such as pdf-only were applied to the whitepaper.md file, and they hid the title and TOC in development, since they were only intended for the PDF version of the whitepaper that is generated, but in production they are not hidden for some reason (see https://dev.datahighway.com/docs/whitepaper).

Also, other aspects that should be appearing on the documentation website whitepaper such as submit-issue image are not appearing despite the CSS logic

Generate visualizations for DAO UI based on on-chain data, since the data that will be originally configured based on the tables in this issue https://github.com/DataHighway-DHX/whitepaper/issues/6 will be dynamically modified by DAO participants

Fix issue that was raised in the old repo https://github.com/DataHighway-DHX/whitepaper/issues/9

Fix issue that was raised in old repo https://github.com/DataHighway-DHX/whitepaper/issues/8

start command：./target/release/datahighway --bootnodes /ip4/3.67.117.245/tcp/30333/p2p/12D3KooWKS7jU8ti7S5PDqCNWEj692eUSK3DLssHNwTQsto9ynVo --name "Node yjcc.pro" --chain ./chain_def_dev.json

error：Error: Input("Error parsing spec file: unknown field codeSubstitutes at line 167 column 1")

Extension of #19.
If the link isn't in the References or Appendices section, then instead of it showing the hyperlink address as the text that is shown, show a descriptive name for the link that explains where clicking the link will take the user.

Change all links in the docs/whitepaper.md i.e.[]() to HTML i.e. <a href="<LINK_ADDRESS>" target="_blank" class="pretty-link-colored"><LINK_NAME></a> so it appears coloured when you view the whitepaper in your browser. Only use target="_blank" for external links (i.e. http://test.com, but for anchor tags that are links to sections within the whitepaper (#MyLink) we actually want to remove target="_blank".)