Source

We're Super-Hyper-Exa-Excited to announce that DefraDB V1.0 is released! Bringing the latest and greatest in Tracability, Governance, and Peer-to-Peer resilience. It's the Database of the future. Come build with us! stats.source.network/q/RpqCtjgB5 #DefraDB #Source #zerotrust #p2p

@isocroft @getifyX Merkle-CRDT is a whole other animal

@getifyX @EdgeOfSource For complex data, having fully decentralized CRDTs is a problem and not a flex. My two cents...

DefraDB from @EdgeOfSource just hit v1.0 RC1. It's a P2P document database with graphql syntax, that syncs across edge devices, no privileged central server required. Embeds anywhere (Go, WASM, C-bindings). Encrypted, auditable/time-traveling, CRDT merging, field-level ACP.

DefraDB v1.0 RC1 is here. Our first stable release candidate after 25 pre-production releases. A peer-to-peer document database for edge AI and offline-first applications. Data syncs across devices using Merkle CRDTs. No central server required. source.network/blog/defradb-v…

Sourcerer 🧙‍♂️ @getifyX spitting facts about passkeys @nordicjs

@joodalooped @getifyX @zero__ms @convex That exists because people didn't realize that we had explanations for each of the edge-first statements, and they would ask why it had to be p2p, verifiable, etc. So 2 seconds of scrolling vs constantly getting asked the same questions, even if the answers were on the site

@getifyX @zero__ms @convex @EdgeOfSource but i will say, can you *please* rid of all the scroll and timer-based animations on the site? i’m trying to read and it’s basically impossible

more and more i feel like a combination of versioned event definitions and some kind of "smart enough" client cache might be the best poor man's sync engine and that local-first has been doomed from the start by not being idealogicaly firm enough

I’m hiring backend / protocol engineers to build a new product in the Penumbra codebase DMs are open if you understand these systems like this / namada

📚 System Design: Proxy Re-Encryption **Problem:** Share encrypted data without exposing content **Solution:** Proxy Re-Encryption - Alice encrypts data with her key - Proxy converts to Bob's key format - Bob decrypts with his key - Proxy never sees plaintext Used in secure sharing systems like Source Orbis 🔄

🌐 Tech Philosophy: Edge-First Computing - **Cloud-First**: Send data to distant servers - **Edge-First**: Process data where it's created **Advantages**: - Lower latency (faster responses) - Better privacy (data stays local) - Offline capability - Reduced bandwidth costs The shift from centralized to distributed computing 🚀

💡 Concept Explained: Threshold Cryptography Instead of "1 key = 1 signature," threshold crypto uses an M-of-N scheme: - Split key into N shares - Any M shares can create a signature - Individual shares are useless alone This increases security and fault tolerance. Example: A 3-of-5 system survives 2 node failures. ⚖️

🔬 Algorithm Spotlight: Merkle DAGs - DAG = Directed Acyclic Graph (like a family tree, no loops) **Merkle DAG benefits:** - Each node has a cryptographic hash - Changes create new hashes (tamper evidence) - Efficient verification of large datasets - Used in Git, IPFS, and DefraDB Think "cryptographic data structures that verify themselves" 🔗

📖 Tech Tutorial: Distributed Key Generation (DKG) Traditional crypto: 1 private key = 1 point of failure DKG approach: - Multiple parties collaborate - Generate key shares (no one has full key) - Threshold operations (e.g., 3 of 5 needed) - Reconstruct signatures collectively Result: Security through distribution, not trust 🛡️

🧠 Deep Dive: Zero Knowledge Proofs ZK Proof = Prove you know something without revealing what you know Real examples: - 🔐 Prove you're over 18 without showing your birthdate - 🔐 Prove you have funds without revealing your balance - 🔐 Prove identity without exposing personal data 3 properties: Completeness, Soundness, Zero-Knowledge 🎯

🎓 Learning Corner: Content-Addressable Data Traditional web: "Where is the data?" (URLs point to locations) Content-addressable: "What is the data?" (Hash identifies content) Benefits: - ✅ Data integrity verification - ✅ Deduplication - ✅ Decentralized storage - ✅ No broken links

🧠 @GoogleDevs' Gemma 3 270M shows the future: specialized #AI models for specific tasks. While they're solving deployment at scale, Source is solving the data layer: ✅ Edge-first data management for local AI ✅ Decentralized model versioning with DefraDB ✅ Privacy-preserving inference with ZK protocols Small models + edge compute = true AI democratization 🚀 developers.googleblog.com/en/introducing…

📚 Tech Education: What are CRDTs? CRDT = Conflict-free Replicated Data Type Think Google Docs collaboration, but for databases: - Multiple users edit simultaneously - No "merge conflicts" or data loss - Mathematical guarantees of consistency - Works offline, syncs when connected DefraDB uses Merkle CRDTs for added verification 🔍

My database is so eventually consistent that by the time it converges, I'll have already retired and started a goat farm 🐐

Zero Knowledge Proofs: "I can prove I know something without telling you what it is!" My imposter syndrome: "Finally, a cryptographic protocol that gets me." 🤐

My code is like a fine wine: it gets better with age, but mostly, it just gives me headaches. 🍷🤕

My distributed system is so distributed that I need a distributed system to find my distributed system. 🤔

Building collaborative features shouldn't require a PhD in distributed systems. DefraDB makes it simple: ✅ Real-time collaboration built-in ✅ Offline editing with perfect sync ✅ No conflict resolution logic needed ✅ Works with any data structure Explore real examples and documentation: github.com/sourcenetwork/…