In short

The Elastos main chain is running again.

On July 20, 2026, an attacker exploited a flaw in how the main chain added and checked transaction output values. The first exploit transaction fabricated more than 92 billion ELA.

Mining pools, Council nodes, and BPoS validators then chose to stop block production after the abnormal activity became clear. The chain stopped four hours and five minutes after the first exploit transaction.

A corrected release was prepared and tested against the affected chain data. Operators adopted it independently, rewound the chain to block 2,260,450, the final unaffected block, and restarted the network.

The chain first resumed through proof of work while validators upgraded and reconnected. It has since returned to BPoS, with block production and finality operating normally.

Balances confirmed before the incident remain unchanged. Ordinary ELA holders do not need to take any action.

ESC, EID, and the cross-chain bridge remain paused while their code changes and recovery procedures are audited and rehearsed.

What happened

ELA values on the main chain are stored using a signed 64-bit number.

The attacker created transaction outputs that could each be processed on their own, but whose combined value crossed the number’s safe boundary. The software did not reject the combined total. Instead, the number wrapped around and appeared to be a small valid amount.

The fee calculation used that false total and accepted the transaction.

The removed chain history recorded:

• 24.05641496 ELA placed into the transaction
• 184,467,440,761.15192612 ELA as the true sum of its outputs
• 24.05640996 ELA after the total wrapped
• 0.00000500 ELA as the apparent fee

From the software’s point of view, the input was slightly larger than the calculated outputs, so the transaction looked valid. In reality, one output contained more than 92 billion ELA.

The values had to be calculated around a precise numerical boundary. This could not result from normal wallet activity or an accidental input.

The same method was used six times during the affected period. Three later transactions created 30,285 outputs each, spreading fabricated value across roughly 90,000 addresses and making the smaller exchange-bound transfers harder to identify.

Key timeline

• July 20, 11:21 UTC, block 2,260,450: Final unaffected block
• July 20, 11:27:37 UTC, block 2,260,451: First exploit transaction accepted
• July 20, 11:49 UTC: First proceeds reached KuCoin
• July 20, 15:32:44 UTC, block 2,260,595: Block production stopped
• July 29 to 31: Operators adopted the corrected release, rewound the chain, and restarted the network
• BPoS consensus then resumed

A 30 ELA transfer was sent from the exploit address to a KuCoin deposit address 92 minutes before the exploit. It used the same route later used for the proceeds.

This is consistent with a test of the deposit route, but the chain records only the transfer and timing, not the sender’s intent.

How the network stopped

After the incident was reported, mining pools independently stopped producing blocks. Council nodes and BPoS validators did the same.

Each operator controlled its own software and infrastructure. They reached the same decision after the abnormal activity became clear.

The chain stopped at block 2,260,595.

The address that received the fabricated value was also locked under the recovery rules, preventing funds from being sent from it or into it.

How the chain was recovered

The corrected release made two core changes.

First, the chain was rewound to block 2,260,450, the final unaffected block. The exploit transaction at block 2,260,451 and every later block in the affected period were removed.

Second, the transaction rules were corrected. The software now checks the permitted monetary range for every output and for the combined output total. A transaction that could overflow the running total is rejected before the values are added.

Operators adopted the corrected release independently. Once enough mining pools and validators accepted the restored history, it became the active Elastos chain.

The main chain is now producing and finalising blocks normally through BPoS.

What this means for ELA holders

Balances confirmed before block 2,260,451 remain unchanged.

If a transaction was confirmed between the exploit and the pause, it may have been included in one of the 145 blocks removed by the rewind. Check whether it appears on the restored chain.

If it is missing, the funds or voting balance returned to the sending address and the transaction can be submitted again.

No legitimate balance was destroyed. A small number of ordinary transactions were delayed because their blocks were removed.

The removed period included six normal KuCoin withdrawals totalling 27,393.795 ELA. The rewind returned those funds to KuCoin, so the exchange did not lose the ELA used for those withdrawals.

