Every onchain app that adds AI has a gap in the middle of it. A contract's logic is public. A wallet's balance is public. But the model call? That's a request to a server the chain cannot see. Nothing proves: ⬟ Which model answered ⬟ Who read the data ⬟ What happened during inference And this matters more as AI starts taking real actions. Agents that move user funds, models that score risk, and assistants that act for users all depend on that call. The most consequential decision in the app runs outside the guarantees of the chain it lives on 👀 Closing that gap takes a Layer-1 where inference is settled and verified onchain, with the data encrypted while the model runs. It is what we are building at Nesa.

Privacy usually costs speed, which is the usual reason it gets skipped. Fully homomorphic encryption keeps data hidden during computation, at a heavy performance cost. Our Equivariant Encryption paper takes another route. 📍 Inputs, outputs and intermediate activations stay unreadable to the server running the model, and the paper reports near-zero extra latency compared with unencrypted inference. The paper also includes a threat analysis that lays out the attack vectors, so anyone can test the claims.

Nvidia agreed on September 3 to acquire Hugging Face, one of the most widely used hubs for open models. Nvidia says the aim is to protect open-source AI developers. The dominant GPU vendor will now also own one of the main places open models are published. For the person using those models, little changes. With every inference-as-a-service player today, you still cannot check the proof for: → Which model answered a request → Who could read your prompt → What happens to your data You trust whoever sits in the middle. Open models only stay open if anyone can verify how they run, whoever owns the hub. That takes an execution layer with no owner, where the network checks which model ran and keeps the data private.

NES trading across exchanges will resume on Thursday, September 10 with exact time to be announced soon. From that time forward, reference the revised canonical NES Token CAs below: Ethereum: 0x863F08A3d3B14fbD3D42fFD061D0e290F7dBC538 BNB Smart Chain: 0x097acf27503753e77bCA940277806156C5925B81 Base: 0x2E968fB88998a6303535Ac637C809119ECAd4a4b Arbitrum: 0x8cAd676141FeadB6aCA5eF661E835d5957644033 HyperEVM: 0xdFC12a5cF04Bc91BE4aF0E3Bc46A3CDADB1f86Af Solana: EFuxu8VZJJvWZohJgjsbgXvRifySusuMv7FmSEvzDRoz For on-chain token holders, a NES migration portal will guide you through claiming your token. Note the below snapshot block heights: Ethereum: 25822581 BNB Smart Chain: 117742359 Base: 50377812 Arbitrum: 497772766 HyperEVM: 44010284 Solana: 441313281 Stay tuned as further details and announcements are finalized!

Deployment and migration of the revised NES token CA across exchanges is underway. Upon integration completion, you may refer to the following canonical NES CAs: ETH: 0x863F08A3d3B14fbD3D42fFD061D0e290F7dBC538 BSC: 0x097acf27503753e77bCA940277806156C5925B81 Stay tuned for important news and updates and for our official announcement of migration completion.

Nesa is actively coordinating with all exchanges to reopen deposits, withdrawals and trading this week. Please look out for our announcement on exact day and time shortly. Thanks to swift action from our exchange partners in closing deposit channels, estimated impact of the recent incident was limited in size. Regarding the incident, Nesa Chain was vulnerable to a widely used attack vector and became the target of a malicious actor. On August 24, this actor performed a pre-meditated set of operations against the chain that led to the misappropriation of NES token. Since then, the chain has been fully patched with direct support from the official upstream code maintainers. Nesa maintains a proactive approach to security via a private channel to upstream security fixes and will continue to implement additional safety measures moving forward. Further, Nesa shares a direct communication channel with the official upstream code maintainer team. We sincerely thank our holders and community for their patience and support throughout the emergency response. Upon full completion of this remediation process, Nesa is fully committed to supporting affected holders. The network is moving forward stronger and better protected. Stay tuned for positive news and important announcements to follow.

We have identified malicious behavior on our L1 exploiting a Cosmos EVM vulnerability and are underway into stemming impact. We have taken swift action and will be bringing services online after applying a software fix and further remedies to ensure safe operation. All exchanges have been notified and deposits will resume upon completion.

🦾

What area of AI are you most bullish on right now? Let us know 👇

Gm Now your turn 🫵