This update covers Xandeum storage-layer development, including version 0.5, known as the Ingolstadt release, and planned version 0.6 work for the Stuttgart release.
What is Xandeum?
Xandeum is a storage layer for Solana-connected applications. It is designed to work like a file system so smart contracts and applications can store and update larger datasets than ordinary validator storage can support.
Version 0.4: Where We Are Now
Version 0.4, also called the Herrenberg release, introduced reconstructibility from pods. This means the system can rebuild data stored across provider nodes, or pNodes. The team was also preparing documentation to help developers and operators work with the release.
Version 0.5: Ingolstadt Release
The Ingolstadt release, version 0.5, focused on operator visibility and network measurement:
- pNode Monitoring and Metrics: If you run a pNode (the nodes that provide storage for Xandeum), version 0.5 will track your node's performance. This includes checking if your node is online, responding to heartbeat requests, and handling data requests correctly. These metrics ensure the network runs smoothly and fairly.
- Operator Incentives: pNode incentives depend on current program rules, network status, performance, and protocol parameters.
- Owner-Manager Model: pNode owners can purchase licenses to operate nodes, while managers may handle technical setup and maintenance under separate arrangements.
- Demo App FS Onchain: We've launched a demo app called FS Onchain, similar to a Dropbox-style storage system. It lets you store files directly on the Xandeum storage layer, showing the power of our technology in action.
Operators should review current documentation before setting up or changing pNode infrastructure.
Version 0.6: Stuttgart Release
The planned Stuttgart release, version 0.6, was expected to introduce redundancy and crash fault tolerance:
- Redundancy: Data in Xandeum is split into chunks called "pages" (currently 1 MB each). In version 0.6, these pages will be stored across multiple pNodes. Apps can choose their level of redundancy for example, storing data on 3, 5, or even 43 nodes. If one node fails, the data remains safe and accessible on others.
- Crash Fault Tolerance: If a pNode stops working or sends incorrect data, Xandeum is designed to switch to another node. This is made possible through erasure codes, a technique similar to RAID drives, where data can be reconstructed from other nodes. This helps protect data availability when a node goes offline.
- Preparing for Mainnet: Version 0.6 was planned as a step toward a production-ready storage layer.
We're also working toward Byzantine fault tolerance in future releases to protect against malicious actors, but for the MVP, redundancy and crash fault tolerance are the priorities.
Why Run a pNode?
pNodes are the backbone of Xandeum's storage network. By running one, operators provide storage capacity and help keep the network responsive. At the time of this update, about 150 pNodes were live, with 350 licenses sold. Operators should review current setup guidance and program rules before participating.
Running a pNode on devnet/testnet can help operators prepare for later network phases. Any rewards or boost effects depend on current eligibility, protocol parameters, and performance rules.
What's Next?
The team was also exploring demo applications that use Xandeum storage for real application data.
We're also encouraging developers to build pNode analytics platforms using the RPC interface in version 0.4. These platforms will display node performance, rewards, and more, creating new opportunities for the community to contribute.
A Note from the Team
The Xandeum Foundation is helping drive this project forward. Our director, Anthony, is settling in, and the team is committed to transparency, compliance, and building a decentralized storage solution that is accessible to everyone.
Whether you are a pNode operator, developer, or community member, follow current Xandeum channels and documentation for the latest information.