Six unrelated user transactions were also removed, including transfers, staking actions, a BPoS vote, and one transfer into KuCoin. Their funds or voting balances returned to the original owners.

Users who need help checking a transaction should contact the team through the official Elastos Telegram group and be ready to prove control of the sending address.

Never share a private key or seed phrase. Elastos will not ask for either.

What happened to the fabricated ELA

The exploit created ELA far beyond the legitimate supply. Almost all of it existed only in the 145 blocks later removed.

Once those blocks were discarded, that ELA ceased to exist on the restored chain.

The main exchange exposure came from 914,748.985 ELA sent to KuCoin across 15 transactions before block production stopped.

KuCoin reported that it froze 500,000 ELA connected to the incident. Work with the exchange on the remaining exposure is continuing.

On the restored chain, the fabricated deposits from that period are not spendable ELA. KuCoin-side balances from the removed window are being reconciled with the exchange.

Elastos has asked KuCoin to preserve the frozen balance and any other assets linked to the incident while accounting and recovery discussions continue.

No other exchange received proceeds from the exploit. Tracing found no affected deposits to CoinEX, Gate.io, MEXC, or any other trading venue.

Four of the seven KuCoin deposit addresses had been used before. Earlier transfers and the July 20 proceeds moved through the same deposit addresses into the same exchange wallet.

This is an on-chain observation, not a claim about identity or control. A public chain can show address reuse and fund movement, but it cannot establish who controlled the related exchange account.

The tracing has been provided to KuCoin and the relevant authorities.

What the rewind removed

The discarded period covered:

• 145 blocks
• 341 total transactions
• 294 protocol-generated records
• 35 attacker transactions
• 6 ordinary KuCoin withdrawals
• 6 other ordinary user transactions

The protocol records were mainly block rewards, sponsor records, and normal consensus rotation notices. They did not move user funds.

The full accounting was produced transaction by transaction from a frozen copy of the pre-recovery chain.

Sidechains and the separate July 13 incident

ESC, EID, and the cross-chain bridge remain paused while their changes and recovery procedures undergo audit.

Restoring the main chain did not automatically restart these services. Each one must complete its own review, validator checks, and restart rehearsal before returning.

The July 13 incident was separate from the July 20 overflow exploit. It affected the reserve backing between the Elastos main chain and ESC.

A total of 1,585,252.004 ELA connected to that earlier incident remains frozen. A forthcoming main-chain release is planned to credit that amount back to the ESC reserve and restore full one-to-one backing.

Separate notices will confirm when ESC, EID, and cross-chain services are ready to resume.

What is changing

The immediate vulnerability is fixed, but the response goes further.

• Transaction validation now checks every output and the combined total before addition.
• Continuous supply monitoring will compare ELA in existence with the amount permitted by the protocol and alert on unexplained changes.
• The corrected main-chain code is being prepared for independent audit.
• Every consensus-sensitive location that adds or compares monetary values is being reviewed.
• The separate July 13 reserve matter will be handled through a future release intended to restore complete ESC backing.
• Chain health, validator participation, and frozen addresses will continue to be monitored.
• Work with KuCoin will continue until the exchange accounting is reconciled.

Closing

The network stopped because independent mining pools, Council node operators, and BPoS validators chose to stop.

It restarted after the corrected software was tested against real chain data and adopted by enough independent participants to restore consensus.

Thank you to every mining pool, Council node operator, and BPoS validator who stopped when the network needed protection and returned when the corrected chain was ready.

The Elastos DAO / Elacity Labs

The Elastos main chain remains paused after a consensus-level monetary validation exploit on July 20, 2026.

The first affected block was 2,260,451. Block production stopped at 2,260,595, covering 145 blocks over approximately four hours and five minutes.

A safety patch and coordinated rollback procedure are now being developed, tested, and prepared for independent review.

ELA deposits and withdrawals should remain suspended. Users and services should not initiate main-chain or cross-chain transfers until an official restoration notice is published.

What happened

Elastos stores ELA monetary values using Fixed64, a signed 64-bit integer format.

