Just dropped: a HASHD overview. We walk through the architecture, core components, and how everything fits together. Check out the WIP code here github.com/orgs/hashd-social… and join the waitlist at hashd.social/ . Launching soon on @megaeth

gm! Been heads down on ByteCave for the past month. It turned into a full decentralized P2P storage network - way bigger scope than initially planned. What I built: ContentRegistry - Content hashes registered on-chain before nodes store them. Keeps the network verifiable. AppRegistry - Apps burn $HASHD to register. Once whitelisted, their content can be stored network-wide. Node Economics - Nodes stake $HASHD, earn rewards for storage + uptime. User Sovereignty - deleteOwnedContent() wipes your data network-wide anytime. You control everything you post. Built on libp2p + WebRTC for browser-to-node P2P. Fully decentralized, no central servers. Key features: ✅App-agnostic - any dApp can integrate ✅Store messages, posts, media, NFTs, host entire websites ✅Can run as a private network between friends for encrypted personal storage This is why I pushed back testing - needed to get the foundation right. Now it's just plugging the front end back in and onboarding testers. Putting together a walkthrough video over the next few days.

HASHD is built on a single, uncompromising tenet:zero points of centralization. Everything flows from that. At the heart of the protocol sits 20 smart contracts (yes… 20 and counting 😓) coordinating everything including: 🆔 HashIDs (formerly HASHDtags — RIP, you were a mouthful) → Universal on-chain identifiers powering identity, references, and routing... eg bread@mega / 🔐💬 Encrypted messaging, guild posts & marketplace references → Private conversations and content pointers without leaking metadata 🏰🧙‍♂️ Guild deployment → Automated creation of guild infrastructure, including ERC-20 tokens and NFT Prime Key contracts 🦇🕸️ ByteCave node registry (our custom “IPFS”) → On-chain discovery and capability tracking for bat nodes 💸🔥 Future protocol rewards → ERC-20 incentives for storage, availability proofs, and network participation + much more. This thing has… grown 😅 We’re now up to 8 major services: 1️⃣ Smart Contracts Solidity contracts, tests, and deploy scripts — the on-chain backbone. 2️⃣ Official HASHD Web App 🌐 hashd.social Your primary interface into the network. 3️⃣ HASHD Components - An NPM package for shared components + styles across the ecosystem — and an easy on-ramp for 3rd-party plugins & extensions. 4️⃣ HASHdash - Internal + public dashboard for network, service, and node health. 5️⃣ HASHdash API - Powers the dashboard and is open to 3rd parties for network health + node management. ⚠️ (the API is NOT a core dependency of the network) 6️⃣ ByteNode 🦇 - An Electron app anyone can install to spin up their own bat node and enter the ByteCave cauldron. Contribute storage, earn rewards — or just keep your own encrypted content safe locally. 7️⃣ ByteCave Core -🧠 The Node.js core that powers every bat node. Encrypted blob storage, content filtering, shard policy execution, libp2p stream replication, GC, and continuous node health monitoring. 8️⃣ ByteCave Browser - A libp2p-based client library enabling direct WebRTC P2P between bat nodes. No HTTP gateways. No proxies. Just 🔐 encrypted WebRTC DataChannels + pubsub signaling for NAT traversal. Now a little about incentives (high level and still in development so may change and expand) → Nodes register capabilities on-chain → Prove ongoing content availability to earn HASHD → Users, guilds, and marketplaces spend HASHD for long-term or permanent storage guarantees → A portion of tokens are burned to balance issuance and align incentives Lots of moving parts 🤣 Thousands of tests written, plenty more holes to plug before full end-to-end confidence — but we’re getting there. None of this would be moving this fast without the speed of ⚡️ 📸 A few of screens from the web app and ByteNode below. Expect much more this week. And don't forget to join the waitlist and spread the word.. we will be expanding the airdrop rewards program next week, but early birds may get a little bumb bonus. Stay Uncensored. Alexx.

DEV UPDATE: The ByteCave network is now up and running locally, with encrypted blobs replicating and sharding across multiple nodes. ByteCave is purpose-built for HASHD, so it avoids a lot of the overhead and unpredictability of general-purpose systems like IPFS. Nodes store only ciphertext, support selective retention, and expose verifiable proof-of-storage, all without ever seeing plaintext. This also gives us much cleaner garbage collection and better performance characteristics for real-time messaging and group content. I’ve integrated ByteCave with the messaging contracts and the UI this afternoon, and it’s working beautifully end-to-end. There’s still work to do around node incentives and long-term economics, but the core architecture is proving out exactly as intended. Current flow: - A storage node registers on-chain with a verifiable public key. - Each node declares its own storage policy (what categories of data it will store, shard size, and retention duration). - Encrypted blobs are uploaded, content-addressed, and replicated across eligible nodes. - Nodes can cryptographically prove they are retaining specific blobs, without revealing contents. - Clients verify availability and proofs locally, without trusting any single node. Early days still, and lots more testing to do, but this is starting to feel like the right foundation for sovereign, real-time communication.

Shout out to @opensea for forcing everyone to see prices in USD as opposed to the magical internet money prices and assaulting us with the reality that we've been spending real money on jpgs this whole time. Idk, maybe switch it back before everything goes lower.

Been pushing IPFS to its limits… and it pushed back. Way too slow, no guarantees, no verifiable storage. So we’re building out the ByteCave — an encrypted shadow-storage layer for HASHD: Ciphertext in → replicated blobs → nodes must prove availability → clients verify → garbage-collect what dies → keep what the community wants to live. Nothing trusted. Nothing exposed. Everything sovereign. @MegaETH deserves storage that moves like the chain itself.

OpenSea switching the default from ETH to USD looks cringe... It was always ETH - if someone wants USD they can switch it themselves. A crypto-native platform shouldn’t force fiat framing especially when crypto is the whole point.

DEV UPDATE: HASHDtags are now beginning to take their final shape. They're tradable ENS-like NFTs on @megaeth and can be attached and reattached to different 'mailboxes' whilst always reverse-resolve to your public encryption key. The longer term plan is for 3rd-party dApps to be able to plug into HASHDTags and the HASHD messaging layer via our provider, unlocking encrypted, wallet-based communication and community features anywhere on MegaETH. On day one we'll be launching with @ 'hashd' and 'mega' domains, with community based identites to follow, eg: alexx@punks or simon@bayc etc. We will be partnering with communities as and when on this. If you hop on the waitlist, you'll be first in line to grab one of these at launch. hashd.social/waitlist