7 Commits

Author	SHA1	Message	Date
Micah Zoltu	15f61ed0fd	Adds rule to EIP-1 that references to other EIPs must use relative path format and the first reference must be linked. (#2947) ... I have gone through and updated all existing EIPs to match this rule, including EIP-1. In some cases, people were using markdown citations, I suspect because the long-form was a bit verbose to inline. Since the relative path is quite short, I moved these to inline but I wouldn't be opposed to putting them back to citation format if that is desired by the authors. In doing the migration/cleanup, I found some EIP references to EIPs that don't actually exist. In these cases I tried to excise the reference from the EIP as best I could. It is worth noting that the Readme actually already had this rule, it just wasn't expressed properly in EIP-1 and the "Citation Format" section of the readme I think caused people a bit of confusion (when citing externally, you should use the citation format).	2020-09-30 12:22:43 +08:00
William Entriken	af677b348d	Use solidity/javascript highlighting in various EIPs (#2372)	2019-11-22 23:55:15 +00:00
Nick Johnson	e44c9e6336	Update EIP with new test vectors and better algorithm descriptions (#2322)	2019-10-24 14:00:53 +13:00
Nick Johnson	60bad6b0c7	Add binance chain to EIP2304 (#2318)	2019-10-21 16:58:50 +13:00
Nick Johnson	9f47fdefd6	Ens multichain (#2317) ... * Add description and test vectors for different address types; specify bitcoin format as scriptPubkey * Fix table	2019-10-21 15:03:33 +13:00
Nick Johnson	8664f3500c	Fix use of b58/b58check for bitcoin (#2305)	2019-10-02 11:50:40 +10:00
Nick Johnson	e10d542fde	Ens multichain support (#2304) ... * First draft for ENS multicoin support * Rewrite multicoin support to use maps * Tweaks and fixes * Update and rename eip-draft-ens-multicoin.md to eip-2304.md	2019-10-02 10:16:38 +10:00