Development Framework Integration

Seamless Integration with Development Frameworks
Phalcon Fork can be integrated with popular development frameworks.

Get Acess Key and Fork RPC ID

The first step is getting the API access key (Fork_API_ACCESSS_KEY) and the Fork RPC ID (FORK_RPC_ID). The API access key is obtained in the Account card of the Forks Dashboard. For instance, the Fork RPC ID is the string starting from 901fe.
The API access key and the Fork RPC ID


Add the Phalcon network to hardhat.config.js, by placing the fork's RPC in the URL.
/** @type import('hardhat/config').HardhatUserConfig */
module.exports = {
networks: {
hardhat: {
goerli: {
url: "${YOUR_KEY}",
accounts: ['${PRIVATE_KEY}']
phalcon: {
url: "",
accounts: ['${PRIVATE_KEY}']
solidity: "0.8.17",
When executing the deployment scripts, specify the network as phalcon, for example:
npx hardhat run scripts/deploy.js --network phalcon


Phalcon Fork can be easily integrated into Foundry.
  • Using rpc-url parameter
forge create --rpc-url [FORK_RPC] --private-key %private-key% src/Contract.sol:TokenSwap
  • Add eth_rpc_url to the foundry.toml.
When executing without specifying an rpc-url, it will use Fork by default.
eth_rpc_url = [FORK_RPC]
  • Add Phalcon Fork to the rpc_endpoints section in foundry.toml
phalcon = [FORK_RPC]
When executing, use Fork by specifying the rpc-url.
forge create --rpc-url phalcon --private-key %private-key% src/Contract.sol:TokenSwap


  • Sign the transaction in MetaMask, and check the network to ensure it is being executed on the Fork
  • View the transaction in MetaMask and wait for the status change from Pending to Confirmed.
  • Check the transaction execution details in Phalcon Explorer


Please refer to this manual to see how to add a Fork into MetaMask.