Creating and sending transactions
You can send signed transactions using the
eth_sendRawTransaction JSON-RPC API method.
Signed transactions can be simple value transfers, contract creation, or contract invocation. Set the maximum transaction fee for transactions using the
--rpc-tx-feecap CLI option.
To accept signed transactions from remote connections, set the API listening host to
Use client libraries to create and send a signed raw transaction to transfer Ether and create a smart contract.
Do not use the accounts from the examples on Mainnet or any public network except for testing. The private keys are displayed which means the accounts are not secure.
All accounts and private keys in the examples are from the
dev.json genesis file in the
Setting the listening host to
0.0.0.0 exposes the API service connection on your node to any remote connection. In a production environment, ensure you are using a firewall to avoid exposing your node to the internet.
| || |
|Invokes contract function locally||Broadcasts to the network|
|Does not change state of blockchain||Updates the blockchain (for example, transfers ether between accounts)|
|Does not consume gas||Requires gas|
|Returns the value of a contract function available immediately||Returns transaction hash only. A block might not include all possible transactions (for example, if the gas price is too low).|