Quinten (Mr. Kwibs) | Zano

In the Pursuit of Privacy | of Marketing & Growth @Zano_Project

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

New to Zano but don't know where to start? I got you covered with the best @zano_project links!👇

❔Where to learn about Zano?
🔹Introduction page: https://t.co/5ibFClpD6M
🔹Documentation: https://t.co/zSJ8ItMYii
🔹ZanoList YouTube channel: https://t.co/ZAbp26EERy

❔Where to trade Zano for other crypto?
🔹MEXC: https://t.co/Ne8GVtCQoc
🔹CoinEx: https://t.co/ZHNpw0O7p8
🔹AscendEx: https://t.co/EkXYOzcgYS
🔹 Full list of exchanges: https://t.co/OsCHOl0Gcy

❔Where to buy Zano with a credit/debit card?
🔹Alchemy Pay: https://t.co/IdyRaO2X18

❔Where to trade Zano and the Confidential Assets?
🔹DEX: Zano Trade: https://t.co/KNjXWNc1fS

❔Where to hold your Zano?
🔹@Bitcoincom: https://t.co/WC2nCZAmGs
🔹@EdgeWallet: https://t.co/oYG5p0cjma
🔹@cakewallet: https://t.co/aaythWlpvG
🔹Zano's official mobile & desktop wallet: https://t.co/ZwiB59qeh7

❔How to accept Zano as a business?
🔹WooCommerce plugin (e-commerce): https://t.co/0hmaVnSDt0
🔹Coinremitter (e-commerce): https://t.co/1QCcyUMDLJ
🔹Point of Sale system (IRL commerce): https://t.co/QVJE3KD0mH

❔Where to spend your Zano?
🔹@ZanoX_io (gift cards, swaps, AI bot, lottery): https://t.co/zCjJ9gXp2F
🔹@TrocadorApp (prepaid cards, gift cards, swaps): https://t.co/M7ZwFCTOHx
🔹Zano Shopping (merchandise): https://t.co/EU5V2vh0TK
🔹@ZanoList (merchandise & more): https://t.co/Ix6iEPstnG
🔹Gambling: https://t.co/RZYXZ367Bw

❔Projects building on Zano
🔹@TeamZanoBay (P2P marketplace): https://t.co/4N7qMYUOY7
🔹@FreedomDollar5 (Privacy stablecoin): https://t.co/HUAFeN8aRR
🔹@ConfidentialLyr (Non-custodial bridge that allows you to bridge any popular crypto asset to and from Zano): https://t.co/BXm4a4lBVc
🔹@BanditToken (Meme-ish token building trading tools for Zano): https://t.co/ozV8GearVH
🔹@obscura_nft (Create, manage, and trade private NFTs): https://t.co/W3TICvMJtZ
🔹Wrapped Zano (Bridge to ERC-20): https://t.co/EK1ZQwCnbb

❔Want to design or advertise with Zano?
🔹Media Kit: https://t.co/8VinP9prIh
🔹Graphics Folder: https://t.co/rouxZF5XA3

❔Other useful links
🔹Link Tree: https://t.co/kiQloSB1jq
🔹ZanoStats: https://t.co/cCRImQD4Vj
🔹Explorer: https://t.co/0uat2pSihj
🔹Zano Messenger: https://t.co/F3qzSOh2H0
🔹Roadmap: https://t.co/gyjZdQMlXO
🔹GitHub (open-source): https://t.co/j3JFYYL4J3

❔zAnons to follow on X
🔹@_cryptozoidberg
🔹@pavelravaga
🔹@crypto_sowle
🔹@Gonbat03
🔹@rogerkver
🔹@AaronRDay
🔹@SallyMayweather
🔹@MarcDeMesel
🔹@ValVenisEnt
🔹@vladcostea
🔹@bitcoinnews
🔹@maplesyrupsuckr
🔹@DavidShares
🔹@ourcryptotalk
🔹@thierrybaudet
🔹@briteresi
🔹@HealthRanger
🔹@mattkim1
🔹@JasonBassler1
🔹@MattAgorist
🔹@WeAreZano
🔹@coinmarketmaker
🔹@ZanoAfrica
🔹@ZanoFrancophone
🔹@zanobrasil
🔹@ZanoTurkiye
🔹@Zano_Es
🔹@zano_japan
🔹@moneromatteo
🔹@Zano_Intern
🔹@ZanoChad
🔹@Pinkman_Zano
🔹@Lil__Kingg
🔹@runningzano
🔹@mr_antics1
🔹@TFDCrypto
🔹@XDTravelDude
🔹@biomance

I was only allowed to tag 50 accounts. I know so many more people talk about Zano! Comment below if you are a contributor to the Zano ecosystem.✅👇

