Real data, no exaggeration 👉 July 7, 2026 API snapshot + official PI core team update 🆙

Environment → stellar-core version → current_protocol_version
→ Mainnet: 24.1.0 → 24
→ Testnet (main test network): 26.1.0 → 26
→ Testnet 2: 24.1.0 → 24
→ Your running Pi Node software: community-v1.0-p25.2.2 / p26.0.1

Simple way to understand: School curriculum vs textbook

→ current_protocol_version + stellar-core version = official school curriculum
This only changes when there is a nationwide large-scale teaching content reform
→ Version names like p24.1.0 / p25.2.2 / p26.0.1 = textbook
Same curriculum, but publishers can update textbooks anytime, fix errors, add new exercises, without waiting for the whole curriculum to change

How this applies to Pi

→ If the "school board" hasn't approved a new curriculum, the curriculum code stays at 24
→ Pi has released an updated textbook, version 25.2, meaning bug fixes and new features are ready and rolled out, but not yet officially enabled across the mainnet
→ Testnet is basically a trial classroom, where new content (like version 26) is introduced only after it is safe enough for the real classroom

Common points of confusion

1️⃣ Why is mainnet still at 24 even after the June 18 deadline?
→ That deadline was only for node operators to install the new software. After that, the team still needs to check network consensus consistency and overall stability before flipping the switch. They are cautious to avoid any issues with anyone's funds

2️⃣ Why did my node already install p25.2.2?
→ That just means the new software is in place, fully ready, waiting only for the mainnet green light to enable it

3️⃣ Testnet is already on 26, is that strange?
→ No, not strange at all. Testnet always tests first before going live on mainnet

Bottom line

→ Based on actual data, mainnet is still officially running protocol 24
→ The 25.2 update is ready and installed, just waiting for the right time to enable it
→ The differences between networks are only about timing, not errors or hidden issues