Codex is evolving. From today, our protocols will be consolidated under Logos. Over the past months, we have been working to simplify our structure and align our technologies towards a common goal. The system is no longer working for us, so we are charting a new course by building a decentralised technology stack to revitalise civil society. Join us and build on the Logos stack. One unified ecosystem. Private-by-default. Built for real life. Follow @Logos_Network.

A new era is coming. Build it with us. Join @Logos_network.

August brought big shifts for Codex. We paused the testnet to focus on core protocol design, explored AI use cases, and continued shaping the next phase of our development. Read the full update: blog.codex.storage/codex-aug…

We’ve listened to your feedback from the Codex testnet — and we’re grateful to everyone who participated, tested, and broke things. As we shift focus to core protocol design and specs, we’ll pause the current testnet. 
This next phase is all about laying stronger foundations. We're revisiting key architectural decisions to make Codex more usable, resilient, and aligned with real-world needs. 
A new testnet is already on the horizon — rebuilt from the ground up, based on what we’ve learned together. In the meantime, thank you for being part of this journey. Your feedback is already shaping Codex's future. 
Decentralised storage deserves real usability. That’s what we’re building. Stay tuned.

AI meets unstoppable storage. We're teaming up with @qubetics to integrate Codex's decentralised storage into their AI-centric product stack. First up: QubeQobe libraries stored in SLM format on Codex — optimized, persistent, and censorship-resistant. More to come, stay tuned!

Codex Community Call & AMA nitter.net/i/broadcasts/1dRKZYYOd…

July saw the Codex team make important progress and trial new tools built for the network. We also announced that we are undergoing an exciting evolution that will align us closer to the core vision of @Logos_network. Read the full update: blog.codex.storage/codex-jul…

Join the next Codex Community Call. We'll be talking about @ThirdStorage, a new pinning service built on Codex, and answering questions from the community. Live here on X broadcasts. Mon 4 Aug | 15:00 UTC

Codex is evolving. The last few weeks have been a period of deep reflection and realignment for the Codex project. We are entering a new phase—one that aligns more closely with the long-term vision of the Logos ecosystem. As part of this transition, we are carefully reassessing our priorities, streamlining our efforts, and exploring how to make Codex not only more robust and censorship-resistant, but also more usable and accessible for developers and end users alike. During this realignment, our external communications may be a little quieter than usual. That’s intentional. We're taking the time to get this next chapter right. In the coming weeks, we’ll release a more comprehensive update outlining what’s next for Codex. Until then, thank you for your continued support, patience, and belief in the mission. The future is still decentralised.

Public goods like the @InternetArchive are crucial for preserving our collective history. We can protect them with decentralised infrastructure. Help us by becoming an early node runner. logos.co/songs

Network States require more than ideals — they need infrastructure. Tomorrow at @NapulETH, our Growth Lead @crypto_marina joins a panel to explore: “The Cypherpunk Paradox: Privacy, Network States & Decentralized Growth.” What is sovereignty without control over your data? Let’s unpack this paradox at #NapulETH.

What’s your biggest concern with decentralised storage?

Mobility data will power insurance, autonomy, resale, and traffic prediction. But it needs to be stored independently and durably. If your project deals with real-world data, think beyond the cloud. Let’s talk.

Here is an example: A DIMO-connected fleet logs vehicle health data. Instead of storing logs in AWS, they store it on Codex: + Lower storage cost + Data stays available even if DIMO HQ vanishes + Ecosystem apps can access it with permissions

Codex advantages: + Erasure coding = data protected from loss and hacks + Persistence mode = long-term availability + Censorship-resistant by design + No vendor lock-in + Open-access API for devs

Enter Codex - a decentralised storage network designed for real-world, high-throughput data like: – Vehicle logs – Environmental mapping – IoT sensor streams – Dashcam media

Then there’s control: OEMs like Ford, GM, and Tesla store YOUR car data. Developers building mobility apps? They're renting storage they don’t own. If AWS suspends you or changes pricing, you’re screwed. Privacy? Forget it.

Let’s talk costs: AWS S3 standard storage: ~$23/TB/month + backup (Glacier), egress fees, region replication Serving 1,000 drivers = tens of thousands per month in infra costs.

Where does all that data go? Most of it is streamed to centralised cloud platforms like AWS, Google Cloud, or Azure. Which brings 3 serious problems: Cost Control Longevity

Here’s what that looks like in practice: A typical connected vehicle can generate 25GB of data/hour. That’s 600GB/day if driving 24/7. At fleet scale (say 1,000 vehicles), that’s 219 petabytes/year.