
A bird in a cage is safe but God didn't create birds for that. || P2P Digital Cash advocate. || QA at @Zano_Project.
Joined March 2015
- Tweets9.3K
- Following737
- Followers1.1K
- Likes9.1K
Gonbat | Zano | π¦π· retweeted
No ones calling for the 5 Bitcoin mining pools that make up 80% of hash to reject the hackers transactions
No one is calling for the 18 Solana validators needed to reject the hackers transactions to do so
No one is calling for Ethereum to roll back the chain which they have done previously for a $150m hack
But the are screaming for THORchain to somehow do it?
Roll back Ethereum again if you're so upset about it
Gonbat | Zano | π¦π· retweeted
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.
Gonbat | Zano | π¦π· retweeted
Replying to @Mr_Kwibs
Innovation comes with risk. You can sit back and do nothing, and nothing will happen to you, but that's not how you push the boundaries of freedom technology. I came for the values, and I'll stay because of them. Onwards.
I vibecoded this wrapper a while ago, glad to know it doesnβt actually violate ToS, I was expecting a ban at any moment π€£
Welcome back to Hermes Agent, Claude
New official plugin that uses Claude SDK without the tradeoffs to enable Claude Code subscriptions to work in Hermes Agent again!
Check it out and install it here: hermes-agent.nousresearch.coβ¦
5
227
Gonbat | Zano | π¦π· retweeted
Fuck the Doomers.
Fuck the Decels.
Fuck the Commies.
Access to AI is a right.
Owning compute is a right.
Come and take it.
Over my dead body.
Join us in the fight, anon.
Gonbat | Zano | π¦π· retweeted
Replying to @OrcaRouter @Gio_Patruno
Boooring!
As if Lazarus didnβt have one already, meaning a public release can only help defenders, but I guess itβs too much liability.
Thank you for your work, time to pass the torch.
Grace period of no-KYC instant swaps just ended.
DEX time.
zAnons have recently experienced issues when trying to swap Zano on swap platforms.
Let me give you a thorough explanation of why that is, and how were planning on solving that.ππΌ
Since about 6-8 weeks ago, MEXC has changed their policy on swap providers, and is now asking them for KYC on each swap request.
Swap platforms have always been a great way to tap into the liquidity of major exchanges but without having to register an account and do KYC yourself. Until now.
This is the reason why almost all of the 20+ swap platforms that offered $ZANO swaps, have now temporarily disabled us. Our swap providers are currently looking into alternative liquidity solutions other than MEXC.
All-in-all, I really look forward to the days when you can acquire native $ZANO and Confidential Assets permissionlessly and without KYC on @THORChain. More and more exchanges will go the full compliance route, which emphasises the importance of platforms such as THORchain.
Additionally, once the Zano Execution Layer is live (aka ZEL), you'll be able to buy wrapped Zano on places like Uniswap, and them simply bridge back to native Zano (also permissionlessly).
Thank you for listening to my rant, and yes, I dislike centralized exchanges.
Use DEXes and self-custody wallets, the way crypto was meant to be!π―
6
262
Claude: βIβm sorry, I canβt help you with that requestβ¦β
π¨HUGE: China's Kimi AI just scanned nearly ALL of Bitcoin's open-source code, flagging almost 8,000 flaws.
The Bitcoin Red Team has now covered 501 projects, finding 1,280 critical or high-severity issues, with maintainers validating and patching flaws.
The team leaned on Kimi K3 as its main weapon after US labs restricted access to their models for security work.
3
111
Gonbat | Zano | π¦π· retweeted
There is a critical vulnerability being actively exploited on BTCPay Server, which can result in the loss of funds.
Please update your BTCPayServer to 2.4.2 by going to Admin Dashboard -> Server -> Maintenance -> Update & verify the 2.4.2 version string in the footer.
If you are unable to update right away, turn off your BTCPay Server to prevent unauthorized access until you can update.
Gonbat | Zano | π¦π· retweeted
Replying to @AradhyeAgarwal
Wrong approach altogether, agents should get their own accounts, their own balance, in their own VM. I limit the scope of anything I give them so that I can still sleep if/when it gets compromised.
More guardrailsβ¦ thanks, surely Lazarus Group canβt afford Kimi K3, therefore I have no need to use your models to defend myself, brilliant! π
Replying to @claudeai
Opus 5 is stronger than Opus 4.8 on cybersecurity tasks. But it remains substantially behind Mythos 5 at developing exploits.
Its safeguards are designed to allow developers to identify and fix software vulnerabilities, while blocking high-risk uses.
1
179
Vibecoding + open source is pretty powerful
Instead of installing 100 apps, I can point my agent to their sources and have it read how they implemented X feature, then add just what I need to my setup.
Reminds me of Kevinβs βabsorbeβ power from Ben 10.
1
102






















