@@ -51,18 +51,25 @@ Moreover, such a specification should be unambiguous and capable of
51
51
answering all the questions regarding corner-case behaviors.
52
52
To our knowledge, there was no such formal specification for ERC20, or
53
53
for ERC20 variants, available at the time of this writing (2 December 2017).
54
+
54
55
The existing ERC20 specifications are either too informal to serve as a formal
55
- specification for verification purposes, such as the Ethereum
56
+ specification for verification purposes, or they are not executable, incomplete
57
+ and use unnecessarily advanced logical formalisms.
58
+ For example, the Ethereum
56
59
[ wiki] ( https://theethereum.wiki/w/index.php/ERC20_Token_Standard ) and
57
60
[ github] ( https://github.com/ethereum/EIPs/blob/master/EIPS/eip-20-token-standard.md )
58
- variants in spite of being called * formalized* by a
61
+ variants are rather informal and imprecise, in spite of being called
62
+ * formalized* by a
59
63
[ coindesk article] ( https://www.coindesk.com/ethereums-erc-20-token-standard-formalized ) ,
60
- [ McDonald's] ( https://medium.com/@jgm.orinoco/understanding-erc-20-token-contracts-a809a7310aa5 ) ,
61
- [ Seibel's] ( https://medium.com/@james_3093/ethereum-erc20-tokens-explained-9f7f304055df ) ,
64
+ and so are the ERC20 descriptions by
65
+ [ McDonald] ( https://medium.com/@jgm.orinoco/understanding-erc-20-token-contracts-a809a7310aa5 ) ,
66
+ [ Seibel] ( https://medium.com/@james_3093/ethereum-erc20-tokens-explained-9f7f304055df ) ,
67
+ [ McKie] ( https://medium.com/blockchannel/the-anatomy-of-erc20-c9e5c5ff1d02 ) ,
62
68
etc., as well as the
63
69
[ Stackoverflow] ( https://ethereum.stackexchange.com/questions/16714/what-are-the-key-criteria-for-meeting-the-erc20-token-standard/16725 )
64
- explanations,
65
- or, when actual formalizations as a mathematical theory were attempted, such as
70
+ explanations.
71
+ On the other hand, when actual formalizations as a mathematical theory were
72
+ attempted, such as
66
73
[ McRainface] ( https://dapphub.github.io/LLsai/token ) 's, they are paper-based
67
74
(i.e., not executable) and using logical formalisms that are hard to understand
68
75
by most developers, such as
0 commit comments