The following information will be added to this page soon:
- links to blast / infura docs
- links to ancillary services on the shadowfork
If you currently operate a dApp or Marketplace on Palm network, there should be little change for you arising from the network transition to Polygon Edge node software. We strongly recommend that testing is carried out to minimise the risk of any issues. This page outlines the changes affecting existing services that support web3 applications running on the Palm network.
The commercial API providers that support Palm network, Infura & Blast API, continue to service Palm network users. Some of the API methods they offer may change or be deprecated as a result of the switch to Polygon Edge - please refer to their their documentation for details as well as check the detailed information in the list of JSON-RPC API changes.
- Infura documentation for Palm network TODO link
- Blast API documentation for Palm network TODO link
Any JSON-RPC API differences should be correctly handled by SDKs that use the API providers, such as web3.js, ethers.js, etc.
There may be some small differences in terms of how they handle the different node providers, e.g. error messages or codes may be slightly different, so your applications should be carefully tested to ensure continued functionality - see Testing for more details.
Core Palm network infrastructure has been fully tested on the updated Palm network and continue to be available on their original URLs. The full list of services can be found here.
For testing your application prior to the hard-fork transition, please refer to Testing for updated links to special "shadow fork" versions of the following services:
- Palm Explorer
- Temporary blockscout instance with missing features http://188.8.131.52:4000/
- Palm Graph