Create a smart contract
A transaction that creates a new smart contract instance. After the contract is created you can get the new contract ID by requesting the receipt of the transaction. To create the solidity smart contract, you can use remix or another Solidity compiler. After you have the hex-encoded bytecode of the smart contract you need to store that on a file using the Hedera File Service. Then you will create the smart contract instance that will run the bytecode stored in the Hedera file, referenced by file ID. Alternatively, you can use the ContractCreateFlow()
API to create the file storing the bytecode and contract in a single step.
The constructor will be executed using the given amount of gas, and any unspent gas will be refunded to the paying account. Constructor inputs are passed in the constructorParameters
.
If this constructor stores information, it is charged gas to store it. There is a fee in hbars to maintain that storage until the expiration time, and that fee is added as part of the transaction fee.
Solidity Support
The latest version of Solidity is supported on all networks (v0.8.9).
Smart Contract State Size and Gas Limits
The max contract key value pairs are 16,384,000 (~100 MB). The system gas throttle is 15 million gas per second. Contract call and contract create are throttled at 8 million gas per second.
Admin Key Support for Contracts
With HIP-904, contracts now support Admin Key settings. Set an Admin Key during the ContractCreate
transaction to manage and update token properties. For frictionless-airdrop enabled contracts, set maxAutoAssociations
during the ContractCreate
transaction, ensuring that balance and associations can be managed with a valid Admin Key.
Transaction Signing Requirements
The client operator account is required to sign the transaction.
The admin key, if specified.
The key of the autorenewal account, if specified.
Transaction Fees
Please see the transaction and query fees table for the base transaction fee.
Please use the Hedera fee estimator to estimate the cost of your transaction fee.
Smart Contract Properties
Field | Description |
---|---|
Admin Key | Sets the state of the instance and its fields can be modified arbitrarily if this key signs a transaction to modify it. If this is null, then such modifications are not possible, and there is no administrator that can override the normal operation of this smart contract instance. Note that if it is created with no admin keys, then there is no administrator to authorize changing the admin keys, so there can never be any admin keys for that instance. |
Gas | The gas to run the constructor. |
Initial Balance | The initial number of hbars to put into the cryptocurrency account associated with and owned by the smart contract. |
Byte Code File | The file containing the hex encoded smart contract byte code. |
Staked ID | The node account or node ID to which this contract account is staking to. See HIP-406. Note: Accounts cannot stake to contract accounts. This will fixed in a future release. |
Decline Rewards | Some contracts may choose to stake their hbars and decline receiving rewards. If set to true, the contract account will not earn rewards when staked. The default value is false. See HIP-406. |
Auto Renew Account ID | An account to charge for auto-renewal of this contract. If not set, or set to an account with zero hbar balance, the contract's own hbar balance will be used to cover auto-renewal fees. |
Auto Renew Period | The period that the instance will charge its account every this many seconds to renew. |
Automatic Token Associations | The maximum number of tokens that this contract can be automatically associated with (i.e., receive air-drops from). |
Constructor Parameters | The constructor parameters to pass. |
Memo | The memo to be associated with this contract. (max 100 bytes) |
ContractCreateFlow()
ContractCreateFlow()
The ContractCreateFlow()
streamlines the creation of a contract by taking the bytecode of the contract and creating the file on Hedera to store the bytecode for you.
First, a FileCreateTransaction()
will be executed to create a file on Hedera to store the specified contract bytecode. Then, the ContractCreateTransaction()
will be executed to create the contract instance on Hedera. Lastly, a FileDeleteTransaction()
will be executed to remove the file.
The response will return the contract create transaction information like the new contract ID. You will not get the ID of the file that was created that stored your contract bytecode. If you would like to know the file ID of your contract bytecode, you can create a file and use the ContractCreateTransaction()
API directly.
Methods
Note: Please refer to ContractCreateTransaction() for a complete list of applicable methods.
Method | Type |
---|---|
| byte |
| String |
| ByteString |
| int |
ContractCreateTransaction()
ContractCreateTransaction()
Creates a smart contract instance using the file ID of the contract bytecode.
Constructor | Description |
---|---|
| Initializes the ContractCreateTransaction() object |
Methods
Method | Type | Requirement |
---|---|---|
| long | Required |
| Required | |
| Hbar | Optional |
| Key | Optional |
| byte [ ] | Optional |
| ContractFunctionParameters | Optional |
| String | Optional |
| long | Optional |
| AccountId | Optional |
| boolean | Optional |
| AccountId | Optional |
| Duration | Optional |
| int | Optional |
Get transaction values
Method | Type | Requirement |
---|---|---|
| Key | Optional |
| long | Optional |
| Hbar | Optional |
| FileId | Optional |
| AccountId | Optional |
| ByteString | Optional |
| String | Optional |
| boolean | Optional |
| long | Optional |
| AccountId | Optional |
| AccountId | Required |
| Duration | Required |
Last updated