|
1 | 1 | ### eip: 5??? |
2 | | -### title: Executable Script extention for Token Contracts |
| 2 | +### title: Executable Script extension for Token Contracts |
3 | 3 | ### description: Add a scriptURI to point to point to an executable script associated with the functionality of the token. |
4 | | -### author: James (@JamesSmartCell), Weiwu (@weiwu-zhang), Tore Frederiksen |
| 4 | +### author: James (@JamesSmartCell), Weiwu (@weiwu-zhang), Tore Frederiksen (@jot2re) |
5 | 5 | ### discussions-to: |
6 | 6 | ### status: Draft |
7 | 7 | ### type: Standards Track |
8 | 8 | ### category: ERC |
9 | 9 | ### created: 2022-05-03 |
10 | 10 | ### requires: |
11 | 11 | ### Abstract |
12 | | -This standard is an interface that adds a scriptURI for locating executable scripts associated with the token. |
| 12 | +This standard is an interface that adds a `scriptURI()` function for locating executable scripts associated with the token. |
13 | 13 |
|
14 | 14 | ### Motivation |
15 | 15 | Often NFT authors want to provide some user functionality to their tokens, e.g. through scripts. This should done in a safe way, without opening the user to potential scams. By packaging a link to official scripts, created by the token minter, within the token itself, users can be sure they are using the correct script. |
16 | 16 |
|
17 | | -This ERC proposes adding a scriptURI which is a structure containing an array of URIs to external resources in IPFS, github, a cloud provider, etc. |
| 17 | +This ERC proposes adding a scriptURI which is a structure containing an array of URIs to external resources in IPFS, GitHub, a cloud provider, etc. |
18 | 18 | Each scriptURI semantically contains access information to access a *single* signed script, stored in one or more off-chain locations. |
19 | 19 | Concretely each element in the array contains a pair of URIs, one to the script itself, and one to a signature of the script. |
20 | 20 |
|
@@ -111,10 +111,10 @@ interface IERC5XXX { |
111 | 111 | /// @notice Get the scriptURI for the contract |
112 | 112 | /// @return The scriptURI |
113 | 113 | function getScriptURI() external view returns(ScriptURI memory); |
114 | | - |
| 114 | + |
115 | 115 | /// @notice Get the scriptURI for the contract |
116 | 116 | /// @return The scriptURI |
117 | | - function getVerificationKey) external view returns(address memory); |
| 117 | + function getVerificationKey() external view returns(address memory); |
118 | 118 |
|
119 | 119 |
|
120 | 120 | /// @notice Update the scriptURI |
@@ -146,7 +146,7 @@ The interface MUST be implemented under the following constraints: |
146 | 146 |
|
147 | 147 |
|
148 | 148 | ### Rationale |
149 | | -Using this method avoids the need for building secure and certified centralised hosting and allow scripts to be hosted anywhere: IPFS, github or cloud storage. |
| 149 | +Using this method avoids the need for building secure and certified centralised hosting and allow scripts to be hosted anywhere: IPFS, GitHub or cloud storage. |
150 | 150 |
|
151 | 151 | ### Backwards Compatibility |
152 | 152 | This standard is compatible with all Token standards (ERC20, 721, 777, 1155 etc). |
|
0 commit comments