Stellar Development Foundation Unveils Project Thruput With 7.02 Million Transactions Per Second Benchmark
Key Summary
Stellar Development Foundation released Project Thruput on October 28, demonstrating experimental component benchmarks scaling up to 7.02 million transactions per second across eight machines while proposing a fee-free scheduling model tied to native-token balances.
Key Bullets
- Stellar Development Foundation introduced Project Thruput on October 28 as a technology preview showcasing isolated component benchmarks on FutureNet.
- Reported single-validator execution capacity climbed from 1.18 million payments per second on one machine to 7.02 million on eight machines.
- Official documentation confirmed the figures reflect controlled component measurements rather than end-to-end public network throughput or mainnet readiness.
- The experimental architecture proposes replacing standard transaction fees with a scheduling share mechanism tied directly to unlocked native-token balances.
Stellar Unveils Experimental Engine Benchmarks
Stellar Development Foundation introduced Project Thruput on October 28 as an experimental technology preview designed to alter how blockchain execution engines process competing transactions. According to official release documentation published on FutureNet, single-validator execution capacity climbed from 1.18 million payments per second on one machine to 7.02 million on eight machines. Open-source code and reproducible testing scripts accompanied the release.
Engineers built the proposed model to eliminate the standard ordering bottleneck that occurs when multiple transactions target shared account state. Conventional networks run independent instructions in parallel but serialize operations touching the same data. Thruput scales execution across multiple machines even under heavy workloads. The foundation explicitly stated these figures measure isolated component performance inside a controlled laboratory environment rather than public network capacity.
Separating Laboratory Metrics From Network Reality
Public-blockchain throughput requires more than rapid local computation within a single validator machine. Consensus finality, peer-to-peer message propagation, storage expansion, and adversarial behavior dictate true operational limits. Until those distributed components operate together under live conditions, translating benchmark figures into adoption forecasts remains speculative. Scaling distributed software introduces unavoidable operational trade-offs.
Independent developers must evaluate the gap between an early software prototype and dependable production infrastructure. A breakthrough in local execution speed does not prove that an entire network handles identical demand without failure. Public network integration requires rigorous adversarial testing and third-party verification of all reported figures.
Proposed Fee-Free Scheduling Model Raises Questions
Official specifications indicate the architecture can operate without charging traditional per-transaction fees. Accounts receive a scheduling share proportional to unlocked native-token balances when demand exceeds available capacity, while strict computational limits continue applying to individual transactions. This design replaces standard fee markets with an alternative resource-allocation framework rather than providing unlimited free infrastructure.
Market participants face new questions regarding validator fairness, account concentration risks, and protection against network spam. Developers should wait for complete deployment specifications before adjusting infrastructure promises for end users. Independent reproduction of the FutureNet benchmark remains the primary milestone for network operators.
About CryptoNewsFree Market Intelligence Wire
The CryptoNewsFree Market Intelligence Wire provides rapid, objective coverage of breaking crypto developments, regulatory actions, and market liquidity trends. Our reporting strictly follows our Editorial & Verification Standards.