Upgrade to https (#2626)

EIPS/eip-1123.md

@@ -1840,7 +1840,7 @@ widespread implementation in commonly-used development tools.
 The following tools are known to have begun or are nearing completion of
 a supporting implementation.
 
--   [Truffle](http://trufflesuite.com/)
+-   [Truffle](https://trufflesuite.com/)
 
 -   [Populus](https://populus.readthedocs.io/en/latest/)
 

EIPS/eip-1829.md

@@ -104,7 +104,7 @@ Conversion from affine coordinates to compressed coordinates is trivial: `y' = 0
 * Special point addition/doubling [formulas][formulas] for `α = -3`, `α = -1`, `α = 0`, `β = 0`.
 
 
-[formulas]: http://www.hyperelliptic.org/EFD/g1p/auto-shortw.html
+[formulas]: https://www.hyperelliptic.org/EFD/g1p/auto-shortw.html
 
 TODO: The special cases for `α` and `β` might be worth implementing and offered a gas discount.
 

EIPS/eip-2020.md

@@ -224,10 +224,10 @@ This proposal has been collaboratively implemented by [adhara.io](https://adhara
 ## Copyright
 Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
 
-[ERC-20]: http://eips.ethereum.org/EIPS/eip-20
-[ERC-1066]: http://eips.ethereum.org/EIPS/eip-1066
-[ERC-1462]: http://eips.ethereum.org/EIPS/eip-1462
-[ERC-1996]: http://eips.ethereum.org/EIPS/eip-1996
-[ERC-2018]: http://eips.ethereum.org/EIPS/eip-2018
-[ERC-2019]: http://eips.ethereum.org/EIPS/eip-2019
-[ERC-2021]: http://eips.ethereum.org/EIPS/eip-2021
+[ERC-20]: https://eips.ethereum.org/EIPS/eip-20
+[ERC-1066]: https://eips.ethereum.org/EIPS/eip-1066
+[ERC-1462]: https://eips.ethereum.org/EIPS/eip-1462
+[ERC-1996]: https://eips.ethereum.org/EIPS/eip-1996
+[ERC-2018]: https://eips.ethereum.org/EIPS/eip-2018
+[ERC-2019]: https://eips.ethereum.org/EIPS/eip-2019
+[ERC-2021]: https://eips.ethereum.org/EIPS/eip-2021

EIPS/eip-2028.md

@@ -71,7 +71,7 @@ To suggest the gas cost of calldata we shall conduct two types of tests:
 
 [2] Rafael Pass, Lior Seeman, Abhi Shelat: [Analysis of the Blockchain Protocol in Asynchronous Networks](https://eprint.iacr.org/2016/454.pdf), ePrint report 2016/454
 
-[3] Christian Decker, Roger Wattenhofer: [Information propagation in the Bitcoin network](http://www.gsd.inesc-id.pt/~ler/docencia/rcs1314/papers/P2P2013_041.pdf). P2P 2013: 1-10
+[3] Christian Decker, Roger Wattenhofer: [Information propagation in the Bitcoin network](https://www.gsd.inesc-id.pt/~ler/docencia/rcs1314/papers/P2P2013_041.pdf). P2P 2013: 1-10
 
 [4] Vitalik Buterin: [Uncle Rate and Transaction Fee Analysis](https://blog.ethereum.org/2016/10/31/uncle-rate-transaction-fee-analysis/)
 

EIPS/eip-205.md

@@ -38,7 +38,7 @@ Encoding type 1 specifies plaintext JSON, uncompressed; this is the standard for
 
 Encoding type 2 specifies zlib-compressed JSON. This is significantly smaller than uncompressed JSON, and is straightforward to decode offchain. However, it is impracticalfor onchain consumers to use.
 
-Encoding type 4 is [CBOR](http://cbor.io/). CBOR is a binary encoding format that is a superset of JSON, and is both more compact and easier to parse in limited environments such as the EVM. Consumers that support CBOR are strongly encouraged to also support the [stringref extension](http://cbor.schmorp.de/stringref) to CBOR, which provides significant additional reduction in encoded size.
+Encoding type 4 is [CBOR](https://cbor.io/). CBOR is a binary encoding format that is a superset of JSON, and is both more compact and easier to parse in limited environments such as the EVM. Consumers that support CBOR are strongly encouraged to also support the [stringref extension](http://cbor.schmorp.de/stringref) to CBOR, which provides significant additional reduction in encoded size.
 
 Encoding type 8 indicates that the ABI can be found elsewhere, at the specified URI. This is typically the most compact of the supported forms, but also adds external dependencies for implementers. The specified URI may use any schema, but HTTP, IPFS, and Swarm are expected to be the most common.
 

EIPS/eip-2098.md

@@ -50,7 +50,7 @@ used in Bitcoin.)
 
 Second, the top bit of the `s` parameters is **always** 0, due to the use of
 canonical signatures which flip the solution parity to prevent negative values,
-which was introduced as [a constraint in Homestead](http://eips.ethereum.org/EIPS/eip-2).
+which was introduced as [a constraint in Homestead](https://eips.ethereum.org/EIPS/eip-2).
 
 So, we can hijack the top bit in the `s` parameter to store the value of `v`, resulting in:
 

EIPS/eip-2477.md

@@ -319,7 +319,7 @@ Discussion
 
 Other
 
-1. [Shattered] The first collision for full SHA-1. http://shattered.io/static/shattered.pdf
+1. [Shattered] The first collision for full SHA-1. https://shattered.io/static/shattered.pdf
 2. [320 byte file] The second SHA Collision. https://privacylog.blogspot.com/2019/12/the-second-sha-collision.html
 3. [Chosen prefix] https://sha-mbles.github.io
 4. Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths. (Rev. 1. Superseded.) https://csrc.nist.gov/publications/detail/sp/800-131a/rev-1/archive/2015-11-06