-
Notifications
You must be signed in to change notification settings - Fork 118
NEP: Contract Basic Method Guideline #136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
5605306
nep for upgrade standard
superboyiii 9b3e0a7
improve
superboyiii 417bff6
fix
superboyiii 90b8bc2
Shargon's advice.
superboyiii 1cac040
guideline
superboyiii 8be7bfc
Erik
superboyiii 0c6aed3
Fix and remove event
superboyiii 567feec
fix
superboyiii eee07aa
warning
superboyiii File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,101 @@ | ||
<pre> | ||
NEP: | ||
Title: Contract Basic Methods Guideline | ||
Author: Owen Zhang <[email protected]>, Fernando Díaz Toledano <[email protected]>, Erik Zhang <[email protected]> | ||
Type: Informational | ||
Status: Draft | ||
Created: 2021-04-19 | ||
Replaces: 0 | ||
</pre> | ||
|
||
|
||
|
||
|
||
|
||
|
||
==Abstract== | ||
|
||
This proposal outlines a basic method guideline for the NEO blockchain that will provide systems with a generalized interaction mechanism for smart contract initial deploy, update and destroy. | ||
|
||
==Motivation== | ||
|
||
As the NEO blockchain scales, Smart Contract Initial Deploy, Update and Destroy will become increasingly important. Without guideline for <code>_deploy</code>, <code>update</code> and <code>destroy</code> method, systems will be required to maintain a unique API for each contract, regardless of their similarity to other contracts which makes application development very inconvenient. This guideline can lead most contracts to implement the same basic methods with the same types of parameters but still accept diversity. | ||
|
||
==Specification== | ||
|
||
In the method definitions below, we provide both the definitions of the functions as they are defined in the contract as well as the invoke parameters. | ||
|
||
===Methods=== | ||
|
||
====_deploy==== | ||
|
||
<pre> | ||
{ | ||
"name": "_deploy", | ||
"safe": false, | ||
"parameters": [ | ||
{ | ||
"name": "data", | ||
"type": "Any" | ||
}, | ||
{ | ||
"name": "update", | ||
"type": "Boolean" | ||
} | ||
], | ||
"returntype": "Void" | ||
} | ||
</pre> | ||
|
||
This is an optional function which will be automatically executed when contract first deployed. | ||
|
||
The parameter <code>data</code> can be any type of supported parameters for additional message purpose. | ||
|
||
<code>update</code> returns if it's the initial deployment of this contract. The function SHOULD check whether <code>update</code> returns true. If not, continue execution. If true, return. | ||
|
||
====update==== | ||
|
||
<pre> | ||
{ | ||
"name": "update", | ||
"safe": false, | ||
"parameters": [ | ||
{ | ||
"name": "nefFile", | ||
"type": "ByteArray" | ||
}, | ||
{ | ||
"name": "manifest", | ||
"type": "String" | ||
}, | ||
{ | ||
"name": "data", | ||
"type": "Any" | ||
} | ||
], | ||
"returntype": "Void" | ||
} | ||
</pre> | ||
|
||
Updating a smart contract MUST have <code>nefFile</code> and <code>manifest.json</code>. | ||
|
||
The parameter <code>data</code> can be any type of supported parameters for additional message purpose. | ||
|
||
The function SHOULD check whether the <code>signer</code> address equals the <code>owner</code> hash of contract. The function SHOULD use the SYSCALL <code>Neo.Runtime.CheckWitness</code> to verify the <code>signer</code>. | ||
|
||
====destroy==== | ||
|
||
<pre> | ||
{ | ||
"name": "destroy", | ||
"safe": false, | ||
"parameters": [], | ||
"returntype": "Void" | ||
} | ||
</pre> | ||
This function can delete all the storage of this contract. | ||
|
||
The function SHOULD check whether the <code>signer</code> address equals the <code>owner</code> hash of contract. The function SHOULD use the SYSCALL <code>Neo.Runtime.CheckWitness</code> to verify the <code>signer</code>. | ||
|
||
If any token is in this contract asset, they MUST be transferred to another address before <code>destroy</code>. | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.