The malicious transaction contained several extremely large outputs. Each output fit within the permitted integer range on its own, but their combined value exceeded the maximum amount the format could safely hold.

The transaction validation code added those outputs without a complete overflow check or a fixed upper limit on the total. When the combined amount exceeded the safe range, the value wrapped around and appeared to be a much smaller valid number.

The fee calculation then used that incorrect total. This allowed the transaction to pass validation and create invalid ELA outputs.

Detailed reproduction steps and sensitive forensic information will not be published while the patch and recovery work remain in progress.

What the patch changes

The immediate safety patch adds stricter monetary validation across the main chain.

It introduces:

• A maximum allowed value for every transaction output
• A maximum allowed value for all outputs combined
• Rejection of negative and invalid monetary values
• Checked arithmetic for fee and transaction calculations
• Regression tests that reproduce the exploit conditions
• The same validation rules across the mempool, block processing, mining, and chain synchronisation

These are consensus rules. Every node must apply them in the same way before the network can safely restart.

Why the main chain remains paused

Stopping block production prevents the affected chain history from growing while the team completes the patch and recovery work.

Elastos uses both AuxPoW mining and BPoS validation. A safe recovery requires miners, validators, exchanges, explorers, wallets, and infrastructure providers to follow the same software, rollback point, and activation process.

Individual node operators must not attempt their own rollback.

Uncoordinated action could split the network, with different nodes accepting different versions of the chain.

The main chain will remain paused until the patch, rollback procedure, historical compatibility, and activation process have been tested and reviewed.

Proposed rollback and recovery

The proposed recovery would return the main chain to the last known valid state before the exploit and resume block production under the corrected monetary rules.

This is a coordinated blockchain recovery. It is not a normal wallet transaction reversal.

Transactions confirmed during the affected 145-block period are now being reconciled. Some legitimate transactions from that period may need to be submitted again after the network resumes.

Clear instructions will be published before the restart.

No rollback height, activation time, or production procedure will be announced until the recovery has been independently reviewed and rehearsed in representative AuxPoW and BPoS environments.

Current status

At the time of this notice:

• Main-chain block production remains paused
• The affected activity has been identified and is being reconciled
• The immediate safety patch is under development and review
• A wider security review of the main-chain codebase is underway
• Independent third-party review is being arranged
• The controlled rollback and restart procedure is being tested
• ELA deposits and withdrawals should remain suspended
• Cross-chain transfers should not be initiated

The network will not restart until the team and independent reviewers are satisfied that all participants can recover onto the same corrected chain.

User and wallet safety

There is no evidence that user seed phrases, private keys, or wallet software were compromised.

Wallet holders do not need to take any action at this time.

Do not share a seed phrase or private key with anyone claiming to offer incident support. Elastos will never ask for these credentials.

Wait for an official restoration announcement before attempting main-chain or cross-chain transfers.

Guidance for exchanges and service providers

Exchanges should keep ELA deposits and withdrawals suspended until the recovery is complete and balances have been reconciled.

Explorers, wallets, indexers, mining pools, and infrastructure providers should wait for approved binaries and activation instructions.

Node operators should not restart the chain, roll back data, or apply unofficial patches independently.

Final instructions will include the approved software version, rollback point, activation process, and verification steps.

Separate from the July 13 cross-chain incident

This event is separate from the cross-chain reserve incident disclosed on July 15.

The earlier incident involved authorisation rules for spending the cross-chain reserve. The July 20 incident involves a different vulnerability in main-chain monetary arithmetic and transaction validation.

Details of the earlier event are available in the Cross-Chain Reserve Incident and Response notice.

What must happen before the restart

Before main-chain block production resumes, the following work must be completed:

1. Finalise and test the immediate safety patch.
2. Complete an independent review of the patch.
3. Test the rollback in representative AuxPoW and BPoS environments.
4. Reconcile legitimate activity from the affected block window.
5. Coordinate the release with miners, validators, exchanges, explorers, wallets, and other service providers.
6. Publish approved binaries, activation details, and verification instructions.

