fixing broken links

ergoplatform · Dec 28, 2022 · 5cddbac · 5cddbac
1 parent 5fae199
commit 5cddbac
Show file tree

Hide file tree

Showing 8 changed files with 23 additions and 22 deletions.
diff --git a/README.md b/README.md
@@ -27,11 +27,11 @@ mkdocs serve
 - Finish moving over ErgoTree specification
 - (BUG) Syntax Highlighting not working
 - (BUG) Python in multi-code selector boxes seems to have broken. 
-- (BUG) LaTex commands need refresh to work sometimes. (Preload in Mathjax.js)
-- Flesh out & tidy Apps & Use Cases section (new title?)
-  - P2P
+- [x] (BUG) LaTex commands need refresh to work sometimes. (Preload in Mathjax.js)
+- [x] Flesh out & tidy Apps & Use Cases section (new title?)
 - Split and tidy scaling page
 - Move more research papers into markdown so they're indexed and searchable. 
 - Transfer over any remaining information from ergonaut.space
 - Missing text bottom of modes of operation
-- Tidy Light Nodes page (on learn the basics)
+- Tidy Light Nodes page (on learn the basics)
+
diff --git a/docs/dev/lib/eip12-types.md b/docs/dev/lib/eip12-types.md
@@ -1,3 +1,3 @@
 # EIP12-Types
 
