Web3.py
Web3.py Python Library
Introduction
Web3.py is a set of libraries that allow developers to interact with Ethereum nodes using HTTP, IPC, or WebSocket protocols with Python. Phron has an Ethereum-like API available that is fully compatible with Ethereum-style JSON-RPC invocations. Therefore, developers can leverage this compatibility and use the Web3.py library to interact with a Phron python3 as if they were doing so on Ethereum.
In this guide, you'll learn how to use the Web3.py library to send a transaction and deploy a contract on Phron.
Checking Prerequisites
For the examples in this guide, you will need to have the following:
An account with funds. You can get DEV tokens for testing on Phron once every 24 hours from the Phron Faucet
To test out the examples in this guide on Phron, you will need to have your own endpoint and API key, which you can get from one of the supported Endpoint Providers
NoteThe examples in this guide assume you have a MacOS or Ubuntu 22.04-based environment and will need to be adapted accordingly for Windows.
Create a Python Project
To get started, you can create a directory to store all of the files you'll be creating throughout this guide:
For this guide, you'll need to install the Web3.py library and the Solidity compiler. To install both packages, you can run the following command:
Setup Web3.py with Phron
Throughout this guide, you'll be creating a bunch of scripts that provide different functionalities, such as sending a transaction, deploying a contract, and interacting with a deployed contract. In most of these scripts, you'll need to create a Web3.py provider to interact with the network.
To configure your project for Phron, you will need to have your own endpoint and API key, which you can get from one of the supported Endpoint Providers.
To create a provider, you can take the following steps:
Import the
web3
libraryCreate the
web3
provider using theWeb3(Web3.HTTPProvider())
method and providing the endpoint URL
Save this code snippet, as you'll need it for the scripts that are used in the following sections.
Send a Transaction
During this section, you'll be creating a couple of scripts. The first one will be to check the balances of your accounts before trying to send a transaction. The second script will actually send the transaction.
You can also use the balance script to check the account balances after the transaction has been sent.
Check Balances Script
You'll only need one file to check the balances of both addresses before and after the transaction is sent. To get started, you can create a balances.py
file by running:
Next, you will create the script for this file and complete the following steps:
Set up the Web3 provider
Define the
address_from
andaddress_to
variablesGet the balance for the accounts using the
web3.eth.get_balance
function and format the results using theweb3.from_wei
To run the script and fetch the account balances, you can run the following command:
If successful, the balances for the origin and receiving address will be displayed in your terminal in ETH.
Send Transaction Script
You'll only need one file for executing a transaction between accounts. For this example, you'll be transferring 1 DEV token from an origin address (from which you hold the private key) to another address. To get started, you can create a transaction.py
file by running:
Next, you will create the script for this file and complete the following steps:
Add imports, including Web3.py and the
rpc_gas_price_strategy
, which will be used in the following steps to get the gas price used for the transactionSet up the Web3 provider
Define the
account_from
, including theprivate_key
, and theaddress_to
variables. The private key is required to sign the transaction. Note: This is for example purposes only. Never store your private keys in a Python fileUse the Web3.py Gas Price API to set a gas price strategy. For this example, you'll use the imported
rpc_gas_price_strategy
Create and sign the transaction using the
web3.eth.account.sign_transaction
function. Pass in thenonce
gas
,gasPrice
,to
, andvalue
for the transaction along with the sender'sprivate_key
. To get thenonce
you can use theweb3.eth.get_transaction_count
function and pass in the sender's address. To predetermine thegasPrice
you'll use theweb3.eth.generate_gas_price
function. For thevalue
, you can format the amount to send from an easily readable format to Wei using theweb3.to_wei
functionUsing the signed transaction, you can then send it using the
web3.eth.send_raw_transaction
function and wait for the transaction receipt by using theweb3.eth.wait_for_transaction_receipt
function
To run the script, you can run the following command in your terminal:
If the transaction was succesful, in your terminal you'll see the transaction hash has been printed out.
You can also use the balances.py
script to check that the balances for the origin and receiving accounts have changed. The entire workflow would look like this:
Deploy a Contract
The contract you'll be compiling and deploying in the next couple of sections is a simple incrementer contract, arbitrarily named Incrementer.sol
. You can get started by creating a file for the contract:
Next, you can add the Solidity code to the file:
The constructor
function, which runs when the contract is deployed, sets the initial value of the number variable stored on-chain (the default is 0
). The increment
function adds the _value
provided to the current number, but a transaction needs to be sent, which modifies the stored data. Lastly, the reset
function resets the stored value to zero.
NoteThis contract is a simple example for illustration purposes only and does not handle values wrapping around.
Compile Contract Script
In this section, you'll create a script that uses the Solidity compiler to output the bytecode and interface (ABI) for the Incrementer.sol
contract. To get started, you can create a compile.py
file by running:
Next, you will create the script for this file and complete the following steps:
Import the
solcx
packageOptional - If you haven't already installed the Solidity compiler, you can do so with by using the
solcx.install_solc
functionCompile the
Incrementer.sol
function using thesolcx.compile_files
functionExport the contract's ABI and bytecode
NoteIf you see an error stating that
Solc is not installed
, uncomment step 2 described in the code snippet.
Deploy Contract Script
With the script for compiling the Incrementer.sol
contract in place, you can then use the results to send a signed transaction that deploys it. To do so, you can create a file for the deployment script called deploy.py
:
Next, you will create the script for this file and complete the following steps:
Add imports, including Web3.py and the ABI and bytecode of the
Incrementer.sol
contractSet up the Web3 provider
Define the
account_from
, including theprivate_key
. The private key is required to sign the transaction. Note: This is for example purposes only. Never store your private keys in a Python fileCreate a contract instance using the
web3.eth.contract
function and passing in the ABI and bytecode of the contractBuild a constructor transaction using the contract instance and passing in the value to increment by. For this example, you can use
5
. You'll then use thebuild_transaction
function to pass in the transaction information including thefrom
address and thenonce
for the sender. To get thenonce
you can use theweb3.eth.get_transaction_count
functionSign the transaction using the
web3.eth.account.sign_transaction
function and pass in the constructor transaction and theprivate_key
of the senderUsing the signed transaction, you can then send it using the
web3.eth.send_raw_transaction
function and wait for the transaction receipt by using theweb3.eth.wait_for_transaction_receipt
function
To run the script, you can enter the following command into your terminal:
If successful, the contract's address will be displayed in the terminal.
Read Contract Data (Call Methods)
Call methods are the type of interaction that don't modify the contract's storage (change variables), meaning no transaction needs to be sent. They simply read various storage variables of the deployed contract.
To get started, you can create a file and name it get.py
:
Then you can take the following steps to create the script:
Add imports, including Web3.py and the ABI of the
Incrementer.sol
contractSet up the Web3 provider
Define the
contract_address
of the deployed contractCreate a contract instance using the
web3.eth.contract
function and passing in the ABI and address of the deployed contractUsing the contract instance, you can then call the
number
function
To run the script, you can enter the following command in your terminal:
If successful, the value will be displayed in the terminal.
Interact with Contract (Send Methods)
Send methods are the type of interaction that modify the contract's storage (change variables), meaning a transaction needs to be signed and sent. In this section, you'll create two scripts: one to increment and one to reset the incrementer. To get started, you can create a file for each script and name them increment.py
and reset.py
:
Open the increment.py
file and take the following steps to create the script:
Add imports, including Web3.py and the ABI of the
Incrementer.sol
contractSet up the Web3 provider
Define the
account_from
, including theprivate_key
, thecontract_address
of the deployed contract, and thevalue
to increment by. The private key is required to sign the transaction. Note: This is for example purposes only. Never store your private keys in a Python fileCreate a contract instance using the
web3.eth.contract
function and passing in the ABI and address of the deployed contractBuild the increment transaction using the contract instance and passing in the value to increment by. You'll then use the
build_transaction
function to pass in the transaction information including thefrom
address and thenonce
for the sender. To get thenonce
you can use theweb3.eth.get_transaction_count
functionSign the transaction using the
web3.eth.account.sign_transaction
function and pass in the increment transaction and theprivate_key
of the senderUsing the signed transaction, you can then send it using the
web3.eth.send_raw_transaction
function and wait for the transaction receipt by using theweb3.eth.wait_for_transaction_receipt
function
To run the script, you can enter the following command in your terminal:
If successful, the transaction hash will be displayed in the terminal. You can use the get.py
script alongside the increment.py
script to make sure that value is changing as expected:
Next you can open the reset.py
file and take the following steps to create the script:
Add imports, including Web3.py and the ABI of the
Incrementer.sol
contractSet up the Web3 provider
Define the
account_from
, including theprivate_key
, and thecontract_address
of the deployed contract. The private key is required to sign the transaction. Note: This is for example purposes only. Never store your private keys in a Python fileCreate a contract instance using the
web3.eth.contract
function and passing in the ABI and address of the deployed contractBuild the reset transaction using the contract instance. You'll then use the
build_transaction
function to pass in the transaction information including thefrom
address and thenonce
for the sender. To get thenonce
you can use theweb3.eth.get_transaction_count
functionSign the transaction using the
web3.eth.account.sign_transaction
function and pass in the reset transaction and theprivate_key
of the senderUsing the signed transaction, you can then send it using the
web3.eth.send_raw_transaction
function and wait for the transaction receipt by using theweb3.eth.wait_for_transaction_receipt
function
To run the script, you can enter the following command in your terminal:
If successful, the transaction hash will be displayed in the terminal. You can use the get.py
script alongside the reset.py
script to make sure that value is changing as expected:
This tutorial is for educational purposes only. As such, any contracts or code created in this tutorial should not be used in production.The information presented herein has been provided by third parties and is made available solely for general information purposes. Phron does not endorse any project listed and described on the Phron Doc Website (https://docs.Phron.ai/). Phron does not warrant the accuracy, completeness or usefulness of this information. Any reliance you place on such information is strictly at your own risk. Phron disclaims all liability and responsibility arising from any reliance placed on this information by you or by anyone who may be informed of any of its contents. All statements and/or opinions expressed in these materials are solely the responsibility of the person or entity providing those materials and do not necessarily represent the opinion of Phron. The information should not be construed as professional or financial advice of any kind. Advice from a suitably qualified professional should always be sought in relation to any particular matter or circumstance. The information herein may link to or integrate with other websites operated or content provided by third parties, and such other websites may link to this website. Phron has no control over any such other websites or their content and will have no liability arising out of or related to such websites or their content. The existence of any such link does not constitute an endorsement of such websites, the content of the websites, or the operators of the websites. These links are being provided to you only as a convenience and you release and hold Phron harmless from any and all liability arising from your use of this information or the information provided by any third-party website or service.
Last updated