Nelson retweeted
For every business we integrate, thousands more could unlock the same benefits.
Less friction. More customers. More revenue.
@FinanceComputer makes it simpler than ever.
Stock.estate saw the opportunity. And acted.
They’re live!
Anybody with a repair streak nft they aren't using?
Over 450 days streak about to die 😑🥲
Help!
@xPortalApp
1
102
Nelson retweeted
elrond-erd-2:native deposits and withdrawals on @krakenfx have been reenabled.
We are working with all outstanding exchanges to be fully operational as soon as possible.
Nelson retweeted
A few quick notes
(1) Network. Supernova is live, running with remarkable speed and precision.
(2) Exchanges. Over the next 5–10 days, global exchanges and other independent partners will begin reopening deposits and withdrawals. The rollout is gradual by design. Each exchange follows its own rigorous internal process, built to protect users and keep the recovery smooth.
(3) Security report. An in-depth security analysis is still underway. Several critical elements are already mapped and understood, from the bugs and their fixes to the technical implications and the path to recovery. A few discussions with independent parties remain open. The findings are preliminary, but one stands out above the rest. The tools, methods, preparation, and coordination behind this attack appear to go well beyond those typically associated with amateur attackers. The observed sophistication bears the hallmarks of advanced, experienced, repeated threat actors, including groups operating at the level historically associated with hacker organizations such as Lazarus. Attribution is not yet confirmed, but it is worth stating this out loud: to have successfully defended our users against Lazarus, or another group of that caliber, is a milestone we are proud of! Huge respect to all independent partners, including global exchanges, who have mobilized with extraordinary speed for the greater good of protecting users and the network!
(4) Lessons. More importantly, the larger lesson goes beyond this incident. As an industry, we have entered an era of permanent, constant, unending war. Open-source financial infrastructure operates on a global battlefield, continuously exposed to increasingly sophisticated attackers, tools, and methods. Under these conditions, the traditional definition of security is no longer sufficient.
Three capabilities are becoming non-negotiable:
(a) a relentless defensive and offensive security tooling arms race;
(b) continuous, 24/7 red-teaming and penetration testing;
(c) blitz-speed detection, coordination, and response.
We have been intensifying precisely these capabilities over the past 3–6 months. What happened over the last few days is one visible incident among several potential threats that have been identified, contained, or neutralized through increasingly proactive security work.
This reality is not unique to MultiversX. Every major open-source stack, every blockchain (bitcoin and ethereum not excluded), and soon, every closed source software stack, will increasingly have to adapt to an environment where infrastructure is continuously and deeply probed, attacked, and tested. That requires a much more rugged approach to code. A more adversarial approach to architecture design. And ultimately, a fundamental rethinking of how safety-critical software is built and defended.
The three measures above are critical today. But over time, we will need to go much further and rethink security from the ground up for the new world we are actually operating in. Verifiably correct-by-construction software is about to have its moment and become fashionable very quickly. Reality has a way of accelerating standards. Not so much by preference, but by necessity.
Nelson retweeted
Is $EGLD crypto next cycle’s SLEEPING GIANT?
Like finding Solana in 2020? #MultiversX
Click HERE 👇
>> youtu.be/nW3h3J4wKSQ
Nelson retweeted
SUPERNOVA IS LIVE
Fix is deployed. Users and funds are secured.
The network is working beautifully.
Huge respect for all the partners involved in this mission-critical recovery, especially the team working day and night to get us here.
Nelson retweeted
we need some new code.
we need to review, audit, verify and test it.
the developers are on. we are working.
preparing a new release.
but it will remain pending for tonight.
We are preparing a new release for the next recovery attempt. An epoch change occurred during today’s attempt, so we need to test recovery across that epoch change before proceeding.
we thought there would be quorum on all shards before epoch change, shard 1 missed that window.
coding, testing, coding, testing.
Update:
The Mainnet restart is still pending.
Shard 1 did not complete the recovery transition in time, preventing its blocks from being confirmed by the metachain. Validators have been asked to stop their nodes while engineering assesses whether the restart can be retried immediately.
Please continue to wait for the all-clear: do not submit or rebroadcast transactions, or use EGLD and ESDT deposit and withdrawal routes through exchanges or bridges.
We will share the next confirmed steps as soon as they are available. Thank you for your continued patience and support.
Nelson retweeted
There’s a lot of talk right now about MultiversX downtime, off-switches, first halt, all of it.
Fine. Let’s go through what actually happened since launch, six years ago, from a validator’s chair.
I’ve run a node since day one. Before it was MultiversX. When the chain was still Elrond. You remember the weekends more than the marketing. The nights Telegram lights up. That’s the job.
People talk this week like the chain never broke before, or like someone pressed a button on my servers. Neither is true.
December 2021 — RIDE
Nobody asked us to stop nodes. The chain kept making blocks. Listing traffic, bots, timeouts. Unusable for hours. Congestion.
Consensus downtime: none. I didn’t reboot the server.
June 2022
multiversx.com/blog/incident…
VM bug. executeOnDestContextByCaller in a callback. Same shard. ~1.65M EGLD out of the wrap contracts, dumped on Maiar.
They paused DEX, WEGLD swap, bridge, public API send. Not the chain. The report says the blockchain was never turned off. Own API still worked. In-place upgrade, most nodes on the new binary in ~30 min. Users made whole.
Consensus downtime: none. Apps dark ~2 days.
May 14, 2025
multiversx.com/blog/sc-bug-i…
First real consensus halt.
transferValueAndExecute. Missing check. Huge wrapped USDC credit, then USDT. They called verified / red-line operators, community delegation, 25+ SPs. Enough to break 66%. Quorum died. Patch v1.8.13.0. Back in 2h30. 99.999% recovered. No users directly affected.
I wasn’t on that call. If you weren’t in that group you just watched it stall.
Consensus downtime: 2h30.
September 19, 2026
teapawt.org/MultiversX/status/2101…
Same idea, bigger.
VM atomicity. Invalid state already on chain. Official line: order-of-operations on an edge case. This time they asked everyone to keep mainnet nodes down. Hard fork from a checkpoint. That’s why it’s days, not two hours.
I stopped my own nodes after the announcement. Nobody flipped a switch on my servers. I can still refuse the upgrade. PublicKeyToListenFrom in my config.toml is empty. I never cleared it.
Should be back this afternoon. Call it ~4 days. ~96h.
The map
2021 RIDE: consensus 0
2022: consensus 0, apps ~2 days
2025: 2h30
2026: ~96h, restart this afternoon
SLA since launch:
Since genesis (July 2020.) : ~98.5h down → about 99.82% uptime.
Since 1 Jan 2026: only this one → about 98.5% this year.
We’ve had incidents. We’ve had downtime. This is just the first time it stayed down more than a few hours. Not a fairy tale about a button.
Those are the facts.
Update:
We have confirmed that a actor attempted to exploit a VM-level atomicity issue.
The attempt caused invalid state changes, and network progression remains paused to prevent any further impact. Engineering has prepared a fix and will validate it on a shadow fork.
Subject to successful testing, deployment to Mainnet will be coordinated with validators, exchanges and infrastructure partners.
In parallel, we are evaluating a targeted recovery approach designed to preserve finalized transaction history and legitimate user state while addressing only incident-related invalid changes. No action is required from users beyond waiting for the all-clear.
Please do not submit or rebroadcast transactions, or use EGLD and ESDT deposit and withdrawal routes through exchanges or bridges.
We will communicate again when there is confirmed progress to share. A full technical incident report will be published once the response is complete and the findings have been finalized.
Thank you for your patience and continued support while we work through this.
Nelson retweeted
1/22 I think the @MultiversX EGLD team & responding validators did an exceptional job coordinating containment under pressure. The bug was severe; the response deserves credit. These are real humans. Here is what the evidence supports, what remains open.
gist.github.com/kressm/8bf1d…

