Ttykuu

How can a function with a hole (removable discontinuity) equal a function with no hole?

How to escape string to filename? It is in backup a file append date

Implement the Thanos sorting algorithm

Is this apparent Class Action settlement a spam message?

How do scammers retract money, while you can’t?

Opposite of a diet

Proof of work - lottery approach

CREATE opcode: what does it really do?

What is the difference between "behavior" and "behaviour"?

Avoiding estate tax by giving multiple gifts

Failed to fetch jessie backports repository

when is out of tune ok?

Valid Badminton Score?

How do we know the LHC results are robust?

How long to clear the 'suck zone' of a turbofan after start is initiated?

What happens if you roll doubles 3 times then land on "Go to jail?"

Why escape if the_content isnt?

Why didn't Theresa May consult with Parliament before negotiating a deal with the EU?

Was the picture area of a CRT a parallelogram (instead of a true rectangle)?

How to be diplomatic in refusing to write code that breaches the privacy of our users

Can criminal fraud exist without damages?

Is HostGator storing my password in plaintext?

Was Spock the First Vulcan in Starfleet?

Balance Issues for a Custom Sorcerer Variant

CREATE opcode: what does it really do?

What does bytecode of blank contract do?When does a SUICIDE opcode becomes effective?Possible to create new contract via a proposal in the ethereum.org/dao framework?What are the two arguments to a RETURN opcode?Can the CALL opcode be used to create a contract?Transaction Error. Exception thrown in contract code. REVERT opcode when sending ETH to crowdsaleWhat happens in CALL when gas is set to 0?Ethereum opcode: meaning of first few instructions?callvalue opcode, for what?EVM SIGNEXTEND Opcode explanation

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 1 hour ago

user311703user311703

1806

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 1 hour ago

user311703user311703

1806

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 1 hour ago

user311703user311703

1806

share|improve this question

asked 1 hour ago

user311703user311703

1806

share|improve this question

asked 1 hour ago

user311703user311703

1806

asked 1 hour ago

user311703user311703

1806

asked 1 hour ago

user311703user311703

1806

1 Answer
1

active

oldest

votes

3

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 39 mins ago

answered 47 mins ago

flygoingflygoing

7,560931

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  ah, so CREATE when creating a contract actually returns the contract bytecode, right? then after that, CALL will actually executes the contract?
  
  – user311703
  38 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  37 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  CREATE executes the code passed to it, and that code returns the contact bytecode, yes. Just wanted to be clear on that
  
  – flygoing
  20 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  19 mins ago
  

  
  
  
  

add a 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');

var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);

;
$window.on('scroll', onScroll);

);

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

3

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 39 mins ago

answered 47 mins ago

flygoingflygoing

7,560931

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  ah, so CREATE when creating a contract actually returns the contract bytecode, right? then after that, CALL will actually executes the contract?
  
  – user311703
  38 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  37 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  CREATE executes the code passed to it, and that code returns the contact bytecode, yes. Just wanted to be clear on that
  
  – flygoing
  20 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  19 mins ago
  

  
  
  
  

add a comment | 

3

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 39 mins ago

answered 47 mins ago

flygoingflygoing

7,560931

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  ah, so CREATE when creating a contract actually returns the contract bytecode, right? then after that, CALL will actually executes the contract?
  
  – user311703
  38 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  37 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  CREATE executes the code passed to it, and that code returns the contact bytecode, yes. Just wanted to be clear on that
  
  – flygoing
  20 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  19 mins ago
  

  
  
  
  

add a 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 39 mins ago

answered 47 mins ago

flygoingflygoing

7,560931

share|improve this answer

edited 39 mins ago

answered 47 mins ago

flygoingflygoing

7,560931

answered 47 mins ago

flygoingflygoing

7,560931

answered 47 mins ago

flygoingflygoing

7,560931