Deploying contracts
Available development stacks
Since PGN is built with OP Stack (opens in a new tab), you can utilize one of the following development stacks. We don’t currently have a strong recommendation on which one you use.
| Development stack | Description |
|---|---|
| ApeWorX (opens in a new tab) | ApeWorX is a smart contract development tool for Pythonistas, Data Scientists, and Security Professionals |
| Brownie (opens in a new tab) | Brownie is a Python-based development and testing framework for smart contracts targeting the Ethereum Virtual Machine. |
| Foundry (opens in a new tab) | Foundry is a smart contract development toolchain that manages your dependencies, compiles your project, runs tests, deploys, and lets you interact with the chain from the command-line and via Solidity scripts. |
| Hardhat (opens in a new tab) | Hardhat is a development environment for Ethereum software that consists of different components for editing, compiling, debugging and deploying your smart contracts and dApps. |
| Remix (opens in a new tab) | Remix IDE is used for the entire journey of smart contract development by users at every knowledge level. It requires no setup, fosters a fast development cycle, and has a rich set of plugins with intuitive GUIs. |
| Truffle (opens in a new tab) | Truffle is a world class development environment, testing framework, and asset pipeline for blockchains using Ethereum, aiming to make life as a developer easier. |
| Waffle (opens in a new tab) | Waffle is a library based on Truffle that makes writing and testing smart contracts simpler, sweeter, and faster. |
Configuring your development stack
Make sure to configure these tools with the correct chain ID and RPC URL to deploy smart contracts to PGN’s mainnet and testnet. See our network and contract details page for more information.
Request for contributions
If you are interested in contributing to PGN, we’d love to include more specific tutorials that show how to set up, verify, and deploy dApps using these different development stacks.
Please feel free to contribute via our docs GitHub (opens in a new tab), which is linked to from the “Edit this page” button on the right side of this page.