From 7b713c661e2dd0b8976e01adc4029b28e61cc205 Mon Sep 17 00:00:00 2001 From: Robert Phair Date: Tue, 6 Sep 2022 13:36:36 +0530 Subject: [PATCH] issue 109: cross-CIP links need absolute path until general remediation (#304) --- CIP-0011/README.md | 6 +++--- CIP-0035/README.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/CIP-0011/README.md b/CIP-0011/README.md index bbb3f931b6..ca948ca09a 100644 --- a/CIP-0011/README.md +++ b/CIP-0011/README.md @@ -11,7 +11,7 @@ License: CC-BY-4.0 ## Abstract -Starting with the Shelley hardfork, Cardano makes use of both the *UTXO model* and the *account model*. To support both transaction models from the same master key, we allocate a new chain for [CIP1852](../CIP-1852) +Starting with the Shelley hardfork, Cardano makes use of both the *UTXO model* and the *account model*. To support both transaction models from the same master key, we allocate a new chain for [CIP1852](https://github.com/cardano-foundation/CIPs/blob/master/CIP-1852/README.md) ## Terminology @@ -36,7 +36,7 @@ Generally it's best to only use a cryptographic key for a single purpose, and so ## Specification -Recall that [CIP1852](../CIP-1852) specifies the following derivation path +Recall that [CIP1852](https://github.com/cardano-foundation/CIPs/blob/master/CIP-1852/README.md) specifies the following derivation path ``` m / purpose' / coin_type' / account' / chain / address_index @@ -71,4 +71,4 @@ stake1uy8ykk8dzmeqxm05znz65nhr80m0k3gxnjvdngf8azh6sjc6hyh36 ## Copyright -This CIP is licensed under [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode) \ No newline at end of file +This CIP is licensed under [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode) diff --git a/CIP-0035/README.md b/CIP-0035/README.md index e138893b5a..f7c99b6521 100644 --- a/CIP-0035/README.md +++ b/CIP-0035/README.md @@ -140,7 +140,7 @@ This proposal deals only with the types of change listed in "Types of change", a This proposal recommends that some of the changes listed in "Types of change" (specified below) should: 1. Be proposed in a CIP. -2. Go through additional process in addition to the [usual CIP process](../CIP-0001/README.md). +2. Go through additional process in addition to the [usual CIP process](https://github.com/cardano-foundation/CIPs/blob/master/CIP-0001/README.md). The additional process mostly takes the form of additional information that should be present in the CIP before it moves to particular stages. As such, it is up to the CIP Editors to enforce this.