Futures
Access hundreds of perpetual contracts
TradFi
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Launchpad
Be early to the next big token project
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
PI ANNOUNCES RPC SERVER: WHAT DOES THIS MEAN?
In my previous comparison between Pi and Stellar,
I analyzed how both systems operate to highlight what makes Pi Network different, especially regarding its underlying algorithm and why it still needs to exist while Stellar continues to perform and grow well.
Two days ago, the Pi Core Team announced the launch of an RPC server on Testnet. After running a few simple commands to inspect the returned data, I confirmed that the system is running on Stellar Core v23.0.1 and has integrated the Soroban environment.
This is a significant step for the system and is closely tied to the technical relationship between Pi and Stellar.
So what exactly are RPC, Soroban, and smart contracts? And what is the real technical significance of this event?l
1. Understanding RPC, Soroban, and Smart Contrac
ts
To make these concepts easier to grasp:
RPC ServerAn RPC server acts as the communication gateway between the blockchain and external applications. While nodes store the full ledger, applications like wallets, exchanges, or games don’t need to download the entire blockchain. Instead, they connect to the RPC server and send requests such as “Check the balance of wallet A.” The RPC reads the blockchain data and returns the result.
This interaction layer is essential because it allows real-world applications (dApps) to plug into the network easily. Without RPC, integration would be complex and inefficient.
Smart Contracts
From a software engineering perspective, a smart contract is a decentralized state machine. It consists of code that is compiled, stored immutably, and executed across all nodes in the network.
Once deployed, it runs automatically when predefined conditions are met, without requiring intermediaries. Smart contracts can enable:
Liquidity pools and automated pricing
Token swaps
Autonomous financial operations
Governance systems
Complex programmable logic
Soroban
If the blockchain is a ledger, then Soroban is the computer attached to that ledger that executes smart contracts.
Before protocol v20, both Stellar and Pi mainly functioned as static balance ledgers. Soroban transforms the system into a programmable environment by introducing a virtual machine capable of executing embedded code.
Soroban uses WebAssembly (WASM), a high-performance standard. Developers can write contracts in languages like Rust, compile them into .wasm, and deploy directly—avoiding niche languages like Solidity.
In simple terms:
Pi is no longer just a currency for transferring value—it is becoming a full platform. Complex operations like lending, escrow, decentralized exchanges, and automated business logic can now be built directly on the network.
2. What Is Actually Happening on Pi Testnet
After querying the RPC server directly, two technical facts are clear:
First:
The Testnet has been upgraded to Stellar Core v23. The returned data shows:
captiveCoreVersion: stellar-core 23.0.1
Since Soroban has been stable from v20 onward, this confirms Pi is aligned with the latest Stellar infrastructure.
Second:
Soroban environment parameters are present.
Fields like sorobanInclusionFee (smart contract execution fees) are already returned—currently set to 0. This indicates:
The smart contract environment is fully installed
But real contract activity has not started yet on Testnet
3. What Happens Next?
Previously, developers building on Pi mostly created Web2-style applications hosted on their own servers. They used the Pi SDK to interact with Pi’s centralized API.
Typical flow: App → Pi SDK → Pi Core Team API → Blockchain → API → App
Developers were limited to predefined functions (mainly payments).
With RPC, everything changes:
Before RPC → Developers were like restaurant customers ordering from a fixed menu.
After RPC → Developers now have direct access to the kitchen.
They can:
Query blockchain data directly
Deploy smart contracts
Build custom logic without relying on Pi Core Team’s API
This removes a major layer of centralization and moves Pi closer to a true Web3 architecture.
4. Technology vs Market Price
A critical distinction:
Technology (RPC, Soroban, v23): builds infrastructure and utility
Market price: driven by psychology, speculation, and supply-demand
Strong technology does not guarantee immediate price increases. However, without solid infrastructure, no project can sustain long-term value.
Conclusion
The launch of RPC and integration of Soroban v23 signals a clear transition:
Pi is moving from network building → utility building
The data layer is now open.
The next phase depends on developers:
Writing smart contracts
Deploying dApps
Creating real use cases
This is when ecosystem growth truly begins