
web3.js v3 is worth paying attention to, but don’t mistake familiarity with the interface for a painless upgrade. This week’s focus is the developer ecosystem beginning to reunite. ① On October 7 (Beijing Time), Solana Developers officially introduced web3.js v3. Be clear on the date: GitHub’s v3.0.0 release, converted to Beijing Time, was on October 2; the recent development is the official announcement, not the initial code release. ② The new version retains the familiar class-based API while under the hood integrating with Kit. The goal is to align legacy API usage patterns with the new toolchain, sharing more foundational capabilities and reducing long-term fragmentation costs across the ecosystem. ③ New wallet adapters have also emerged, but a “major version” inherently requires careful review of migration differences. Familiar call patterns do not guarantee that all old types, behaviors, and dependencies will remain unchanged. ④ When migrating, cover wallet connection, signing, transaction serialization, RPC, and error handling. The SDK being labeled v3 does not automatically imply full end-to-end support for all new transaction formats. My own assessment: Unifying developer tools is a slow-burning but significant ecosystem benefit. It may lower costs for launching new projects and maintaining existing ones, but it cannot replace thorough migration testing. I’m willing to monitor and experiment—but I won’t upgrade production environments to the new version without proper regression testing. @Solana_zh @solana @solana_devs