-https://github.com/capt-nemo429/eip12-types
+[EIP12-Types](https://github.com/capt-nemo429/eip12-types) is a static typing library for Ergo Blockchain's dApp Connector Protocol.
diff --git a/docs/dev/protocol/nipopow/nipopow_nodes.md b/docs/dev/protocol/nipopow/nipopow_nodes.md
@@ -3,7 +3,7 @@ tags:
   - NIPoPoWs
 ---
 
-# Light Nodes
+# Light Clients
 
 **Light Clients** are essential when considering the hurdles cryptocurrency faces with mass adoption. Most crypto users do not have the necessary tools to run a full node. Running a full node means having a strong processor, electricity costs, and potentially hundreds of gigabytes of memory to store the entire blockchain. 
 

diff --git a/docs/dev/protocol/zkp.md b/docs/dev/protocol/zkp.md
@@ -16,29 +16,28 @@ In cryptography, most practical problems are associated with secrets. The most p
 
 ## Sigma Protocols
 
-Among the hundreds or even thousands of zero-knowledge protocols, there is a sub-class of efficient and composable proof-of-knowledge protocols called **Sigma Protocols** (Σ-Protocols or *Generalized Schnorr Proofs*).
+Among the hundreds or even thousands of zero-knowledge protocols, there is a sub-class of efficient and composable proof-of-knowledge protocols called [**Sigma Protocols**](sigma.md) (Σ-Protocols or *Generalized Schnorr Proofs*).
 
-[ErgoScript](ergoscript.md) is the language used to specify the conditions under which currency can be spent. The language supports a type of non-interactive zero-knowledge proof called [Σ-protocols](sigma.md). It is flexible enough to allow for ring signatures, multi-signatures, multiple currencies, atomic swaps, self-replicating scripts, and long-term computation.
+> [ErgoScript](ergoscript.md) is the language used to specify the conditions under which currency can be spent. It is flexible enough to allow for ring signatures, multi-signatures, multiple currencies, atomic swaps, self-replicating scripts, and long-term computation.
 
-The two Sigma Protocols right now are proof of discrete log and proof of Diffie-Hellman tuple
+The two Sigma Protocols right now are [proof of discrete log](schnorr.md) and proof of [Diffie-Hellman tuple](diffie.md).
 
 
-## 'Optional' Privacy?
+These composable proofs enable some very strong use cases combined with a blockchain. The logic for proofs can include conditions based on the blockchain state. For example, 'If the deadline block height has been reached, Alice can provide knowledge of a secret key for a refund. OR a ring signature from Alice and Bob is required to spend coins.' Or 'If this account holds a minimum of 100 ERG, Alice OR Bob can remove funds above that amount.'
 
-A rich smart-contract language is a priority in Ergo, and with non-optional privacy, you can't have (efficient) powerful contracts. Even more, for simple payments, formalising leakage is hard, and for arbitrary contracts simply not feasible.
+Swapping coins or custom tokens trustlessly across any Bitcoin-like blockchain is relatively easy. But beyond that, Ergo allows partial swaps. Like on a regular exchange, we can partially fill orders and enable a fully-fledged decentralised exchange (DEX) that enables cross-chain trading: a trustless version of existing crypto exchanges. There's no need for gateways, token wrapping or other potential bottlenecks or points of failure.
 
-There are also plenty of reasons someone might want optional privacy - transparent ledgers are a feature for many use cases. e.g. charities that want everyone to have full access to the flow of funds.  
 
-There are also strong arguments for optional privacy for adoption and regulation. ErgoMixer is non-interactive, so it works with the blockchain alone; no off-chain coordination with others (and a trusted coordinator) is needed.
+## 'Optional' Privacy?
 
-In future, the community could elect to enable privacy by default for every transaction in Ergo. Or we'll see integration mix-nets and other novel ideas on the application layer.  
+> Privacy must remain an option to protect the individual. It does not have to be forced; let people make their own choices. Privacy is the ability to create barriers and erect boundaries to create a space for the individual. It is up to each what borders and boundaries they choose to make. - [*The Ergo Manifesto*](https://ergoplatform.org/en/blog/2021-04-26-the-ergo-manifesto/)
 
-> Privacy must remain an option to protect the individual. It does not have to be forced; let people make their own choices. Privacy is the ability to create barriers and erect boundaries to create a space for the individual. It is up to each what borders and boundaries they choose to make. - *The Ergo Manifesto*
+A rich smart-contract language is a priority in Ergo, and with non-optional privacy, you can't have (efficient) powerful contracts. Even more, formalising leakage is hard for simple payments, and arbitrary contracts are not feasible.
 
+There are also plenty of reasons someone might want optional privacy - transparent ledgers are a feature for many use cases. e.g. charities that want everyone to have full access to the flow of funds.  
 
+There are also strong arguments for optional privacy for adoption and regulation. ErgoMixer is non-interactive, so it works with the blockchain alone; no off-chain coordination with others (and a trusted coordinator) is needed.
 
-## Use Cases
+In the future, the community could enable privacy by default for every transaction in Ergo. Or we'll see integration mix-nets and other novel ideas on the application layer.  
 
-These composable proofs enable some very strong use cases combined with a blockchain. The logic for proofs can include conditions based on the blockchain state. For example, 'If the deadline block height has been reached, Alice can provide knowledge of a secret key for a refund. OR a ring signature from Alice and Bob is required to spend coins.' Or 'If this account holds a minimum of 100 ERG, Alice OR Bob can remove funds above that amount.'
 
-Swapping coins or custom tokens trustlessly across any Bitcoin-like blockchain is relatively easy. But beyond that, Ergo allows partial swaps. Like on a regular exchange, we can partially fill orders and enable a fully-fledged decentralised exchange (DEX) that enables cross-chain trading: a trustless version of existing crypto exchanges. There's no need for gateways, token wrapping or other potential bottlenecks or points of failure.
diff --git a/docs/eco/cyti.md b/docs/eco/cyti.md
@@ -1 +1,3 @@
-# CYTI
+# CYTI
+
+[CYTI](https://github.com/ThierryM1212/cyti) is the acronym for Choose Your Token ID. The team built a ‘minable’ smart contract that will allow an entity “to mint tokens with a given character sequence at the beginning of the token ID. A token minter creates a CYTI request, and miners generate the proper token ID using the CYTI miner software. When one of the miners succeeds, [they receive] the fee from the CYTI contract and the token with the right token ID is sent to the token minter.”
diff --git a/docs/eco/nightowl.md b/docs/eco/nightowl.md
@@ -9,4 +9,4 @@
 
 - [Website](https://dev.nightowlcasino.io/)
 - [GitHub](https://github.com/nightowlcasino)
-- [Slides](pdf/Night_Owl_-_Ergo_Hack_lll_Presentation_Final.pdf)
+- [Slides](/pdf/Night_Owl_-_Ergo_Hack_lll_Presentation_Final.pdf)
diff --git a/docs/mining/autolykos.md b/docs/mining/autolykos.md
@@ -7,7 +7,7 @@ Ergo mining is based on Autolykos, a fairly launched efficient ASIC-resistant Pr
 [
   {
     "title": "Start Mining",
-    "url": "join.md"
+    "url": "setup/join.md"
   },
   {
     "title": "Algorithm",

diff --git a/docs/node/testnet/cpu-mining.md b/docs/node/testnet/cpu-mining.md
@@ -1,7 +1,7 @@
 # CPU Mining
 
 ## Getting Set-up
-> Please refer to [node](node.md) for basic node set-up up to this point.
+> Please refer to [node](install.md) for basic node set-up up to this point.
 
 To CPU mine on the testnet, your `testnet.conf` should look like this.