[Announcement] PlatON Network v1.5.0 Upgrade Notice

PlatON Global Validating
#1

[Announcement] PlatON Network v1.5.0 Upgrade Notice

Dear PlatON Nodes and Ecosystem Partners:

We are pleased to announce that the PlatON mainnet will undergo a governance upgrade to version 1.5.0 between March 27, 2025 and April 11, 2025. This upgrade will implement Phase 4 of PIP-7, introducing multiple new transaction types while optimizing scalability and security to provide stronger support for ecosystem development.

Key Upgrade Highlights

The PlatON 1.5.0 upgrade includes 3 major updates and 3 optimizations:

1. Implementation of PIP-7 Phase 4

According to the PIP-7 proposal, the PlatON mainnet has successfully switched to the new ChainID (210425) and has smoothly transitioned through three minor versions.

To completely isolate the impact of the old ChainID (100), this upgrade will discontinue support for the old ChainID. After the upgrade, the PlatON network will no longer support transaction signatures with ChainID 100.

2. Compatibility with Ethereum’s Berlin and London Upgrades

To maintain full compatibility with the Ethereum ecosystem, PlatON version 1.5.0 will be compatible with the Ethereum Berlin and London upgrades, while also supporting transaction types such as EIP-2718, EIP-2930, and EIP-1559.

This will lay a more solid foundation for new features and ecosystem projects on PlatON.

3. Contract Call Invocation Adjustment

With the in-depth discussion of the Abstract Account (AA) concept, the original EVM chain’s virtual machine did not strictly check whether the sender address was a contract during Call invocation, posing serious security risks (please refer to PR #23303 for details).

Therefore, PlatON will prohibit using contract addresses as the sender in Call invocations in this version.

After the upgrade, PlatON will no longer support using contract addresses as senders for transactions or Call invocations.

4. Standardized Startup Flags

To standardize interface parameters, this version removes some deprecated startup parameters and updates new parameter flags.

The specific changes are as follows:

Module Before Change After Change
rpc rpc http
rpcaddr http.addr
rpcport http.port
rpccorsdomain http.corsdomain
rpcvhosts http.vhosts
rpcapi http.api
ws wsaddr ws.addr
wsport ws.port
wsorigins ws.origins
wsapi ws.api

5. Transaction Receipt Retention

To enhance user experience and meet the needs of ecosystem projects for transaction receipt data, based on the premise that receipt storage does not affect disk space, this version will support storing transaction receipt information.

The fast synchronization mode will retain transaction receipts, and the gc mode will no longer delete transaction receipts.

6. Increased Validator Capacity

To enhance the decentralization and security of the network, the maximum number of validators (maxValidators) on PlatON will be adjusted from 201 to 225.

Upgrade Impact

For Nodes

  • ChainID

    The new version only supports ChainID (210425). Old nodes with ChainID (100) will not be able to validate and execute transactions with the new ChainID (210425), leading to these old nodes stopping synchronization with the main chain blocks.

    Since the previous three versions have already defaulted to switching to the new ChainID (210425), this upgrade will have minimal impact on node operations.

  • Startup Parameter Adjustment

    This upgrade removes some deprecated startup parameters. Nodes using old startup parameters need to replace them with new parameters, such as changing rpcaddr to http.addr. Detailed information can be obtained via the platon --help command.

For dApps

  • Due to the discontinuation of support for ChainID (100), DApps need to confirm if their ChainID has been updated.

    After the upgrade, PlatON will no longer support transactions signed with ChainID 100. For applications still using ChainID 100, they need to update to ChainID (210425) as soon as possible to ensure normal business operation.

    For contracts that have hard-coded ChainID logic, redeploy a new contract with ChainID 210425 and migrate data from the old contract to the new one.

    For applications using ChainID at the application layer (off-chain), adjust the ChainID in the application layer code logic.

  • Confirm if your application uses a contract address as the from address in call invocations.

    After the upgrade, PlatON will no longer support using a contract address as the sender for transactions or call invocations.

    If an application uses a contract address as the from address in a call invocation, the RPC call will immediately return a “sender not an eoa” error, causing the application to fail to operate normally.

    If there is no such usage, no adjustments or modifications are needed; the application can continue running.

    If there is any incorrect use of a contract address as the from address in call invocations, simply replace it with an EOA address that is not a contract.

  • Applications need to adapt to the London and Berlin upgrades.

    To maintain compatibility with Ethereum, this new version adapts to the Ethereum London and Berlin upgrades. After the completion of the PlatON 1.5.0 upgrade, EIP-2718, EIP-2930, EIP-1559, and other improvement proposals will be enabled.

    Applications should check:

    （1）The transaction receipt after the upgrade will include type and effectiveGasPrice fields.

    （2）The block information after the upgrade will include the baseFeePerGas field.

    If the application uses Ethereum's SDK, no modification is required for adaptation. If using platon-sdk or self-developed SDK, you need to adapt to the above content.

Upgrade Instructions

Since this is a major version update, all nodes must upgrade to the new version!

Timeline

  • Proposal Start: March 27, 2025, 11:00 UTC+8
  • Voting Deadline: April 11, 2025, 11:00 UTC+8 （estimate ）

Please assist in completing the upgrade during the proposal period. Thank you for your support!

Upgrade Operations

  • Validators: Upgrade + vote on-chain or declare version.
  • Non-validators: Upgrade only.

Refer to the " PlatON Mainnet Node Upgrade Guide-v1.5.0." for detailed instructions.

Version Details

  • Release: v1.5.0
  • Commit-ID: 7b22c9351d5ff63a9ac8d143e75f9044914077f7

We believe this upgrade will significantly enhance PlatON’s functionality and security. Thank you for your continued support!

The PlatON Team

#2
#3

Is this the long-awaited update that was written about here earlier?

#4

Where i can read full changes list of new update?

#5

There is no more complete description, if needed you can you can check the Github code Releases · PlatONnetwork/PlatON-Go · GitHub

1 个赞
#6

Last release was 1.4.4

#7

Same question, where is 1.5.0?
The link is to 1.4.4.

#8

Sorry，1.5.0 is being upgraded in a vote, and will be the latest version when the vote passes.

image
image1364×815 57 KB