Fdtxjr

How to write capital alpha?

Is there public access to the Meteor Crater in Arizona?

Why is it faster to reheat something than it is to cook it?

How much damage would a cupful of neutron star matter do to the Earth?

What do you call the main part of a joke?

What was the first language to use conditional keywords?

Trademark violation for app?

What does it mean that physics no longer uses mechanical models to describe phenomena?

How to play a character with a disability or mental disorder without being offensive?

Can a new player join a group only when a new campaign starts?

One-one communication

What does Turing mean by this statement?

Antipodal Land Area Calculation

Project Euler #1 in C++

Did Mueller's report provide an evidentiary basis for the claim of Russian govt election interference via social media?

What would you call this weird metallic apparatus that allows you to lift people?

What to do with repeated rejections for phd position

Generate an RGB colour grid

Amount of permutations on an NxNxN Rubik's Cube

Converted a Scalar function to a TVF function for parallel execution-Still running in Serial mode

Strange behavior of Object.defineProperty() in JavaScript

AppleTVs create a chatty alternate WiFi network

What's the meaning of "fortified infraction restraint"?

Why limits give us the exact value of the slope of the tangent line?

CREATE opcode: what does it really do?

2

I am looking at the docs, but cannot really understand what CREATE opcode does. I can tell that CREATE does create a new smart contract from a memory chunk, pass the gas value to this new contract, then returns. But before returning, does it execute the new contract?

This confuses me because looking at the disassembly code of the smart contract bytecode, after CREATE, I cannot see any call to CALL after that, but then I still see a call to RETURNDATASIZE, which I suppose only happen after CALL. Without CALL, where it get returned data from?

Any enlighten, please?

opcode create

share|improve this question

asked Mar 27 at 19:41

user311703user311703

1846

add a comment | 

2

I am looking at the docs, but cannot really understand what CREATE opcode does. I can tell that CREATE does create a new smart contract from a memory chunk, pass the gas value to this new contract, then returns. But before returning, does it execute the new contract?

This confuses me because looking at the disassembly code of the smart contract bytecode, after CREATE, I cannot see any call to CALL after that, but then I still see a call to RETURNDATASIZE, which I suppose only happen after CALL. Without CALL, where it get returned data from?

Any enlighten, please?

opcode create

share|improve this question

asked Mar 27 at 19:41

user311703user311703

1846

add a comment | 

I am looking at the docs, but cannot really understand what CREATE opcode does. I can tell that CREATE does create a new smart contract from a memory chunk, pass the gas value to this new contract, then returns. But before returning, does it execute the new contract?

This confuses me because looking at the disassembly code of the smart contract bytecode, after CREATE, I cannot see any call to CALL after that, but then I still see a call to RETURNDATASIZE, which I suppose only happen after CALL. Without CALL, where it get returned data from?

Any enlighten, please?

opcode create

share|improve this question

asked Mar 27 at 19:41

user311703user311703

1846

share|improve this question

asked Mar 27 at 19:41

user311703user311703

1846

share|improve this question

asked Mar 27 at 19:41

user311703user311703

1846

asked Mar 27 at 19:41

user311703user311703

1846

asked Mar 27 at 19:41

user311703user311703

1846

1 Answer
1

active

oldest

votes

5

CREATE, in a way, does a built in CALL. What actually happens is that the data passed to call isn't the contract bytecode, it's the init bytecode.

When CREATE opcode is executed, the EVM creates a call frame in the context of the new contract (e.g. address(this) is the new contracts address). This executes the data passed to CREATE as the code, which in higher level languages is basically the constructor. At the end of this init stuff, it returns the actual code of the contract that is stored in the state trie.

The easiest way to think about it, which is also fairly accurate, is that the Solidity compiler takes all the executional code of the contract, compiles it to bytecode, and adds it as a return statement at the end of the constructor.

share|improve this answer

edited Mar 27 at 20:20

answered Mar 27 at 20:13

flygoingflygoing

7,755931

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  ah, so CREATE when creating a contract actually returns the contract bytecode, right? then after that, CALL will actually executes the contract?
  
  – user311703
  Mar 27 at 20:22
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Please could you tell me what is the best way to track/trace what is really happening at bytecode level? Does Remix a good tool to do this?
  
  – user311703
  Mar 27 at 20:23
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  CREATE executes the code passed to it, and that code returns the contact bytecode, yes. Just wanted to be clear on that
  
  – flygoing
  Mar 27 at 20:40
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  If you need to a call a function after it's created, then yeah, there would be a CALL right after. Remix is a pretty good way to track/trace on the bytecode level, it has pretty good EVM debugging tools for stepping in/out of bytecode
  
  – flygoing
  Mar 27 at 20:41
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  In that case the init code would just return the code for your contract. The compiler basically creates a default constructor that does nothing but return the actual bytecode.
  
  – flygoing
  Mar 28 at 14:22
  

  
  
  
  

 | 
