NEO GUI “Execution terminated in fault state”
Hi I am a newbie in NEO blockchain, trying to deploy my first contract using neo-gui.
I am following this toturial:
https://freestartupkits.com/articles/technology/cryptocurrency-news-and-tips/ultimate-neo-smart-contract-tutorial/#part4
on "Invoke your second smart contract" I get error "execution terminated in fault state" (see image below).
I believe that I have enough gas. How to fix this?
blockchain
edited Nov 14 at 11:14
Chris Skardon
4,97322338
asked Nov 12 at 10:56
justadev
140210
add a comment |
Hi I am a newbie in NEO blockchain, trying to deploy my first contract using neo-gui.
I am following this toturial:
https://freestartupkits.com/articles/technology/cryptocurrency-news-and-tips/ultimate-neo-smart-contract-tutorial/#part4
on "Invoke your second smart contract" I get error "execution terminated in fault state" (see image below).
I believe that I have enough gas. How to fix this?
blockchain
edited Nov 14 at 11:14
Chris Skardon
4,97322338
asked Nov 12 at 10:56
justadev
140210
add a comment |
Hi I am a newbie in NEO blockchain, trying to deploy my first contract using neo-gui.
I am following this toturial:
https://freestartupkits.com/articles/technology/cryptocurrency-news-and-tips/ultimate-neo-smart-contract-tutorial/#part4
on "Invoke your second smart contract" I get error "execution terminated in fault state" (see image below).
I believe that I have enough gas. How to fix this?
blockchain
edited Nov 14 at 11:14
Chris Skardon
4,97322338
asked Nov 12 at 10:56
justadev
140210
Hi I am a newbie in NEO blockchain, trying to deploy my first contract using neo-gui.
I am following this toturial:
https://freestartupkits.com/articles/technology/cryptocurrency-news-and-tips/ultimate-neo-smart-contract-tutorial/#part4
on "Invoke your second smart contract" I get error "execution terminated in fault state" (see image below).
I believe that I have enough gas. How to fix this?
blockchain
blockchain
edited Nov 14 at 11:14
Chris Skardon
4,97322338
asked Nov 12 at 10:56
justadev
140210
edited Nov 14 at 11:14
Chris Skardon
4,97322338
asked Nov 12 at 10:56
justadev
140210
edited Nov 14 at 11:14
Chris Skardon
4,97322338
edited Nov 14 at 11:14
Chris Skardon
4,97322338
edited Nov 14 at 11:14
Chris Skardon
4,97322338
4,97322338
asked Nov 12 at 10:56
justadev
140210
asked Nov 12 at 10:56
justadev
140210
asked Nov 12 at 10:56
justadev
140210
140210
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This is because of a compatibility issue in the contract compiler.
You will have to return to the point where you had built and deployed the neo-compiler. Open the project for neo-compiler, find the neon/Program.cs:line 26 and amend the line that sets the bCompatible as:
bool bCompatible = true;
Then re-build, re-deploy, the compiler and recompile your contract with the new compiler.
I know, this is not entertaining.
Alternatively one may be able to pass the --compatible flag to the compiler when building the contract but that is too much for a VS newbie such as me.
answered Nov 19 at 12:18
laksu
316
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53260666%2fneo-gui-execution-terminated-in-fault-state%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is because of a compatibility issue in the contract compiler.
You will have to return to the point where you had built and deployed the neo-compiler. Open the project for neo-compiler, find the neon/Program.cs:line 26 and amend the line that sets the bCompatible as:
bool bCompatible = true;
Then re-build, re-deploy, the compiler and recompile your contract with the new compiler.
I know, this is not entertaining.
Alternatively one may be able to pass the --compatible flag to the compiler when building the contract but that is too much for a VS newbie such as me.
answered Nov 19 at 12:18
laksu
316
add a comment |
This is because of a compatibility issue in the contract compiler.
You will have to return to the point where you had built and deployed the neo-compiler. Open the project for neo-compiler, find the neon/Program.cs:line 26 and amend the line that sets the bCompatible as:
bool bCompatible = true;
Then re-build, re-deploy, the compiler and recompile your contract with the new compiler.
I know, this is not entertaining.
Alternatively one may be able to pass the --compatible flag to the compiler when building the contract but that is too much for a VS newbie such as me.
answered Nov 19 at 12:18
laksu
316
add a comment |
This is because of a compatibility issue in the contract compiler.
You will have to return to the point where you had built and deployed the neo-compiler. Open the project for neo-compiler, find the neon/Program.cs:line 26 and amend the line that sets the bCompatible as:
bool bCompatible = true;
Then re-build, re-deploy, the compiler and recompile your contract with the new compiler.
I know, this is not entertaining.
Alternatively one may be able to pass the --compatible flag to the compiler when building the contract but that is too much for a VS newbie such as me.
answered Nov 19 at 12:18
laksu
316
This is because of a compatibility issue in the contract compiler.
You will have to return to the point where you had built and deployed the neo-compiler. Open the project for neo-compiler, find the neon/Program.cs:line 26 and amend the line that sets the bCompatible as:
bool bCompatible = true;
Then re-build, re-deploy, the compiler and recompile your contract with the new compiler.
I know, this is not entertaining.
Alternatively one may be able to pass the --compatible flag to the compiler when building the contract but that is too much for a VS newbie such as me.
answered Nov 19 at 12:18
laksu
316
edited Nov 19 at 15:26
answered Nov 19 at 12:18
laksu
316
answered Nov 19 at 12:18
laksu
316
answered Nov 19 at 12:18
laksu
316
316
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53260666%2fneo-gui-execution-terminated-in-fault-state%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
