we’re selling space on our clothes. and taking Web3 brands with us across 5 major crypto events in Mumbai. yes, we’re making our outfits part of the marketing. every event. every photo. every video. every conversation. your brand comes with us. 2 people. 1 campaign. 25 brands. we’re turning ourselves into walking billboards for Web3. and while everyone’s talking about Singapore right now, we’re betting on Mumbai. 🇮🇳 5 events. One packed Web3 week. 25 limited spots. your logo. on us. IRL. want your brand on the outfit? → web3duo.fun featuring: @IBWofficial · @SuperteamIN · @EFDevcon · @UnchainedSummit · @ETHGlobal which Web3 brand should claim a spot? 👀👇

Today, I've read the criticism of how Zano handled the Gateway Address exploit, including from people I consider friends of the project. A lot of it is fair, and I want to respond personally. First, we made mistakes. A bug made it into Hard Fork 6 and went unnoticed for weeks. Our first messages were rushed: we said "24 hours" and "no other choice" before we fully understood what had happened. That's on us, and I'm sorry to everyone who lost time, money, or trust because of it. Second, why the restart? Once the exploit was confirmed, there were two paths, and neither was good. Doing nothing meant unauthorized ZANO and fUSD in circulation without limit, diluting every holder and breaking the most basic promise a currency makes: a fixed supply. It would also tell every future attacker that exploited coins get to keep their value. No project survives that. Immutability exists to protect transactions made within the consensus rules. These coins were created by a bug that let those rules be broken. Fixing that doesn't override consensus; it restores it. Restarting the chain from before Hard Fork 6 costs a month of history, and it costs trust, which we'll have to earn back. But it restores the supply everyone signed up for, and it leaves a path to rebuild. Which is better than 7 years of hard work left to die. We know it hurts. But not doing it would have hurt more. Third, nobody "pressed a button." The team can't roll back Zano. What it can do is publish new source code and ask the majority of the network to run it. That's exactly why we had to ask everyone to stop transacting and to update: if the team could flip a switch, none of that would have been necessary. Pools, exchanges, node operators, and wallets each decide for themselves whether and when to switch. In practice, a few large players like the major mining pools carry a lot of weight in that decision, and that's a fair point to raise. A broader base of independent operators would make Zano stronger, and that's something we should all work toward. Fourth, reimbursement. The team intends to make the community whole, and I won't pretend that's simple. A month of payments between people, each depending on the one before it, is genuinely complex, and I don't have all the answers yet on how the process will work. What I can tell you is where the money comes from: the dev fund, team funds, and large holders who have committed to contribute. No additional coins will be issued. Nobody's holdings get diluted to pay for this. Instead of walking away, the team and some of the project's biggest supporters chose to double down and put their own funds on the line. In my opinion, that's a strong sign and shows the team's and community's commitment to not just give up. Finally, what comes next? The team will publish the technical cause, a review of the related code, and clear criteria before Gateway Addresses return. Bugs can happen in any project. How you respond to them is a choice. I'm still here because I believe in what Zano is building: a private economy that anyone can use. That trust has to be earned back with work, not words, and that's what we intend to do. Thank you to everyone who stayed, questioned us, and held us to a higher standard. From here, we rebuild.

Security update and coordinated upgrade: The core team has identified a vulnerability in public Gateway Addresses that affects asset issuance, including fUSD. Transaction privacy is unaffected, and no spend keys or wallets are compromised. We will coordinate a network upgrade asap. It requires majority consensus to activate, so we ask node operators, pools, and exchanges to be ready to update. No action is needed from ordinary users beyond upgrading when the release is published. A full technical write-up will follow after the upgrade is in place.

Oh, this is NICE! 👀🇮🇳 Indians can now use private assets ( like $XMR, $ZANO or $FUSD - a private dollar) for everyday expenses. A private economy is being created, with the Auditable Wallets feature of $ZANO enabling auditability/compliance when needed. Travel: ✈️ Air India 🚕 Ola 🌍 Klook Fuel: ⛽ BPCL ⛽ Indian Oil Entertainment: 📺 JioHotstar 🎬 Zee5 🎬 SonyLIV Gaming: 🎮 BGMI / Battlegrounds Fashion & Shopping: 👕 AJIO And this is just part of what’s available. The interesting question isn't just: “Can you hold private money?” It's: “What can you actually do with it?” 🛡️ Good times ahead for self-custody and financial privacy. #Privacy #PrivacyInIndia

I just realised that it's not that easy for a beginner to understand the ZANO structure. How do Ring Signatures, Stealth Addresses, Pedersen Commitments plus Bulletproofs+ work together to hide the sender, receiver, and amount on-chain? It can get technical pretty quickly. But don’t fret - things are in the works to make it easier to understand. 😉 Stay tuned. 🛡️ #Privacy #Bitcoin zano:native

🔐 How Does a Privacy Coin Actually Hide Your Transaction? We know that privacy matters. But here's the bigger question: How does a privacy coin actually make a transaction private? 👀 This week on #PrivacyTuesday , we're going one level deeper - but keeping it beginner-friendly. We'll break down: 🔒 How transaction privacy actually works 👤 How Stealth Addresses hide the recipient 🔄 How Ring Signatures help hide the sender 💰 How Pedersen Commitments help hide transaction amounts 🧡 And how these technologies come together in Zano We'll also do some simple examples and explain what an outside observer can - and can't - learn from a private transaction. 🎙️ EP12 of #PrivacyTuesday (in Hindi) 📅 Tuesday 🕖 7:00 PM IST / 1:30 PM UTC 📺 Main livestream + giveaway: YouTube piped.video/@SurvivingInCryp… 🎙️ X Space: I'll be live there too nitter.net/i/spaces/1RJZzBenwjmJB 🎁 Giveaway: We'll have a zano:native giveaway during the YouTube livestream! No technical background needed. If you've ever wondered “Okay, but HOW does a privacy coin actually hide my transaction?” - this one's for you. 👀 Come hang out, learn something new, and bring your questions. 🧡 @zano_project zano:native #Privacy #Bitcoin

GM GM! ☀️ Spent yesterday researching AI efficiency across different models and comparing ChatGPT, Gemini, and Claude for different tasks. My current findings: 🖼️ Best for image generation: ChatGPT 🧠 Best for context & memory: ChatGPT I’m going to experiment more with Gems in Gemini Pro for better responses, and also make more use of NotebookLM. I was considering getting a ChatGPT subscription, but first I want to properly test Gems + NotebookLM with Gemini Pro. The idea: one AI acts as the main, while the others become my advisory board. 🤖 Let’s see how this setup works! 👀

Quick “Ready for the Run” Event Recap! ✨ For me, this was the most educational Web3 meetup I’ve attended to date. Every speaker had tons to share, from grassroots data and community insights to careers in Web3 and AI. Some of the valuable takeaways: → How they’re collecting grassroots data from Web3 folks across different cities in India, targeting 100K+ responses → Why most projects FAIL: a distribution problem, backed by various case studies → Why having a great team is so important → Live surveys and real-time results that keep participants engaged and involved And much more! Also got to meet lots of cool people at the event. Really enjoyed the conversations and the overall vibe. 🤝 Biggest takeaway: Build in public! 🚀 #ReadyForTheRun #Web3Events #India