Restriction on Write Path to Sequencer in Soneium Minato (testnet) and Soneium (mainnet)

Thank you for building on Soneium.

 

Soneium aims to unleash people's creativity and create a platform where anyone can become a creator. To achieve this, we need to build an environment that not only serves those who have previously engaged with Web3 in their daily lives, but also provides a secure and accessible experience for those who have never interacted with Web3 before. This requires us to balance the openness and permissionless nature that the onchain community values with strict regulatory compliance and adherence to legal requirements necessary for providing stable services.

As part of our compliance efforts, we will transition to an operation that restricts permissionless write-capable RPC paths to the sequencer node. Currently, only a limited number of RPCs can access the sequencer node on both testnet and mainnet. Transaction submission to the network remains open to all users using public and private RPC endpoints, but running a permissionless write-capable node will no longer be supported.

This measure is intended to comply with laws and regulations, fulfill our accountability to regulatory authorities, and protect the continuity of the network. We will minimize the impact while addressing the community's concerns and aim to strengthen decentralization in the future.

Summary of Changes

• Both testnet (Soneium Minato) and mainnet will limit write requests to the sequencer node to those from compliance-approved RPCs only.

• We will announce the compliance-approved RPC endpoints sequentially including the inquiry link to add newly compliance-approved RPCs.

• Access via hopping (relay/proxy) will also be prohibited. DApps using hopping should consider migrating to accessible RPCs.

• Schedule: testnet changes will start on September 19, 2025, and mainnet changes are scheduled for mid-October 2025 (the schedule is subject to change without notice).

Actions Required for Node Operators and dApps Developers

1. Switch to Compliance-Approved RPC Endpoints By obtaining a compliance-approved endpoint. Update the RPC URL of your application/server/infrastructure to the corresponding endpoint

2. Verify Transmission Path Ensure that you are not using self-hosted relays, proxies, or hopping

3. Pre-Verification on Testnet Verify the operation after the switch on the testnet from September 19, 2025

Schedule

• Testnet: Applicable from Friday, September 19, 2025

• Mainnet: Mid-October 2025 (specific date to be announced once confirmed)

*We recommend verification on the testnet before applying to the mainnet to ensure sufficient preparation time.

*The schedule is subject to change without notice. Thank you for your understanding.

We strive to balance network sustainability and compliance with laws and regulations while considering the community. Although this may cause inconvenience in the short term, we are committed to working together to achieve a stronger and more open ecosystem in the medium to long term. We appreciate your understanding and cooperation.