Practical overview
When it fits
Use it when developing or testing an application that needs Polygon PoS bridge contract functionality, or when working directly with the bridge contracts.
Who it is for
- Developers integrating Polygon PoS bridge contracts into dApps.
- Teams building and testing contract-level bridge functionality.
Documented uses
- Install the bridge contract package from NPM.
- Build the repository’s contracts with Hardhat or Foundry.
- Run the documented Hardhat or Foundry tests.
- Set up local Ethereum- and Polygon-like chains for the repository’s deployment workflow.
Requirements & limits
The repository is public and lists a GPL-3.0 license. Its README documents NPM installation. No account or pricing information is provided.
- The repository supports distinct Hardhat and Foundry build and test workflows.
- Hardhat setup calls for NodeJS, NVM, and NPM; Foundry workflows call for Foundry.
- The documented local deployment path uses two chains; its standalone Ganache-and-Bor option lacks Heimdall and therefore validator-dependent state sync and checkpointing.
- The README identifies Infura credentials and a funded deployer key for fork testing.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Build and test the contracts with Hardhat
Set up the repository, compile its contracts, and run the documented Hardhat tests.
Before you start
- NodeJS, NVM, and NPM
- The repository’s required Node version
Steps
Clone the pos-portal repository and enter its directory.
Use NVM to install and select the required Node version.
Install dependencies with npm i and build with npm run build.
Run the tests with npm run test.
Expected outcome
The repository’s Hardhat build and test commands have been run.
Guide limitations
- The README does not specify a completed dApp integration.
- This describes the documented development workflow, not an independent verification of results.
Build and test with Foundry
Generate interfaces, build the contracts, and run the documented Foundry tests.
Before you start
- Foundry
- For fork testing, an Infura API token and a funded deployer private key
Steps
Generate interfaces with npm run generate:interfaces.
Build the contracts with forge build.
For fork testing, configure INFURA_TOKEN and PRIVATE_KEY in the .env file.
Run forge test.
Expected outcome
The documented Foundry build and test commands have been run.
Guide limitations
- The README notes that ForkupgradeMPT.t.sol can take a while; it documents a command to skip that test.
- This describes the repository instructions, not an independent verification of results.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 9 October 2026
- Original website title
- maticnetwork/pos-portal · Official homepage title · retained in its source language