From a9bf09f9738001825563f737fabfd43416247514 Mon Sep 17 00:00:00 2001 From: VargSupercolony Date: Tue, 29 Jun 2021 17:35:55 +0300 Subject: [PATCH 1/3] fix some typos --- PSPs/psp-17.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/PSPs/psp-17.md b/PSPs/psp-17.md index 3791ed6..828c629 100644 --- a/PSPs/psp-17.md +++ b/PSPs/psp-17.md @@ -11,7 +11,7 @@ A standard interface for Ink! tokens. -This proposal aims to define the standard token in ink! smart contracts, in the same way of EIP-20 for Ethereum ecosystem (https://github.com/ethereum/EIPs/edit/master/EIPS/eip-20.md). +This proposal aims to define the standard token in ink! smart contracts, just like [EIP-20](https://github.com/ethereum/EIPs/edit/master/EIPS/eip-20.md) for Ethereum ecosystem. ## Implementation @@ -26,15 +26,15 @@ A standard interface allows any Ink! tokens on Polkadot/Kusama to be re-used by ## Motivation for having a standard separate from ERC20 -Due to different nature of ink!'s the Token Standard should be have ink! specific rules and methods. -Therefore different name - PSP-20. +Due to different nature of ink!, the standard should have ink!-specific rules and methods, +therefore PSP-20 differs from ERC-20 in its implementation. ## Specification The main motivation for this proposal is to have one **trait** that shares the same **trait naming** between all implementations, as naming of trait affects the identifiers of functions in this trait. -The second motivation is to define an exhaustive method list in this trait. Unlike ERC20, we suggest including `increase_allowance` & `decrease_allowance` +The second motivation is to define an exhaustive method list in this trait. Unlike ERC-20, we suggest including `increase_allowance` & `decrease_allowance` as a part of standard proposal and extract metadata fields to separate trait. From 4f69b941d7e4cf14fed0ff0b7301a3a312e068de Mon Sep 17 00:00:00 2001 From: VargSupercolony Date: Thu, 1 Jul 2021 11:39:56 +0300 Subject: [PATCH 2/3] fix some typos, add local links --- PSPs/psp-17.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/PSPs/psp-17.md b/PSPs/psp-17.md index 14e4926..f03165c 100644 --- a/PSPs/psp-17.md +++ b/PSPs/psp-17.md @@ -14,7 +14,8 @@ A standard interface for Ink! tokens. This proposal aims to define the standard token in ink! smart contracts, just like [EIP-20](https://github.com/ethereum/EIPs/edit/master/EIPS/eip-20.md) for Ethereum ecosystem. ## Importance -Currently with no standard every contract will have a different signature. So no interoperability is possible. This porposal aims to resolve that by having one **trait**(interface) that shares the same **trait naming** between all implementations, as naming of trait affects the identifiers of functions in this trait. +Currently, while there is no standard, every contract will have different signatures. Thus, no interoperability is possible. This proposal aims to resolve that by having one **trait**(interface) that shares the +same **trait naming** between all implementations, as naming of trait affects the identifiers of functions in this trait. ## Implementation @@ -37,10 +38,10 @@ Another difference is that it has `PSP17Receiver` trait, and `on_received` metho ## Specification -1. Traits -2. Types -3. Events -4. Errors +1. [Traits](#Traits) +2. [Types](#Types) +3. [Events](#Events) +4. [Errors](#Errors) ### Traits From 6d2b148156b97be62ce0ece1daeaadec5ffc6fe0 Mon Sep 17 00:00:00 2001 From: VargSupercolony Date: Thu, 1 Jul 2021 11:41:28 +0300 Subject: [PATCH 3/3] fix signatures typo --- PSPs/psp-17.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/PSPs/psp-17.md b/PSPs/psp-17.md index f03165c..90766f7 100644 --- a/PSPs/psp-17.md +++ b/PSPs/psp-17.md @@ -14,7 +14,7 @@ A standard interface for Ink! tokens. This proposal aims to define the standard token in ink! smart contracts, just like [EIP-20](https://github.com/ethereum/EIPs/edit/master/EIPS/eip-20.md) for Ethereum ecosystem. ## Importance -Currently, while there is no standard, every contract will have different signatures. Thus, no interoperability is possible. This proposal aims to resolve that by having one **trait**(interface) that shares the +Currently, while there is no standard, every contract will have different signature. Thus, no interoperability is possible. This proposal aims to resolve that by having one **trait**(interface) that shares the same **trait naming** between all implementations, as naming of trait affects the identifiers of functions in this trait. ## Implementation