5.9.0.md

RPC Data and Endpoints (v5.9.0)

With the v5.9.0 release, we have reverted the EVM RPC methods to their original specifications, ensuring strict EVM compliance. At the same time, we continue to support developers who require both synthetic and EVM data through updated Sei-specific methods.

Summary of Changes:

• EVM RPC methods:

  • eth_getBlockByNumber, eth_getBlockReceipts, and eth_getLogs will now return only EVM-specific data.
  • Synthetic transaction hashes (Tendermint hashes prefixed with '0x') can still be queried using eth_getTransactionReceipt. However, this data is only available when explicitly queried with the synthetic hash and will not appear in any other EVM RPC responses by default.

• Sei-Specific RPC methods:

  • The Sei-specific methods (sei_getBlockByNumber, sei_getBlockReceipts, and sei_getLogs) will continue to return both EVM and synthetic Tendermint events. These custom methods are served over the same EVM RPC endpoint, ensuring a unified interface while allowing access to both EVM and synthetic data.
  • These methods will also surface CW20 and CW721 events when applicable. Additional testing is recommended for transactions without a pointer.

Actions Required:

• If your application relies on the existing synthetic events: To maintain a complete view of the chain, you must:

  • Switch to the Sei-specific methods (sei_getBlockByNumber, sei_getBlockReceipts, and sei_getLogs), or
  • Implement a custom solution that combines both EVM and Tendermint RPC data.

• If your application continues to use solely on the EVM RPC methods:

  • ⚠️You will no longer receive complete or accurate data.

---

Note: For a full breakdown of the changes, please refer to the previous announcement.