Ronne (Zeneca) | Zano

Running socials at @zano_project

[Ronne (Zeneca) | Zano @RonneTVR]

Just made my first $ZANO donation to @Antiwarcom 🕊️

[Zano @zano_project]

The Zano team will be at @AIBC_World in Rome from 2 to 5 November.

We are bringing our own booth, where you can:

🔹 See how private payments work on Zano
🔹 Find out what you can build on top of Zano
🔹 Get set up with a wallet and start using Zano in the real world
🔹 Talk to our BD team about adding private payments to your platform

Find us at booth H7-7381. 🔒

[Ronne (Zeneca) | Zano @RonneTVR]

@Mr_Kwibs 🎯🎯🎯

[Zano @zano_project]

🎙 Zano is live on 3 X Spaces today 🎙

Come join us for the latest on privacy, Zano, and the wider crypto space 👇

🔹 3 PM UTC — Your Wallet Knows Too Much: Who Fixes Onchain Privacy?
Hosted by @wenaltseason | With @RonneTVR
https://t.co/Nxu1UCe6rQ

🔹 3 PM UTC — What's Next at Zano?
Hosted by @HouseofChimera | With @Mr_Kwibs
https://t.co/0F9sKLr3Ap

🔹 5 PM UTC — Are Hardware Wallets Cooked?
Hosted by @Dashpay | With @GinoFPM
https://t.co/e22HbXk3Ci

Hit "Set reminder" so you don't miss them, and bring your questions. 🔒

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

Now that the Gateway Addresses incident is behind us and the last few reconciliations are being processed, we can look ahead again.

What are Zano's current priorities?👇

1. Having a reputable third party audit Zano's Gateway Addresses so we can bring them back safely.
- This means the @THORChain integration can continue, and the Zano Execution Layer also depends on it.

2. Launching the Zano Execution Layer.
- This fixes our accessibility issues, brings extra use cases to zano:native, and brings programmability to Confidential Assets such as $FUSD.

3. Activating Zenith (full PoS consensus with hidden amounts) on Zano mainnet.
- The peak of Zano consensus, further increasing network security, allowing us to have 15-20s block times with just 4-6 block confirmations before you can spend received assets (full confirmation in 60-90 seconds). Unprecedented speed in the privacy space.

We will update the roadmap accordingly, as we need to give the auditor a few months to complete their work thoroughly.

Furthermore, we are also continuing our work on Zano Quest, the platform where zAnons can publish content, complete on-chain tasks, onboard new zAnons, and redeem zano:native for their contributions. This will be critical to growing the Zano ecosystem.

New listings and integrations are also in the works to expand Zano's reach.

The ecosystem is also expanding: @ZanoNames is about to launch so you can trade Zano aliases, and @freedomdollar5 is continuously improving services like FreedomSwap, FreedomWallet, and more.

All in all, there's plenty to look forward to, and I'm personally very excited about Zano's bright future. Let's rock and roll!

[Zano @zano_project]

Thanks to @THORChain for having us on and @raynalytics for this thorough recap.

Recovery is progressing, and Gateway Addresses will only return after an independent audit. That's also the path to a future THORChain integration that will give the community permissionless access to $ZANO.

Read the full recap 👇

[THORChain @THORChain]

⚡ This Saturday on the THORChain Podcast | Ecosystem Spotlight.

@Mr_Kwibs from @zano_project joins @KentonC137 and @patriotsounds live at 10AM EDT / 2PM UTC.

Jump on stage and ask your questions live: https://t.co/phkxsU6sdy

[Zano @zano_project]

An update for ZANO holders on MEXC.

We have completed our part of the reconciliation, including covering deposits made during the affected period.

We expect MEXC to process balance updates and resume services at their earliest convenience.

We will share another update as soon as MEXC has processed the reconciliation process.

[Zano @zano_project]

https://t.co/DMZqzcTyL1

[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.

[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.

[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]

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.

[Zano @zano_project]

Zano network update: Recovery solution for Gateway Address vulnerability

The core team has identified a serious issue involving Gateway Addresses, which enabled unauthorized ZANO and fUSD to enter circulation.

Our investigation has found no compromise of wallet spend keys or ordinary transaction privacy. Zano core consensus is unaffected.

The team has developed a solution to eliminate all unauthorized activity with a coordinated network upgrade. To ensure full network integrity, the Zano blockchain has been restarted from block height 3,833,000, immediately prior to Hard Fork 6. This affects approximately one month of chain history. The recovery requires participating nodes, miners, stakers, and services to adopt the update.

We are relaunching services such as the mobile wallet node and the wrap service one by one. It is up to each third-party wallet, exchange, and service to update on their own behalf. Before sending funds to or from any of them, check that they have moved to the recovered chain.

Transactions confirmed during the affected period are not part of the recovered chain. Keep transaction IDs and trade records, and do not resend a payment until you have updated your wallet and checked its final status on the recovered chain.

If you run a full node, mine, stake, operate a pool, or provide exchange, bridge, or payment services, please install the emergency release as soon as possible. Use only https://t.co/Owl0dihhYd or the official GitHub releases page, and verify the published checksums. Ordinary wallet users can now download the updated wallet from our website as well. Seed phrases are not required to perform this upgrade.

This update removes all unauthorized activity from Zano's chain. It cannot affect payments already settled in USDT, DAI, or other assets on separate networks. The team is working with affected projects and counterparties to account for any losses and will publish the reimbursement and claims process.

Real people and businesses have been affected. We intend for the community to be made whole throughout this process. Certain community members have already pledged support to ensure that assets are restored.

Pushing innovation carries risk, and this is a clear example. Serious incidents have occurred elsewhere: Bitcoin recovered from an exploited supply bug and chain reorganization in 2010; Zcash recently patched a potential counterfeiting flaw before any known exploitation; and Ethereum made an exceptional state change after the DAO attack. Each case was different, and none diminishes the harm here. We will publish the technical cause, the results of reviewing adjacent Gateway Address code, and the criteria for safely resuming activity. Confidence must be earned through that work, and the team is committed to working with the community to deliver on these efforts.

[Ronne (Zeneca) | Zano @RonneTVR]

@AgoristN 🎯

[Zano Intern @Zano_Intern]

@fede_intern You're literally talking about @zano_project! Anyone can issue their own privacy tokens that inherit the same level of privacy as native $ZANO, along with the world's first private Proof-of-Stake consensus with hidden amounts. Learn more here: https://t.co/i3aCzoQWxn

[Ronne (Zeneca) | Zano @RonneTVR]

@GinoFPM @zano_project

[Zano @zano_project]

https://t.co/C3jl1hKlyV

[Zano @zano_project]

New to Zano, or know someone who is?

Our workshop from Common S3nse in Amsterdam is now online. @RonneTVR walks through setting up a wallet, making your first private transaction, and what you can do across the Zano ecosystem.

Full workshop below. 🔒

[Ronne (Zeneca) | Zano @RonneTVR]

@FreedomWallet Only freedom money 🔒

[Vini B 「thecoding.dev」 @vinibarbosabr]

Zano Confidential Assets is one of @zano_project 's biggest competitive advantages, imo.

• anyone can create tokens that benefit from a large anonymity set
• these are native assets, just like $ZANO

In this article we go deep into the CAs, like fUSD ↓ https://t.co/Jn7nAl0Qds