JSON-RPC API changes
There are some important API changes arising as a result of changing the node software from Hyperledger Besu to Polygon Edge. The majority of API calls are unchanged and should return the same results, however it's recommended that testing is carried out on your application to ensure that there are no unexpected issues arising from the switch to the Edge client.
The table below lists the API methods available with Polygon Edge.
Method | Comment |
---|---|
DEBUG methods:
| These should be used in place of any existing usage of TRACE methods |
ETH methods:
|  |
NET methods:
|  |
TXPOOL methods:
|  |
WEB3 methods:
|  |

The table below lists methods that are not available in Polygon Edge. Some have never been applicable to Palm network (such as Proof of Work methods), so are unlikely to be an issue.
Alternatives for the most commonly-used methods such as the TRACE are outlined below where applicable.
If there are any missing RPC methods that are essential for your application to be retained or replaced, please get in touch.
Method | Comment / Alternative |
---|---|
ADMIN methods:
| This info can be obtained direct from the polygon-edge client |
Subset of DEBUG methods:
| No alternatives. |
Subset of ETH methods:
| Majority are not applicable to Palm network (e.g. proof-of-work methods) |
IBFT methods
| Primarily used for managing validators on Palm network, these are replaced by new contract-based methods for managing validators |
MINER methods
| Not applicable to Palm network |
NET methods
| No alternatives. |
PLUGINS methods
| Applicable to besu software only |
TRACE methods
| DEBUG methods should be used as alternatives:
|
TXPOOL methods
| Applicable to besu software only |

The following methods are available in Edge, but may have different interpretations/calculations of data or have additional parameters
Method | Difference |
---|---|
eth_gasPrice |
This may give rise to slightly different results at particular blocks however overall, the data is fairly consistent. |