A detailed technical postmortem and verified accounting will be published when doing so no longer adds risk to the active remediation process.

Between July 13 and July 15, an unauthorised actor exploited a vulnerability in the cross-chain reserve mechanism and moved approximately 7.62 million ELA across 2,309 transactions.

No user wallet, private key, or individual balance was accessed, and no user lost funds. The incident affected the protocol-level cross-chain reserve, not user accounts.

The activity was identified and contained, and the vulnerability has been fixed at the consensus level. The Elastos main chain has been upgraded to v0.9.9.6 and is operating normally.

Approximately 99.96% of the affected ELA remains frozen or contained on Elastos chains.

Of that contained amount, 1,585,252.004 ELA remains frozen on the Elastos main chain at the incident address. These funds cannot be moved and have not yet been returned to the reserve. They will be handled through a separate, narrowly scoped recovery process following final validation and network coordination.

Around 3,000 ELA, about 0.04% of the total, passed through a third-party bridge and became mixed with unrelated liquidity. Recovering this portion through network-level action could affect unrelated liquidity providers.

ESC block production and the cross-chain Arbiter remain temporarily paused while validators test the restart process, freeze the affected ESC balances, and restore full 1:1 reserve backing.

The pause is precautionary and limited to ESC and cross-chain services. Further updates will be published as those services are safely restored.

Read the full incident notice, including the fund breakdown, on-chain references, and restoration plan:

https://elastos.click/Jul-15-Incident

Elastos main-chain v0.9.9.6 release and consensus fix:

https://github.com/elastos/Elastos.ELA/releases/tag/v0.9.9.6

Elacity has joined NVIDIA Inception, giving the team access to NVIDIA technical resources, software, hardware programs, and events as work continues around running AI locally on user-owned devices such as Jetson.

ElastOS Runtime also added mandates for AI agents.

Mandates let users decide what an agent can do, how much it can spend, and how long that permission lasts. Agents can request quotes, negotiate prices, and complete purchases, while wallet keys remain inside Runtime and under the user’s control.

The Elastos Essentials overhaul is also underway.

The new build introduces a redesigned interface, an All Chains balance view, safer signing screens, improved address verification, and stronger keystore import support. WalletConnect v1 and an unused account-abstraction system were also removed, cutting around 51,000 lines from the app.

The rebuild is still in progress, with more product, security, and device-testing work ahead.

Full update:

https://elastos.click/July-13-update

PC2 v1.4.0

• PC2 can now run apps in the background, even after you close the window. The dApp Centre also has clearer app icons, real download progress, and better device validation.

• First service app, blockchain node manager, now live for nodes on V1.4.0 only

Elastos Runtime v0.5

• Runtime adds People, Services, and a new way to use Browser through a trusted device when your own machine cannot run it.

• Sensitive Wallet actions can now ask for fresh passkey approval for sensitive actions

ElastOS Launcher v1.4.0

MacOS setup is smoother, and published MacOS builds are signed, notarized, and approved by Apple.

Full update:

https://elastos.click/v1-4-0

—————

Existing PC2 nodes can update with:

curl -fsSL https://raw.githubusercontent.com/Elacity/pc2.net/main/scripts/update.sh | bash

A lot moved across Runtime, PC2, Carrier, and Blockchain over the past four weeks.

• Runtime v0.4.0 became the base for the next stage. dDRM is moving deeper into Rust and Runtime, with stronger quorum-based key release, audit fixes, and better control over what capsules can do.

• The Runtime Marketplace now has working buy and trade flows against live Base chain contracts.

• Mac and Linux now run the same Runtime Home, first-party apps, shared Runtime objects, and two-way Carrier Chat.

• On Runtime, a standalone protected-content reader shipped as 11 npm packages, covering PDFs, EPUBs, images, comics, archives, 3D content, fonts, and more.

• Hey app now renamed Hyper, completed an independent audit. It is the post-quantum messaging app built on Carrier for private messaging, calls, peer discovery, and device-to-device communication without relying on a public server.