[Zano @zano_project]

How recovery of affected balances will work

The team is working on a process to recover affected balances in full. ZANO supply and emission will remain unchanged. Funding comes from the dev fund, team members' personal funds, and contributors who have committed support.

Most affected balances sit with exchanges and services, so recovery runs through them:

🔹 Withdrawals from an exchange during the affected period (August 26 to September 27). These coins are back in the exchange's wallet on the updated chain. The exchange replays these withdrawals once it reopens.
🔹 Deposits to an exchange during the affected period. The team is working directly with each exchange to cover these, so your exchange balance can be credited.
🔹 Frozen MEXC accounts. We are working with MEXC to release accounts with no link to invalid transactions as quickly as possible.
🔹 Card top-ups and payment services. These are settled directly between the service and the team.
🔹 Payments between individuals. These are back with the sender on the updated chain. For cases that cannot be resolved this way, a process for individual users will follow.

What to expect

Each exchange and service checks a month of activity, transaction by transaction, before it reopens. This takes time, and doing it carefully is what prevents balances from being credited to the wrong people or twice. Each exchange announces on its own channels when it is ready.

No action is needed right now. Keep your transaction IDs and records. The team will never DM you first or ask for your seed phrase.

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

@JasonWeyl @zano_project You'll be fine. More info to follow soon🤝🏼

[Zano @zano_project]

Zano recovery update

The hotfix has been pushed and the network is stable on the updated chain.

Where things are at right now:

The updated mobile wallet is now live for both Android and iOS. Desktop users can download the updated wallet from https://t.co/Owl0dihhYd or the official GitHub releases page. If you haven't updated yet, please do. Seed phrases are not required.

Third-party wallets, exchanges and payment services all need to update their own nodes to the updated chain before they can safely process transactions again. For exchanges, these updates will determine when ZANO deposits and withdrawals reopen. We are in direct contact with them to support that work, and each of them announces on their own channels when they are ready. Please wait for each service to confirm through its official channels that it has resumed operations before sending funds.

For anyone who was affected, the recovery process is being prepared. No action is needed from you at this stage, and we will publish the details once they are finalized.

Thanks for your patience and support over the past days; it has meant a lot to the team.

Questions are welcome on https://t.co/Q8SLVkCld7 and in our official Telegram, where you're always talking to the actual team.

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

Gateway Addresses are not active on the recovered chain. They'll return only after a full code review, and the post-mortem will outline what was affected and the criteria for bringing them back.

They were built to make integrations with services and other chains easier, so the goal is to get them right rather than rush them back.

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

@B0risTh3Blade @zano_project Yes, correct.

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

@zeroUTXO @B0risTh3Blade @zano_project @TrocadorApp You're right, and we're working actively with services and partners to make this happen.

[Zano @zano_project]

Update on the Gateway Address vulnerability

The network is stable. The team is working on a process to recover affected balances. ZANO supply and emission will remain unchanged. Funding will come from the dev fund, team members’ personal funds, and contributors who have committed support.

Current priorities for the Zano core team:

🔹 Recovery for affected users. We are working with partners and counterparties to verify affected activity and finalize how recoveries will be handled. No action is needed from affected users right now, and we will share clear instructions as soon as possible.

🔹 Supporting exchanges and service operators. Every exchange, wallet and payment service implements the update on their own side, and we are supporting them by answering technical questions, walking through what they need and confirming their setup before they go live again. Several are already well on their way, and each one will announce when they are ready.

🔹 The post-mortem. This will cover the incident, the response and the steps that follow from it, including an analysis of the Gateway Address code so that we can say with confidence what was affected and what was not. It will be published once that analysis is complete.

The community's support throughout this process has been remarkable, and we’re incredibly grateful.

A recovery update will follow with where things stand across wallets, services and exchanges.

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

@0xJustSandra 💙

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

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.

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

@skyzer4ever @B0risTh3Blade @zano_project Everyone who legitimately purchased coins during the exploit period will be fully reimbursed. Stay tuned for further updates.

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

@JV_Vink Appreciate you Joep🙏🏼

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

@blockblanc 🫶🏼

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

@adamamcbride Thank you🙏🏼

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

@0xalank @DrFuture8000 @zano_project All good, thanks for being so honest!

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

@DrFuture8000 @0xalank @zano_project No it isn't.

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

@Arifai777 💪🏼

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

@Gonbat03 @PleefsX @SallyMayweather I second that.

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

@Niteur1 Thank you!💙

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

@StevePa19490615 @zano_project 💙

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

@DragonXchain It's painful, but giving up ain't an option. We move on.🙏

[Quinten (Mr. Kwibs) | Zano @Mr_Kwibs]

@Gonbat03 I share your sentiment!