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

Smoothness of finite-dimensional functional calculus

Test whether all array elements are factors of a number

What would happen to a modern skyscraper if it rains micro blackholes?

Email Account under attack (really) - anything I can do?

Why don't electron-positron collisions release infinite energy?

Why Is Death Allowed In the Matrix?

Schoenfled Residua test shows proportionality hazard assumptions holds but Kaplan-Meier plots intersect

can i play a electric guitar through a bass amp?

Do I have a twin with permutated remainders?

Did Shadowfax go to Valinor?

How is it possible to have an ability score that is less than 3?

Why doesn't H₄O²⁺ exist?

Theorems that impeded progress

Modeling an IP Address

Why does Kotter return in Welcome Back Kotter?

The use of multiple foreign keys on same column in SQL Server

Pattern match does not work in bash script

What do the dots in this tr command do: tr .............A-Z A-ZA-Z <<< "JVPQBOV" (with 13 dots)

Can a Warlock become Neutral Good?

Writing rule stating superpower from different root cause is bad writing

Can I make popcorn with any corn?

Have astronauts in space suits ever taken selfies? If so, how?

Dragon forelimb placement

Collect Fourier series terms



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?










share|improve this question


























    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?










    share|improve this question
























      2












      2








      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?










      share|improve this question














      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













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 27 at 19:41









      user311703user311703

      1846




      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

























          • 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











          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


















          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















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          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

























          • 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















          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

























          • 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













          5












          5








          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















          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














          share|improve this answer



          share|improve this answer








          edited Mar 27 at 20:20

























          answered Mar 27 at 20:13









          flygoingflygoing

          7,670931




          7,670931












          • 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

















          • 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
















          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





          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





          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




          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





          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




          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





          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




          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





          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

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Ethereum Stack Exchange!


          • 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.




          draft saved


          draft discarded














          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















          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







          Popular posts from this blog

          Adding axes to figuresAdding axes labels to LaTeX figuresLaTeX equivalent of ConTeXt buffersRotate a node but not its content: the case of the ellipse decorationHow to define the default vertical distance between nodes?TikZ scaling graphic and adjust node position and keep font sizeNumerical conditional within tikz keys?adding axes to shapesAlign axes across subfiguresAdding figures with a certain orderLine up nested tikz enviroments or how to get rid of themAdding axes labels to LaTeX figures

          Luettelo Yhdysvaltain laivaston lentotukialuksista Lähteet | Navigointivalikko

          Gary (muusikko) Sisällysluettelo Historia | Rockin' High | Lähteet | Aiheesta muualla | NavigointivalikkoInfobox OKTuomas "Gary" Keskinen Ancaran kitaristiksiProjekti Rockin' High