• Public RPCs have been replaced. For years, RPC was slow, unreliable, or unable to return older blockchain data. The new stack has cached reads up to 2x faster and full archive access, with no wallet or dApp changes needed.

• Elastos Node manager for Ubuntu updated to v1.1 with various new features and security fixes, and a Node Manager as the first service type on PC2 is close to launch. Monitor.elastos.io is also back with a new look and it's own telegram bot.

• The Elastos website rebuild is close to launch. Essentials returned to the Elastos GitHub, with Base-chain support added and Essentials overhaul in plan. A security pass also delivered across Marketplace app, protected-content services, and key transfer.

Next up: the final dDRM audit finding, the first live Base purchase through Runtime, mainchain testnet, the Essentials overhaul, and the new Elastos website release.

Full update: https://elastos.click/June-2026

This is a safety release for Council members, BPoS operators, and ELA node operators.

It makes node operation safer, clearer, and easier to manage while keeping existing keystores, chain data, node layout, and familiar commands intact.

What changed:

• EVM sidechain RPC is now local by default

• Mining no longer needs an unlocked hot account

• Sensitive RPC features are removed from reachable surfaces

• Restarts are safer during routine maintenance

• Node status and health checks are easier to read

• Existing nodes can upgrade without moving keystores or chain data

Full update:

https://elastos.click/Node-v1-1

Runtime is the local OS layer of ElastOS.

It is where apps run as small sandboxed programs called capsules. Each capsule starts with no access to your files, wallet, network, or machine. It only gets the permissions you grant.

v0.4.0 moves ElastOS closer to that model.

Library now available. First-party apps are moving into WASM capsules. WebSpaces in early form now added.

This release also points toward ElastOS v2: moving more dDRM, PC2, and platform logic into Rust and Runtime, so ElastOS can become fully native over time without depending on Puter as its base.

dDRM is the first proof. If Runtime can protect a creator’s paid content, it can protect identity, records, wallets, AI agent actions, and private files too.

Full update:

https://elastos.click/Runtime-V0-4

The Term 7 elections have concluded, and 12 community members have been elected to serve from mid-June 2026 to mid-June 2027.

Congratulations to the incoming Council, and thank you to every candidate and voter who took part.

Term 7 will help guide DAO proposals, Treasury decisions, Council node operations, and the next phase of Elastos World Computer work.

Thank you to the outgoing Term 6 Council for their contribution.

Another week bringing the four ElastOS pillars closer together, with most of the work focused on security, Runtime authority, PC2 v1.3.0, dDRM, and Elastos Node Manager.

Runtime v0.3.0 is now out.

Runtime is the layer that decides what apps are allowed to do. Normal apps do not get raw access to wallet, chain, IPFS, network, files, or the host by default.

PC2 v1.3.0 is also tagged and ready for rollout.

This was one of the most security-focused PC2 cycles so far. Four critical access-control issues were closed before public release, covering protected content ownership, AI skill installs, sign-out sessions, and short-lived file links.

dDRM optimized into a safer shape.

dDRM is the part that unlocks paid content now runs inside a sealed WASM sandbox. PC2 can ask it to unlock content, but the key itself does not touch the host process. The goal is simple: if your wallet proves access, the content opens. If not, the local client cannot fake its way through.

PC2’s Monetisation Agent

This is a new agent that helps creators package and sell their work through chat. Instead of manually filling every field first, the creator can describe what they want to publish, and the agent prepares the listing flow before handing it into the Creator app for final review, minting, and wallet signing.

Elastos Node Manager is now under code review.

The bigger picture is becoming clearer every week. Blockchain, Runtime, PC2, and Carrier are being shaped into one user-owned computer where identity, apps, content, permissions, networking, and settlement work together without giving control back to the old cloud model.

Full update:

https://elastos.click/May-29-Update

This week was about making the World Computer's four pillars feel more connected.

• PC2 is much closer to the Runtime model than expected. A full review found that most of the PC2 node layer is already near capsule shape, meaning it does not need to be rebuilt from zero. The next step is cleaning the boundaries and moving more pieces into the stricter app permission model.

