Nesa

The World's AI Blockchain

[Nesa @nesaorg]

The counter to centralized AI. Built by a team of award-winning researchers, now powering the largest companies on earth. This is Nesa.

[Nesa @nesaorg]

32% of AI users say they have told a chatbot something they kept from close friends, parents or doctors.

In the same DuckDuckGo survey of 1,944 US adults, only 25% knew that AI chats can be subpoenaed.

People use chatbots as confidants. Most major chatbots train on conversations by default and tie them to an account.

What you ask an AI is some of the most sensitive data you produce, and today it sits readable on someone else's servers.

Encrypting the query and the output at the point of inference means the provider never holds the readable version.

That's exactly what we are building here.

[Nesa @nesaorg]

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.

[Nesa @nesaorg]

Over the next two years this will be one of the biggest topics for the industry. Build with Nesa.

[Stefan @stefanluke_]

Demis Hassabis is warning about the next wave of AI-driven cyberattacks.

The industry is spending billions making models more capable while security architecture continues to play catch-up.

Nesa’s technology ensures that secure computation can advance alongside model intelligence, not years after it.

[Nesa @nesaorg]

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.

[Nesa @nesaorg]

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.

[Nesa @nesaorg]

The official NES migration portal is now live for eligible on-chain holders. See the article on the official Nesa website below:

https://t.co/ODANctPFft

Please use only links shared through official Nesa channels.

[Nesa @nesaorg]

📍 The TypeScript SDK on GitHub (nesaorg/ai-sdk-ts).

It manages AI sessions and sends inference requests to over 100,000 models

In the browser or in Node.

Install it with npm @nesaorg/ai-sdk.

[Nesa @nesaorg]

Where you start building on Nesa depends on what you already have:

1. No model chosen yet?
→ Use the Playground on our website

2. Your own model?
→ Use custom model upload

3. An app that uses the ChatGPT format?
→ Use the ChatGPT-compatible API

4. A TypeScript project?
→ Use the SDK

Learn more below 👇

[Nesa @nesaorg]

📍 The ChatGPT-compatible API.

If your app already uses the ChatGPT format, moving it to Nesa is a one-line change.

The query and output stay unseen on every request.

[Nesa @nesaorg]

Where you start building on Nesa depends on what you already have:

1. No model chosen yet?
→ Use the Playground on our website

2. Your own model?
→ Use custom model upload

3. An app that uses the ChatGPT format?
→ Use the ChatGPT-compatible API

4. A TypeScript project?
→ Use the SDK

Learn more below 👇

---

2/
📍 The Playground

Browse the on-chain model catalog by modality and task, compare each model's latency and usage, and try models before you commit to one.

The catalog spans text, image, video, audio, 3D, bio and multi-modal models.

3/
📍 Custom model upload

Register your own model through the Build on Nesa flow with a Docker image or GitHub repo

Plus its metadata and visibility settings, and it runs on the network.

Maintaining more models requires Nesa Pro, with up to 5 active custom models.

4/
📍 The ChatGPT-compatible API.

If your app already uses the ChatGPT format, moving it to Nesa is a one-line change.

The query and output stay unseen on every request.

5/
📍 The TypeScript SDK on GitHub (nesaorg/ai-sdk-ts).

It manages AI sessions and sends inference requests to over 100,000 models

In the browser or in Node.

Install it with npm install @nesaorg/ai-sdk.

[Nesa @nesaorg]

An AI chain should not ask every node to do the same job

Agreeing on transactions is one kind of work, but running a model is another, and it asks for more computing power.

Nesa gives each its own node type:

⬟ Validators handle consensus
⬟ Miners handle inference

You pick one when you set up with the official bootstrap script.

[Nesa @nesaorg]

53% of organizations still don't encrypt sensitive data at rest and in motion.

That's from IBM's 2026 Cost of a Data Breach report.

If you're a developer shipping an AI model on patient records or financial data right now, what's your plan for the other 47%?

[Nesa @nesaorg]

Now more than ever before, the world needs private AI.

It's time for a new standard of artificial intelligence.

[Nesa @nesaorg]

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!

[Nesa @nesaorg]

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 @nesaorg]

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.

[Nesa @nesaorg]

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.

[Nesa @nesaorg]

OKX opens ETH Chain for NES
https://t.co/QJHz3mDC69