show 1 more comment

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "642"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
);



);

draft saved

draft discarded

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

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fethereum.stackexchange.com%2fquestions%2f68943%2fcreate-opcode-what-does-it-really-do%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

5

CREATE, in a way, does a built in CALL. What actually happens is that the data passed to call isn't the contract bytecode, it's the init bytecode.

When CREATE opcode is executed, the EVM creates a call frame in the context of the new contract (e.g. address(this) is the new contracts address). This executes the data passed to CREATE as the code, which in higher level languages is basically the constructor. At the end of this init stuff, it returns the actual code of the contract that is stored in the state trie.

The easiest way to think about it, which is also fairly accurate, is that the Solidity compiler takes all the executional code of the contract, compiles it to bytecode, and adds it as a return statement at the end of the constructor.

share|improve this answer

edited Mar 27 at 20:20

answered Mar 27 at 20:13

flygoingflygoing

7,755931

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  ah, so CREATE when creating a contract actually returns the contract bytecode, right? then after that, CALL will actually executes the contract?
  
  – user311703
  Mar 27 at 20:22
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Please could you tell me what is the best way to track/trace what is really happening at bytecode level? Does Remix a good tool to do this?
  
  – user311703
  Mar 27 at 20:23
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  CREATE executes the code passed to it, and that code returns the contact bytecode, yes. Just wanted to be clear on that
  
  – flygoing
  Mar 27 at 20:40
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  If you need to a call a function after it's created, then yeah, there would be a CALL right after. Remix is a pretty good way to track/trace on the bytecode level, it has pretty good EVM debugging tools for stepping in/out of bytecode
  
  – flygoing
  Mar 27 at 20:41
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  In that case the init code would just return the code for your contract. The compiler basically creates a default constructor that does nothing but return the actual bytecode.
  
  – flygoing
  Mar 28 at 14:22
  

  
  
  
  

 | 
show 1 more comment

5

CREATE, in a way, does a built in CALL. What actually happens is that the data passed to call isn't the contract bytecode, it's the init bytecode.

When CREATE opcode is executed, the EVM creates a call frame in the context of the new contract (e.g. address(this) is the new contracts address). This executes the data passed to CREATE as the code, which in higher level languages is basically the constructor. At the end of this init stuff, it returns the actual code of the contract that is stored in the state trie.

The easiest way to think about it, which is also fairly accurate, is that the Solidity compiler takes all the executional code of the contract, compiles it to bytecode, and adds it as a return statement at the end of the constructor.

share|improve this answer

edited Mar 27 at 20:20

answered Mar 27 at 20:13

flygoingflygoing

7,755931

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  ah, so CREATE when creating a contract actually returns the contract bytecode, right? then after that, CALL will actually executes the contract?
  
  – user311703
  Mar 27 at 20:22
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Please could you tell me what is the best way to track/trace what is really happening at bytecode level? Does Remix a good tool to do this?
  
  – user311703
  Mar 27 at 20:23
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  CREATE executes the code passed to it, and that code returns the contact bytecode, yes. Just wanted to be clear on that
  
  – flygoing
  Mar 27 at 20:40
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  If you need to a call a function after it's created, then yeah, there would be a CALL right after. Remix is a pretty good way to track/trace on the bytecode level, it has pretty good EVM debugging tools for stepping in/out of bytecode
  
  – flygoing
  Mar 27 at 20:41
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  In that case the init code would just return the code for your contract. The compiler basically creates a default constructor that does nothing but return the actual bytecode.
  
  – flygoing
  Mar 28 at 14:22
  

  
  
  
  

 | 
show 1 more comment

CREATE, in a way, does a built in CALL. What actually happens is that the data passed to call isn't the contract bytecode, it's the init bytecode.

When CREATE opcode is executed, the EVM creates a call frame in the context of the new contract (e.g. address(this) is the new contracts address). This executes the data passed to CREATE as the code, which in higher level languages is basically the constructor. At the end of this init stuff, it returns the actual code of the contract that is stored in the state trie.

The easiest way to think about it, which is also fairly accurate, is that the Solidity compiler takes all the executional code of the contract, compiles it to bytecode, and adds it as a return statement at the end of the constructor.

share|improve this answer

edited Mar 27 at 20:20

answered Mar 27 at 20:13

flygoingflygoing

7,755931

share|improve this answer

edited Mar 27 at 20:20

answered Mar 27 at 20:13

flygoingflygoing

7,755931

answered Mar 27 at 20:13

flygoingflygoing

7,755931

answered Mar 27 at 20:13

flygoingflygoing

7,755931