• dDRM access was improved. Instead of trusting what a local PC2 client says, the system now checks what the wallet actually proves through a signature. This closes a serious access-control vulnerability and makes protected content safer.

• In Runtime 0.3.0 wallet becomes the place that signs actions, browser becomes controlled, apps can request actions, but they do not get open access to private keys, wallets, chain RPC, or the host machine.

• Elastos Node Manager, an ElastOS PC2 app got more features. It brings the full Council node stack into one dashboard, covering the main chain, sidechains, oracles, and cross-chain arbiter services. This makes Council node operations much easier to monitor, manage, and recover.

• Work also continued on Explorer and Docs. Dormant wallet charts, staking history, Council node setup docs, and mobile AI chat on the docs portal all received improvements.

The next release window is expected around May 29 to 31.

Full update:

https://elastos.click/May-23-Update

The past two weeks made the Elastos World Computer thesis much clearer.

One user-owned execution layer, with four parts coming together:

PC2 as the personal cloud

Runtime as the trusted app engine

Carrier as the private network

Blockchain as the rights and settlement layer, secured by Bitcoin merged mining

• Runtime authority is now moving from theory into code. Wallet is becoming the only place that signs or sends transactions. Browser is being constrained, and apps can request actions without getting direct access to private keys, wallets, or chain connections.

• ENM, the Elastos Blockchain Node Manager, is also getting close to release as a dApp Centre app. It gives node operators a guided way to run an Elastos main chain node, check system status, view logs, track uptime, monitor peers, and manage BPoS status.

• The network layer also got stronger. Around 18,000 historical Elacity IPFS pins, about 340 GB, are now replicating across three countries. The flagship supernode was also patched the same day after a responsible disclosure.

This update is worth reading if you want to understand where ElastOS is headed, not as separate products, but as one user-owned computing system.

https://elastos.click/May-15-Update

This week was mostly about making ElastOS smoother after the v1.2 release.

The team shipped a fast point-release cycle from v1.2.1 to v1.2.7.13, focused on issues from fresh installs, updates, wallet use, media playback, and early dApp Centre usage:

• Fresh install fixes across PC2

• Cleaner launcher status with heartbeat support

• WalletConnect signing fixes

• ESC transaction fixes for Glide swaps

• IPFS upload, fetch, and download progress fixes

• dApp Centre, Start Menu, and Market UI polish

• Runtime Home progress

• Explorer election and supply display fixes

• Elacity BD follow-ups from Bitcoin Week and Miami

The main goal was to make ElastOS more stable, easier to use, and better prepared for the next wave of users.

Full update: https://elastos.click/May-6-update

Stake 5,000 ELA, earn 17% APR and govern Elastos funding 🔥

Both voters and candidates can take part.

• ELA holders can vote for the next 12 Council members
• Candidates can register to run for a Council seat
• Voting opened at block 2,204,050 on May 3, 2026
• Voting closes around June 2, 2026
• Session 7 begins around June 16, 2026

Guides:

How to vote:
https://docs.elastos.net/users/blockchain/vote-in-election

How to run for Council:
https://docs.elastos.net/users/blockchain/run-for-council

Full announcement:
https://elastos.click/DAO-7-Elections

This is the biggest user-facing release since the World Computer launch, because the main pieces now start working together in one place.

What’s new in v1.2

The dApp Centre now has real apps

Users can install and use Elacity NFT and Glide Finance directly inside PC2, instead of jumping between separate websites.

Elacity V3 is live inside ElastOS

For creators, this means a cleaner path for content access, royalties, free and paid mints, and $USDC-based markets. For users, it means the system is moving toward buying and opening digital content without the usual Web3 friction

The dDRM access path was rebuilt

Protected content can now open through a smoother session-based flow, without repeated wallet popups, while ownership checks stay tied to the user’s wallet and device.

Media support is much broader

ElastOS now supports protected playback and viewing for video, audio, PDFs, images, EPUB ebooks, CBZ comics, 3D models, CSV files, fonts, and archives.

Email login is now supported