ALT Evidence review dated 22 September 2026. Supported: an integrated shutdown trigger; original contract directly calls a Barnard-gated hook. Approximately 76.68 million EGLD is supported as balances plus outflows, not an exact net mint. Not established: Foundation use of the trigger, exchange sales, or Supernova’s 600ms design causing the exploit. Based on pinned GitHub code and original transaction bytes; no exploit replay or validator logs.
Nelson retweeted
Running a node since D1 here.
We stopped ourselves after the announcement. Nobody has a button on my machine. And I can still say no to the upgrade if I want.
The tokens that hit exchanges got locked. They weren’t sold.
Of course there was a hack, I’m not pretending there wasn’t. I just don’t see the story people are spinning. Team and validators spent the weekend cleaning it up.
Ugly, we lost 100% uptime, but nobody’s funds disappeared.
EGLD has been totally exposed for its lies & hidden centralization today! ⚠️
3 days of downtime is only the tip of the iceberg: 76M EGLD (2.5x supply) was minted & partially sold!
EGLD did not halt; the foundation used an off-switch!
All consequences of its reckless design! 🧵
Unlike a normal chain halt, where the chain stops due to a "consensus failure/disagreement", this was far, far worse. Instead of the chain stopping because an "inflation bug" caused consensus to fail, it kept going...
That is what allowed the hacker to actually send their EGLD into exchanges & cause considerable harm. What comes next is even more unbelievable. As I was wondering how it was even possible to shut down a chain with 3k validators in 66min...
That is what made me uncover the next bombshell: There is a literal foundation-controlled off-switch in the code!!!
The Off-Switch
Every mainnet node runs with a hard-fork trigger enabled that listens for a message signed by one specific public key. That is a remote stop switch held by the Foundation! We cannot know for sure if they pressed that switch, but it is highly unlikely they could have stopped the chain that quickly otherwise & the fact that it even exists is bad enough!
This is all a direct consequence of the shortcuts they had to make to bring a sharded chain down to 600ms...
Reckless Design
Sharding comes with certain trade-offs: EGLD claimed to overcome these trade-offs through its unique design. Turns out, in reality, those trade-offs had some extreme consequences we are feeling now:
EGLD sharding splits every transfer into a sender-shard debit & a destination-shard credit that must be reconciled by hand, & on one path the credit had no debit: a money printer. With no global supply invariant, finality before execution, & no protocol-level freeze, the only fix was manually shutting down the chain & a hard fork erasing the "final" history!
Lack of Disclosure
Given what I just explained, you can judge for yourself whether the team's disclosure is adequate. I argue it absolutely was not. The fourth screenshot shows their communication on the matter so far & exactly what they failed to mention
Including the mint, the hackers' success & the off-switch!
The fact that it took my own chain & code analysis to reach these conclusions tells us the team cared more about minimizing PR damage than properly disclosing the incident. At least with this piece out, they will not be able to get away with that anymore & will have to also include this information in their report
The community deserves to know what is really going on, how centralized EGLD really is & how the tech is not a magical panacea but instead comes with serious trade-offs
Chain Analysis
The record is clear, all on a public chain for all to see. The attacker exploited this vulnerability in the chain & managed to mint 76M EGLD! Over 2.5x the supply! Along with 430M bridged USDC, about 430M bridged USDT & 5,540 bridged WBTC...
The hacker then proceeded to split these into 16 wallet addresses & then send EGLD to multiple exchanges. If we look at the timing of when these exchanges "froze" EGLD, we see that MEXC did not act in time & it perfectly corresponds with very suspicious selling activity on that exchange, which was not even arbitraged out when the full freeze took effect. We cannot tell whether the hacker managed to exit the exchange afterward, but they certainly could have!
Which means the hacker was likely able to walk away with around $1M USD, effectively defrauding the exchange in the proccess, by leveraging this EGLD vulnerability
Please look at the visuals, as they provide all of the supporting evidence that can also be independently verified with publicly available information
Conclusion
This is BTC's 2010 inflation bug & ETH's 2016 DAO's hack rolled into one. That this all happened in 2026 is even more embarrassing
Unlike those historic failures, there was no full disclosure of the problem as it was happening. People deserve to know; we are blowing the lid off this story now!
This is also nothing like SOL's historic downtime, which involved network halts caused by bugs. Something that has happened in over two years. While EGLD managed to beat SOL in total downtime with this single incident!
SOL also never ever had an off switch! The irony & I apologize; some degree of schadenfreude cannot be helped in my situation. As the EGLD community was one of the loudest spreading that false narrative. Turns out it was unknowingly a projection!
The biggest red flag is still the team itself, after my fallout with EGLD last year. The toxicity & dishonesty became too much to bear
This will likely trigger another ad hominem campaign against me, as it did last time & as it did for other influencers/journalists/thinkers. Fortunatly, I am specialized in weathering the storm. While these facts are undeniable & mostly speak for themselves
EGLD certainly has some good technology; we can learn something from everyone. However, what we saw here over the last few days is beyond the pale
That's where the value lies: In also understanding the character of a chain's leadership, especially at an early stage, as even with decentralized governance, bad leadership can still mess it all up!
This is a truly worst-case scenario for a blockchain; there are very few examples of this level of collapse in blockchain history. After such an event, we have to question the competence & the wisdom of the underlying design choices
EGLD's design is flawed & reckless, making centralization trade-offs other chains would never even dream of. All while claiming to be holier-than-thou
It is never too late to change our minds in the face of new evidence; please study the supporting visuals for yourself. The truth cannot be credibly denied
What occurred here is undeniable, while the silence of EGLD's leadership speaks louder than words: 🎓
Nelson retweeted
machines and people were up for the 4th day.
rehearsing, coding, making sure everything is clean and nice. we do not want shortcut solutions, but the best possible even in the case of hard fork.
when everything is visible, everything is public, everything follows the rules of decentralised, permissionless world with proofs and everything.
some people are spreading lies are spreading hate and laughing on the misfortune of others. so be it. we are in the trenches building and we will get out of this stronger.
yes, even in case of a pause and restart and hardfork you can do it without whitelists / blacklists and doing it with coordination of validators, where every validator decides. it takes more time, it takes more code, because we are validating everything, and actually the validator code validates everything. there is no blind trust, but verify everything on your own machine.
p.s. the inflation for the last year was 4.3% ish, there was actual no dilution. no funds were allocated / used for acceleratorDAO. just as information.
Update:
Validator rehearsal planned for tomorrow
We are preparing a coordinated recovery rehearsal on Devnet tomorrow, Tuesday, Sep 22, 2026, tentatively at 12:00 UTC, and invite validators to participate.
The protocol fix is prepared, and the simplified recovery procedure has completed a successful first internal trial. We will repeat the trial internally tomorrow morning with a wider transition window. Subject to successful validation, we plan to proceed to public Testnet, followed by the Devnet rehearsal.
To prepare for the rehearsal:
- If you already operate Devnet nodes, please ensure they are synced.
- If you would like to participate but do not currently run Devnet nodes, you can start a Devnet observer or squad using start-in-epoch mode and allow it to sync ahead of tomorrow’s rehearsal.
We will provide the rehearsal release, including the new binary and configuration, for installation through the usual upgrade process. The start time and operational instructions will be confirmed in this channel before the rehearsal.
If testing and the rehearsal are successful, we plan to proceed to the coordinated Mainnet rollout. Its timing will be confirmed separately with validators, exchanges and infrastructure partners.
Mainnet nodes must remain stopped until explicit restart instructions are issued. The preparation above applies only to Devnet.
Thank you for your support, it means the world to us. We keep building.
Nelson retweeted
A few notes, only for some crypto people.
If you’re not in crypto, please keep scrolling. Nothing to see here.
1. Is Supernova live and delivered?
YES. After years of work, it’s live. It works. It’s delivered.
2. Does this change your life?
Yes and no. Yes, if you’re building something cool and know how to find users.
No, if you're not looking to building anything.
3. Does the Finance Computer use MultiversX?
YES. Does it use EGLD? Yes.
4. Is the Finance Computer a product for crypto people? Another thing for crypto people to generously bless with their omniscient wisdom?
No. It’s not built for crypto people.
Their omniscient wisdom, fortunately, doesn’t apply here. :)
5. Will the Finance Computer spend every day talking about crypto?
No. Plain and simple.
This is a distinct B2B distribution product.
It targets businesses, not crypto users. It speaks their language, solves their problems, and focuses on delivering a service they actually want to use. Less explaining crypto. More of making money actually work better.
6. Now that Supernova is live, will there be new use cases?
YES. That’s precisely the point.
The Finance Computer is a new interface for bringing these capabilities into the real world.
Different audience. Different language. Different distribution. Same underlying rails.
7. Will there be announcements and partnerships?
YES.
8. When when when, sirs? Can we have everything today?
No. Not everything today.
During next week and September, we’ll start sharing the first business use cases. Something merchants and companies can use in a simple way. Beyond that, we’ll have some focused workshops around what the Finance Computer can actually unlock for businesses.
Simple language. Clear benefits. Clear next steps. Use cases businesses can use today.
9. Do we have strategic use cases that validate the Finance Computer and meaningfully accelerate momentum?
YES. Some very interesting ones. That is the entire point of the finance computer. Let those be cooked. We announce them when they are shipped, or just ready.
10. So when do we get all the information?
At the right time. What I can say is this: this quarter will be defining for both the Finance Computer and MultiversX from a business adoption and real-world use case standpoint.
We have shipped a massive infrastructure upgrade, with a completely new interface, that speaks a different language for the business world. Taking that further is the focus now. Crawl, walk, run.
11. Isn't it unprofessional or impolite to block trolls who fill my posts and timeline with NPC rubbish?
No. We worked for two years on Supernova. Actually, much longer. We set out to deliver an extremely difficult technical milestone, and we delivered it.
Together with the entire team, I am very proud of that milestone. We now stand at the very frontier of performance, on the right ground, with a clear suite of money services ready for the business world.
So yes, trolls will disappear from my timeline. Better for everyone that way. In computer science, we have a technical term for this. It’s called garbage collection. Works surprisingly well, highly recommended. :)
12. Are we here to solve all the world's problems?
No. We’re here to build a great product and deliver it.
Take what is useful. Build on it. Adapt it. Move forward. That’s it.
13. But but but, isn’t this supposed to be for everyone?
No. Not everything needs to be for everyone.
What we are building stands for something specific. A better way of accessing, moving and programming money. If it resonates with you, and you need it, great. Come build, use it, contribute, push it forward. If it doesn’t, also great. Life is short. Find something else that does.
14. One final thing.
Crypto, generally, has gotten so toxic that it feels more and more like an autoimmune disease, the body eating itself from the inside. We are in the process of treating that toxicity. Changing the focus, applying more effort on money used in the real world, communicating to the right distribution target, and spending less time on things that are clearly misaligned.
Simple steps can go a long way. That’s the direction.
/end of professional rant :)
—------
Ps. That said, for the rest of the cool people here, the Finance Computer makes things simple for real world money movement adoption. It abstracts rocket science technology, and makes things just work.
Next week we are sharing some simple use cases that enable businesses to take this product and use it. It also enables you as an individual to find businesses you are close to, or love, deliver this to them, and potentially make some money as they adopt it.
Anyway. With these milestones delivered, and the new Finance Computer unveiled, we have officially entered the adoption phase.
My Supernova ID ✦ Class of 2021
1,878 days onchain - here before the 600ms era begins on 10 September.
Reveal yours: supernova.multiversx.com/
1
23
407
Nelson retweeted
🚨 DeepSeek API pricing can DOUBLE during peak hours.
The annoying part?
The API doesn’t tell you which rate you’re paying. 💀
So today I’m launching DeepSeekBar 🐳
A tiny macOS menu bar app that shows your real DeepSeek API spend at a glance.
💸 See exactly what you’ve spent
🐳 Know when you’re on cheap pricing
🔓 100% open source
Nelson retweeted
✅ Secure Proof of Stake
✅ Meritocratic validator selection
✅ ~3,200 active validators
✅ Zero equivocation
✅ Formally verified VM
✅ Fully sharded, horizontally scalable
✅ Parallel cross-shard execution
✅ ~$0.0002 per transfer
✅ Unconsumed gas refunded
✅ Gas abstraction
✅ Onchain 2FA
✅ Protocol-native tokens
✅ Fungible tokens
✅ Non-fungible tokens
✅ Semi-fungible tokens
✅ Multi-token transfer
✅ WASM smart contracts
✅ Custom-built Virtual Machine
✅ Native VM elliptic curve operations
✅ Multi-VM customizable chains (Lightspeed SDK)
✅ Reproducible smart contract builds
✅ Upgradeable contracts
✅ Chain Simulator
✅ Millisecond-precision smart contract timestamps
✅ Mature onchain governance
✅ KPI-gated emissions
✅ Developer royalties
✅ MCP integration
✅ Agentic Commerce Stack (x402, UCP, ACP, AP2)
✅ MX-8004 agent identity standard
✅ Agent Builder Hub
✅ Carbon negative
✅ Validators run on 4 cores and 8 GB RAM
🔜 <250ms finality
🔜 600ms blocks
🔜 Rebuilt consensus engine
⏳ Protocol-native Zero Knowledge proof
⏳ Instant delegation migration
⏳ Guardian activation at wallet creation
Built different.




















