DeFi, payments, tokenization, Soroban, governance, and project launches — curated daily from publications, project blogs, and community channels across the Stellar blockchain ecosystem.
Stellar offers a superior platform for ICOs compared to Ethereum, featuring built-in token issuance, a decentralized exchange, lower fees, faster transactions, and enhanced security for projects that don't require complex smart contracts.
Tutorial on issuing custom tokens on Stellar, demonstrating how to create, distribute, and manage tokens like the example HUG token with fixed supply and built-in exchange capabilities.
Stellar Development Foundation announced the creation of Lightyear.io, a for-profit company to handle partnerships, integrations, and commercial services, while SDF refocuses on protocol development and governance as a neutral non-profit steward of the Stellar network.
Stellar.org announced the Stellar Build Challenge, a grant program offering awards across four categories: Anchors, Applications, Exchanges, and First-Time Submissions. Winners will be announced October 1, 2016, with funding from unclaimed lumens.
Stellar Core has been upgraded with significant code improvements, now 50% smaller and faster while maintaining security through the Stellar Consensus Protocol. Developers can upgrade their accounts and begin building financial services on the improved network.
Stellar Development Foundation released an upgraded distributed network codebase with improved security, scalability, and modularity. The new version introduces batching operations and multisignature accounts, enabling developers to build financial services like crowdfunding without scripting.
Stellar network upgrade launching in November will rebrand stellars to lumens and require user account upgrades. The nine-month development effort delivers a safe, scalable, and accessible network for global financial services.
Stellar celebrated its first anniversary, growing from two cofounders to a 16-person team while launching the Stellar Consensus Protocol, building global partnerships, and establishing a thriving developer community across multiple continents.
The Stellar Consensus Protocol (SCP) introduces federated Byzantine agreement, a consensus mechanism that achieves decentralized control, low latency, flexible trust, and asymptotic security simultaneously. SCP enables a worldwide financial network where participants reach agreement without relying on centralized institutions.
The Stellar Foundation released details on its new Stellar Consensus Protocol, based on federated Byzantine agreement, designed to replace the existing consensus mechanism. The protocol has been stress-tested to handle 100 million accounts and hundreds of transactions per second, with deployment targeted for summer.
Stellar.org introduces the Stellar Consensus Protocol (SCP), a federated Byzantine agreement mechanism designed for decentralized payments. SCP offers four key properties: decentralized control, low latency, flexible trust, and asymptotic security, with a new open-source codebase now available for peer review.
Stellar co-founder Joyce Kim discusses the project's launch challenges, consensus protocol issues being addressed by Chief Scientist David Mazières, and efforts to drive developer adoption and financial inclusion in emerging markets like Nicaragua and Vietnam.
A ledger fork in the Stellar network sparked debate over the Ripple consensus protocol's safety. Stellar Development Foundation attributed the incident to protocol flaws, while Ripple Labs disputed the claims, arguing the issue stemmed from Stellar's modifications to the code.
Stellar experienced a ledger fork due to weaknesses in its Ripple-based consensus algorithm. The network temporarily switched to a single validator node and is prioritizing development of a new provably correct consensus system to prevent future forks and double-spend risks.
Stellar network experienced a 16-hour outage on September 20, 2014, caused by validator nodes running out of RAM, halting consensus and all transactions. The foundation addressed communication gaps and began work on scalability improvements to prevent recurrence.