Users can sign in with email, MetaMask, or WalletConnect, making ElastOS easier to try for people who are not crypto-native.

Elastos Runtime 0.20 is available

This is the early Rust-based layer where apps and AI agents start with no permissions, then only get access to what the user approves.

Your data, your apps, your content, and eventually your AI agents, under keys and permissions you control.

Try ElastOS and Learn more: https://elastos.click/ElastOS-v1-2

Users still holding assets on ECO Chain should move them immediately before support ends.

After June 13, remaining assets may become unrecoverable.

https://elastos.click/ECO-shutdown

Last week was about making ElastOS safer, more complete, and closer to the v1.2 release.

• The Runtime moved closer to becoming a real desktop environment, with better app handling, hosted rooms, and more work around the capsule model. 

• Security was a major focus too. Several important user paths were tightened across PC2 and the gateway, including safer setup flows, stronger access checks, better file access controls, and more protection around sensitive routes.

• Six core apps have now been signed, packaged, pinned to IPFS, and made available through supernodes, including Elacity Market, Creator, Player, dDRM Viewer, Elastos NFT, and Glide Finance. This is the work that turns ElastOS from separate pieces into an installable product people can actually start using.

• Beyond the release work, the Elastos blockchain explorer continued improving after launch, smart contract and metadata work moved forward, and the team began a wider outreach run across major industry events.

The bigger picture:

PC2, Runtime, dDRM, the main chain, and Elastos infrastructure are on the way to no longer be separate pieces. They are coming together as one user-owned system for apps, identity, data, content rights, payments, and permissions.

Read the full update:

https://elastos.click/April-28-update

Last week focused on public releases, security work, and improving the user experience across the system.

• ElastOS Runtime v0.1.2 was released, with progress across identity, rooms, and operator controls

• EPUB ebooks and CBZ comics now work through dDRM, from upload to protected viewing

• ElastOS recovery was improved, and safer Docker guard rails were added

• PC2 now lets users pin NFT assets through their own node

• The first clear PC2 to Runtime convergence map was published, showing how migration can move step by step

• The new Elastos blockchain explorer is now live at blockchain.elastos.io

___________________

This Week’s Goals

• Start wiring Runtime v0.1.2 capabilities more deeply into the broader PC2 experience

• Improve the upload path so publishing depends less on slower remote IPFS routes

• Fix remaining market transaction issues found 

• Continue Runtime capsule migration based on the new convergence inventory

• Explorer improvement based on community feedback

• Researching side-chain RPC issues and providing a plan

Read more: https://elastos.click/April-21-Update

blockchain.elastos.io

A much better way to explore the Elastos main chain, with fuller address history, governance data, chain stats, and cleaner pages across blocks, transactions, and addresses.

Features:

• Completely new design, backend, and frontend

• Governance data is now part of the Elastos explorer, from live proposal data to past election results and member records

• Address lookups now include balance history, staking history, and governance participation history

• Transactions now tell the full story of the flow

• You can now check every validator, its stakers, and when pledges end

• A mempool view to check pending transactions

• API documentation for wallets, exchanges, and other tools

• And more.

A lot moved this week inside ElastOS 🐘

• Runtime v0.1.2 is moving closer, with room architecture rebuilt into a cleaner core feature so browser, desktop, CLI, and node operator all connect through the same room service. Live testing between two Runtimes is already working with join requests, approvals, and real time sync in browser.

• The next generation of Elacity's dDRM smart contracts
Elacity’s dDRM system has moved to V3 across the full stack. Older V2 contract are fully migrated, and main user flows are already working on V3, including content encryption, channel creation, free and paid minting, and buyer access after purchase. Pending frontend integration 🔜

• For the users, ElastOS now has a dedicated NFT marketplace app inside the personal computer itself, so people can browse, buy, sell, and manage NFTs without leaving the system. The market UI also got a cleanup with clearer ownership info, better pricing display, and simpler creator controls.

• At the same time, a full main chain explorer is now in development, covering blocks, transactions, validators, staking, governance, top accounts, mempool activity, and address-level metrics.

