Contracts Deployment
Getting started contract deployment in Patex Network
This tutorial teaches you the basics of Patex development. Patex is EVM equivalent, meaning we run a slightly modified version of the same geth you run on mainnet. Therefore, the differences between Patex development and Ethereum development are minor.
Patex Network Description
Network name
Patex Network
RPC URL
Chain ID
789
Currency symbol
ETH
Block explorer URL
Network name
Patex Sepolia Testnet
RPC URL
Chain ID
471100
Currency symbol
ETH
Block explorer URL
# Patex endpoint URL
Network choice
For development purposes we recommend you use either a local development node on Patex Sepolia Testnet. That way you don't need to spend real money. If you need ETH on Patex Sepolia for testing purposes, you can use this faucet.
# Interacting with Patex contracts
We have Hardhat's Greeter contract on Patex Sepolia, at address 0x317ccBB804c1f104b0fA1495B625c87F66091745. You can verify your development stack configuration by interacting with it.
As you can see in the different development stacks below, the way you deploy contracts and interact with them on Patex is almost identical to the way you do it with L1 Ethereum. The most visible difference is that you have to specify a different endpoint (of course).
# Development stacks
# Best practices
It is best to start development with the EVM provided by the development stack. Not only is it faster, but such EVMs often have extra features, such as the ability to log messages from Solidity or a graphical user interface.
After you are done with that development, debug your decentralized application using either the Sepolia test network. This lets you debug parts that are Patex specific such as calls to bridges to transfer assets between layers.
Only when you have a version that works well on a test network should you deploy to the production network, where every transaction has a cost.
Contract source verification
You don't have to upload your source code to block explorers, but it is a good idea. On the test network it lets you issue queries and transactions from the explorer's user interface. On the production network it lets users know exactly what your contract does, which is conducive to trust.
Just remember, if you use the Patexscan API, you need one API key for Patex and a separate one for Patex Sepolia.
Last updated