Elacity joined NVIDIA Inception in July, while ElastOS added a new way for AI agents to spend and act without receiving control of a user’s wallet keys.
The same two-week period brought new work across Runtime, Elastos Essentials, the proposed ELA bridge to Base, infrastructure, and Hyper.
Elacity joins NVIDIA Inception
Elacity was accepted into NVIDIA Inception following conversations at the AI Agent World’s Fair in San Francisco.
Inception is NVIDIA’s startup program, not a commercial partnership. It gives members access to technical training, hardware and cloud programs, SDKs, early product programs, and NVIDIA events.
For Elacity, the main connection is local AI hardware.
ElastOS already runs on NVIDIA Jetson Orin, where AI models can use the device’s own GPU without sending conversations outside the home. DGX Spark is the next target. Its 128 GB of unified memory would allow larger models to run on user-owned hardware.
The team is also evaluating TensorRT-LLM and NVIDIA NIM for the local AI stack.
AI agents get limits instead of wallet keys
ElastOS now supports mandates for AI agents.
A mandate defines what an agent may do, how much it may spend, and how long the permission remains active. The user can revoke it at any time, while the wallet’s private key stays inside Runtime.
The Mandates app lets the user create permissions, review actions, monitor spending, and stop the agent when needed.
Spending limits remain in place across restarts. Uncertain transactions are recorded instead of being forgotten. If a payment leaves the device but no acknowledgement returns, the Money panel marks it for later review.
Agents can also request quotes, negotiate prices, and complete purchases through marketplace and stablecoin checkout paths.
Each action creates a signed receipt that can be verified outside ElastOS. An operator, auditor, or counterparty can inspect what happened without contacting the Runtime that produced it.
The agent receives permission to act, not control of the keys.
Runtime and PC2
The Runtime marketplace now covers more of the purchase flow. An on-chain content identity resolves to a listing, purchase rules reject unsafe defaults, and Library can buy and pin the purchased asset through the normal capsule path.
A security pass fixed six Runtime issues, including unauthenticated Carrier access, denial-of-service limits, request-forgery protections, redirect handling, signature downgrade attempts, and response character-set validation.
Home can now run with either a graphical interface or a command-line shell. Both use the same Runtime permissions and app data.
Elastos Node Manager is now live in the PC2 dApp Centre.
Elastos Essentials rebuild
Elastos Essentials is going through its largest single-app development cycle of the year.
The current build introduces a new visual system, shared components, corrected fonts and icons, and an All Chains view that combines balances from supported networks.
Receive now asks the user to choose the network first, since the network determines the address.
Known third-party vulnerabilities fell from about 184 to 109. WalletConnect v1 was removed, while WalletConnect v2 remains supported.
An unused account-abstraction subsystem was also deleted, removing roughly 51,000 lines. Hardcoded service keys moved out of tracked source files, and signing sheets now show the requesting site and whether the session is verified.
Testing covered more than 180 screens across real devices. Fixes included withdrawal decimal handling, scanned-address validation, safer signing defaults, and full keystore import for the Elastos main chain, Bitcoin, and Tron.
The rebuild is not finished. Several hundred prioritised items remain.
ELA to Base feasibility study
A technical study found no major blocker to bridging native ELA from the Elastos main chain to Base.
The bridge is not built yet, but the main technical risks now have defined solutions.
A light client would verify Base data, while withdrawals would be confirmed against Base’s finalised state on Ethereum before Council nodes approve them.
The Elastos main chain already publishes the Council keys needed when membership rotates. The bridge can reuse the Arbiter’s existing withdrawal engine, with a new Base driver and supporting wiring.
Fifty-eight of sixty contract tests currently pass. The finality verifier has already confirmed a real Base mainnet transaction on a Base fork.
The largest remaining item is automatic Council rotation. It must still be built and tested against a real Elastos rotation transaction.
Infrastructure costs fall again
Elastos public RPC services have moved from managed cloud infrastructure to bare-metal servers in two regions.
Retiring ECO services and moving RPCs away from AWS reduced the monthly bill. June AWS costs were $4,503, while July is projected at $2,789.
Including the new bare-metal servers, total monthly infrastructure costs are expected to be around $3,181.
That is $1,840 below May and roughly 73 percent below the approximately $12,000 monthly cost before the current infrastructure changes began.
Restoring the Elastos main-chain testnet is the final large server item. Remaining Essentials services can then move away from AWS.
Hyper App improves phone reliability
Hyper received an Android power and reliability audit.
Background reconnect attempts now slow down over time, offline-peer retries back off, and refresh polling pauses when the app enters the background. Call audio and stability also improved.
Following and chatting are now separate permissions. Following someone does not automatically allow private chat, and both sides must agree before a conversation opens.
Deleting a chat revokes its capability, while blocking deliberately cuts the relationship.
The invitation links were also repacked, reducing shared QR-code size by about one-third. A live social feed shipped with avatars, collapsible comments, and live refresh.
What comes next
Runtime will test an end-to-end marketplace purchase through the audit ledger.
The ELA-to-Base work will focus on the Council-rotation entry-point. The multi-shell system and new component interface still need to reach the public Runtime repository.
Elastos Essentials will continue working through its security and product list.
AI agents can now operate under spending limits without holding wallet keys. Essentials has a stronger security base, infrastructure costs are lower, and the Base bridge now has a tested technical path.
