NEP: Triggers for NeoContract #15

erikzhang · 2017-10-16T11:09:28Z

Trigger is a mechanism for triggering execution for smart contracts. This NEP defines 4 kinds of triggers, they are Verification, VerificationR, Application and ApplicationR.

Sajjon · 2017-10-16T11:51:05Z

Triggers.mediawiki

+
+==Abstract==
+
+Trigger is a mechanism for triggering execution for smart contracts. This NEP defines 4 kinds of triggers, they are <code>Verification</code>, <code>VerificationR</code>, <code>Application</code> and <code>ApplicationR</code>.


Since writing "two kinds of triggers " in Section "Rationale", you might wanna change "4 kinds of triggers" to "four different kinds of triggers"

Sajjon · 2017-10-16T11:51:50Z

Triggers.mediawiki

+
+==Rationale==
+
+Currently, we have two kinds of triggers in NeoContract: <code>Verification</code> and <code>Application</code>. These two triggers make smart contracts to be able to verify the transactions and modify the states of the blockchain.


"These two triggers make smart contracts to be able to verify the transactions"

should maybe be changed to:

"These two triggers make smart contracts able to verify transactions"

Sajjon · 2017-10-16T12:01:39Z

Triggers.mediawiki

+
+===Verification===
+
+This trigger indicates that the contract is being invoked as a verification function. The verification function can accept multiple parameters, and should return a boolean value that indicates the validity of the transaction or block.


"This trigger" could be made clearer by changing it into "The VerificationR trigger indicates"

Sajjon · 2017-10-16T12:03:40Z

Triggers.mediawiki

+
+===VerificationR===
+
+This trigger indicates that the contract is being invoked as a verification function because it is specified as a target of an output of the transaction. The verification function can accept no parameter, and should return a boolean value that indicates the validity of the transaction.


Maybe "The verification function can accept no parameter" should be changed into "The verification function accepts no parameter" or "... function does not accept any parameter" or "... function takes no parameters"

Sajjon · 2017-10-16T12:04:15Z

Triggers.mediawiki

+
+===Application===
+
+This trigger indicates that the contract is being invoked as an application function. The application function can accept multiple parameters, change the states of the blockchain, and return any type of value.


"The Application trigger indicates that.."

Sajjon · 2017-10-16T12:05:27Z

Triggers.mediawiki

+
+===ApplicationR===
+
+This trigger indicates that the contract is being invoked as an application function because it is specified as a target of an output of the transaction. The application function can accept no parameter, change the states of the blockchain, and return any type of value.


"The application function can accept no parameter" same as above: "takes no parameters" or any of the other suggestions :)

localhuman · 2017-10-16T12:27:50Z

Would the Verification and VerificationR triggers be run for each transaction? Or is VerificationR only run on transactions which have a non-standard verification script?
What does the R in VerificationR stand for?
Would VerificationR have full read-write access for blockchain data? Could it create another contract?

Nikolaj-K · 2017-10-16T15:34:03Z

I supposed "reject"?
Is the argument scheme of Main (operation and then args) more than a suggestion?

canesin · 2017-10-17T03:58:44Z

@erikzhang wouldn't neo-project/neo#84 eliminate the need for this ?

erikzhang · 2017-10-17T07:18:19Z

@localhuman

VerificationR will be triggered only if the deployed contract has been specified as the target of an output of transaction. Immediate contract won't be triggered as VerificationR or ApplicationR.
R means "recipient" or "receiver".
No, Verification and VerificationR can't change the states of blockchain.

RavenXce · 2018-02-08T10:01:09Z

Is anyone assigned to this? Also I'm assuming the new triggers must only apply to InvocationTransaction?

erikzhang · 2018-02-08T10:57:59Z

They apply to every TransactionOutput if the output is a deployed contract.

draft

8d17229

erikzhang added the NEP-Standard label Oct 16, 2017

Sajjon suggested changes Oct 16, 2017

View reviewed changes

Sajjon reviewed Oct 16, 2017

View reviewed changes

grammatical adjustment

1224892

localhuman mentioned this pull request Oct 18, 2017

Feature verification state machine neo-project/neo#84

Closed

Erik Zhang added 2 commits December 14, 2017 23:04

add receiving and received function

5b0bcf1

repair the syntax errors

697cbe3

erikzhang added the accepted label Dec 20, 2017

change state to accepted

597f0dc

erikzhang mentioned this pull request Jan 15, 2018

NEP: URI Standard for Native Asset Transfer #25

Merged

erikzhang added 3 commits May 9, 2018 13:26

add implementation

5d06eb4

Merge remote-tracking branch 'origin/master' into Triggers

c07b464

change state to final

fddb94c

erikzhang merged commit 7d43598 into master May 9, 2018

erikzhang deleted the Triggers branch May 9, 2018 05:48

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

NEP: Triggers for NeoContract #15

NEP: Triggers for NeoContract #15

erikzhang commented Oct 16, 2017

Sajjon Oct 16, 2017

Sajjon Oct 16, 2017

Sajjon Oct 16, 2017

Sajjon Oct 16, 2017

Sajjon Oct 16, 2017

Sajjon Oct 16, 2017

localhuman commented Oct 16, 2017

Nikolaj-K commented Oct 16, 2017

canesin commented Oct 17, 2017

erikzhang commented Oct 17, 2017

RavenXce commented Feb 8, 2018

erikzhang commented Feb 8, 2018


		==Abstract==

		Trigger is a mechanism for triggering execution for smart contracts. This NEP defines 4 kinds of triggers, they are <code>Verification</code>, <code>VerificationR</code>, <code>Application</code> and <code>ApplicationR</code>.


		==Rationale==

		Currently, we have two kinds of triggers in NeoContract: <code>Verification</code> and <code>Application</code>. These two triggers make smart contracts to be able to verify the transactions and modify the states of the blockchain.


		===Verification===

		This trigger indicates that the contract is being invoked as a verification function. The verification function can accept multiple parameters, and should return a boolean value that indicates the validity of the transaction or block.


		===VerificationR===

		This trigger indicates that the contract is being invoked as a verification function because it is specified as a target of an output of the transaction. The verification function can accept no parameter, and should return a boolean value that indicates the validity of the transaction.


		===Application===

		This trigger indicates that the contract is being invoked as an application function. The application function can accept multiple parameters, change the states of the blockchain, and return any type of value.


		===ApplicationR===

		This trigger indicates that the contract is being invoked as an application function because it is specified as a target of an output of the transaction. The application function can accept no parameter, change the states of the blockchain, and return any type of value.

NEP: Triggers for NeoContract #15

NEP: Triggers for NeoContract #15

Conversation

erikzhang commented Oct 16, 2017

Sajjon Oct 16, 2017

Choose a reason for hiding this comment

Sajjon Oct 16, 2017

Choose a reason for hiding this comment

Sajjon Oct 16, 2017

Choose a reason for hiding this comment

Sajjon Oct 16, 2017

Choose a reason for hiding this comment

Sajjon Oct 16, 2017

Choose a reason for hiding this comment

Sajjon Oct 16, 2017

Choose a reason for hiding this comment

localhuman commented Oct 16, 2017

Nikolaj-K commented Oct 16, 2017

canesin commented Oct 17, 2017

erikzhang commented Oct 17, 2017

RavenXce commented Feb 8, 2018

erikzhang commented Feb 8, 2018