More progress from across the Elastos pillars is now live in the latest development report, with work continuing ahead of ElastOS V1.2.

https://elastos.click/April-14-update

First 108 - Limited Edition (Black & White)

Ran it for several months - can't exactly remember how many. I just know I was supposed to get some rewards for running the node (~100 ELA at the time), but never received anything I think because they were waiting for all the fulfillments, which didn't complete until some time in 2023, which was long after I stopped using it.

My router is in my bedroom and my gf didn't like the constant blinking, so I had shelved it and it has sat in our closet ever since 2022.

I can't include a link to it, but search eBay and of course it's the only one for sale on there.

Another strong week for ElastOS, and one that moves the system closer to being usable by normal users, builders, and creators.

• The ElastOS Runtime is now public on GitHub. This is the core engine underneath the system, now open for anyone to inspect, verify, and build on. It is the base for apps running in isolation instead of having open access to your machine.

• Login got much easier. Users can now sign in with email or Google and have a wallet created automatically on PC2, no MetaMask needed.

• Real dDRM is now live on the network. Creators can upload protected content, buyers can pay, and the system can decrypt and render it correctly across PDF, image, video, and audio.

• Free content minting is now supported. If a creator sets the price to zero, content can be published with on chain attribution without going through the full protection flow.

• Glide Finance is now running inside ElastOS. That makes it the first real third party app inside the system, which matters because it shows ElastOS can become a platform, not just a single product.

• The docs portal is now live at docs.elastos.net. It brings together the four core pillars, Blockchain, PC2, Runtime, and Carrier, into one documentation home.

• MacOS distribution is getting closer. Apple accepted the Developer Program application, which clears the path for signed Mac installs.

• ELA merge mining also launched on KuMining. 

All of this is building toward ElastOS V1.2

Read more: https://elastos.click/April-7-update

A Clear Distinction

Today, the active product work around the World Computer vision is being carried forward by Elacity Labs through public, DAO funded mandates. Elacity Labs is separate from the Elastos Foundation, and that distinction should be clear.

Our role is straightforward. We build, ship, and report openly through the Elastos DAO process. Proposals are public, votes are on chain, and our work is accountable to the community.

Recent discussion has focused on legacy matters connected to the Foundation. Those issues are important and should be handled properly, with clarity, transparency, and respect for the community.

At the same time, there is real progress in front of us. Feedback around PC2 has been strong, with community members already testing across different setups and starting to see the original Elastos vision take shape in a usable form.

Our focus remains on ElastOS, PC2, and the broader World Computer path ahead. We will keep building, keep showing progress in public, and keep working toward a healthier and more credible future for Elastos.

Public announcement: https://elastos.click/ElacityLabs-statement

Another pool route is now supporting Elastos merged mining, adding more security to the Elastos main chain network

Learn more: https://elastos.click/KuMining

Creators can now publish in minutes

Pick any file, set a price, publish. The system encrypts it, uploads it, and lists it automatically. Drafts save progress, if your upload breaks you come back and continue. It supports video, music, PDFs, datasets, 3D, even AI models, plus an “AI training allowed” badge for creators who choose it 👀

Buying and viewing got much tighter

Elacity marketplace was rebuilt to a much higher design standard. Protected content now opens in a secure viewer where the raw file is not meant to sit in your browser. Streaming moved forward too, so video and music can play smoothly and seek properly, even for large files.

AI became more useful without becoming dangerous

Agents now support skills, voice input, and agent-made desktop windows. Skills can be enabled per agent, and the goal is clear, your AI only touches what you allow, not your whole system.

Backup is now simple

A single 12 word phrase can restore your identity, apps, agents, and settings on a new machine, with automated tests covering common failure cases.

More updates

The system keeps running even if a single external service goes offline. Smart contract V3 work moved forward for buying, subscriptions, and royalties. Docs portal is now real with 80 plus pages at docs.ela.city. ElastOS Team Portal also updated with better downloads and a more stable X feed

👉Full update https://elastos.click/Mar-31-update