Conflux (Coral) v3.0.2 Upgrade Announcement

This upgrade is mainly to solve the problems below:

Bug Fixes

RPC

Fix eth_call coinbase opcode: Fixed bug where eth_call coinbase opcode was using a random address instead of the correct one

Others

Fix PoS reward reexecution: Fixed issue where PoS reward in DB was not checked if it’s on pivot for reexecution

RPC Changes

New RPC Endpoints

  • debug_blockProperties: Added a custom eSpace RPC endpoint to return extra block property information for all transactions in an eSpace block. This is useful for services that require verification of transaction execution, as transactions within a single Conflux eSpace block may have different block contexts (coinbase, timestamp, difficulty) during execution. See documentation for details.

RPC Improvements

  • Log timestamp support: Added blockTimestamp field to eSpace log object (for methods like eth_getLogs and eth_getFilterLogs)

  • Block number type improvements:
    Renamed RPC type BlockNumber to BlockId for better precision
    RPC type BlockNumber now supports block hash case

  • Log format optimization: Optimized bytes log format from number array to hex string

  • Fix parity trace compatibility: Fixed parity trace error and result structure incompatibility issue

  • Fix block retrieval errors: Use new defined error types instead of strings for block retrieve methods

  • RPC configuration: Added configuration options for eSpace RPCs

Performance Improvements

  • Storage optimization: Optimized to only read from storage if entry is not occupied

  • eth_feeHistory: Optimized to only read header instead of full block for base price calculation

Infrastructure & Dependencies

Memory Management

  • jemalloc upgrade: Switched from jemallocator to tikv-jemallocator

  • Memory profiling: Added memory and CPU pprof support for profiling

Download

Download “Conflux v3.0.2” here: https://github.com/Conflux-Chain/conflux-rust/releases/tag/v3.0.2

I am a node operator/miner, what do I need to do?

If you have a running node, you need to

  • Suspend the running operation of the node

  • Replace the executable file named “conflux” in the run directory of the original node program with the Conflux executable file of the Conflux v3.0.2 node program.

  • Restart the operation of the node

If you start a new node, you can download the latest version of v3.0.2 and run it.

What will happen if I do not upgrade the nodes or refuse to upgrade?

This upgrade aims to improve node stability, it’ll be fine if you do not upgrade to this version.

Thanks to our community for your support!

A sincere thank you to the Conflux community and all the developers in the Conflux ecosystem. Thank you for your hard work, thoughts, and contributions. To a better future!

1 Like