cerc-io/solidity
16
0
Fork 0
mirror of https://github.com/ethereum/solidity synced 2023-10-03 13:03:40 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Clarify contract creation transaction

Browse Source 
The change clarifies how contracts are deployed. The docs state that it's a transaction sent to `0` address (which is incorrect), the PR changes that to emphasize that the recipient is not set.
This commit is contained in:
Tomasz Drwięga 2018-10-09 08:58:05 +02:00 committed by GitHub
parent 15e4a5fc30
commit 88d10b37d7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/introduction-to-smart-contracts.rst
View File

@ -332,14 +332,15 @@ Transactions
============
A transaction is a message that is sent from one account to another
account (which might be the same or the special zero-account, see below).
account (which might be the same or empty, see below).
It can include binary data (which is called "payload") and Ether.
If the target account contains code, that code is executed and
the payload is provided as input data.
If the target account is the zero-account (the account with the
address ``0``), the transaction creates a **new contract**.
If the target account is not set (the transaction does not have
a recipient or the recipient is set to ``null``), the transaction
creates a **new contract**.
As already mentioned, the address of that contract is not
the zero address but an address derived from the sender and
its number of transactions sent (the "nonce"). The payload