Skip to main content

The Onchain Economy Needs Intelligent Defense | NEAR

The Onchain Economy Needs Intelligent Defense | NEAR

November 19, 2026

In the past several months, two of crypto’s largest exchanges were compromised: Bitget for roughly $388 million in September, then Binance for roughly $6 billion on October 29. Stablecoin issuers froze about half of the affected Binance flows within days, and the rest moved across chains to the venues that didn’t stop it.

Crypto has a choice. It can keep absorbing hacks that drain capital and activity from the industry, or it can build decentralized systems secure enough for the global economy to move onchain.

So far, the industry’s response has come down to two blunt tools. One approach is to do nothing, because the system is permissionless. The other is to press pause. Both of these approaches fail users. Doing nothing lets stolen funds settle alongside everyone else’s. Pausing stops everyone to catch a few.

NEAR built SHIELD to give the industry a better option: intelligent, layered defense that acts on the specific flow at risk, while ensuring that the underlying NEAR Protocol stays permissionless.

After the Bitget hack in September, SHIELD detected and blocked 99.7% (over $50M) of the attempted laundering flows. Within two days of the Binance exploit, the attackers had moved roughly $194M of TRON across chains through bridges and swap venues, with only $171k going through NEAR Intents, according to independent onchain tracing. As of November 3, SHIELD had blocked approximately 96% of Binance exploit-linked flows that reached NEAR Intents. NEAR Intents turns these flows away because an onchain economy that settles stolen funds is an economy the rest of the world won’t join.

Below is a deep dive that answers the questions we hear most about how NEAR Intents operates under the hood: how NEAR keeps the base layer protocol permissionless, when and how SHIELD flags transactions, and how other teams can build on this shared security infrastructure.

A Permissionless Base, With Layered Defense

Two kinds of defense, two layers

Security in an onchain economy does two jobs. Protocol security protects the system. Transaction policy protects users and markets. When the two get mixed together, you end up with the blunt tools described above.

NEAR Protocol handles the first job through post-quantum security work, consensus security, and network monitoring. Anyone can hold and transfer assets, deploy contracts, or become a validator on NEAR Protocol. No single party can pause the chain. Protocol security protects the network, and it never decides whose transactions get processed.

Policy lives in applications

Transaction policy sits one layer up. NEAR Intents is an application built on NEAR Protocol and designed for open participation. SHIELD is its financial integrity layer.

SHIELD applies to flows through NEAR Intents, not to balances on NEAR Protocol. If you hold NEAR and never route through NEAR Intents, SHIELD never screens your funds.

Inside SHIELD: Proactive, Scoped, Explainable
Inside Shield - Near

Screening at entry, before execution

SHIELD screens the funds in a request by their public onchain history on the chain they came from. It screens transactions, not identities, so no KYC is needed to use NEAR Intents.

SHIELD acts on flows linked to hacks and other illicit activity identified by signals that come from an internal AML database, third-party intelligence providers, as listed in the NEAR Intents risk and compliance docs, and trusted industry partners acting as authorized producers for SHIELD. Checks run before funds reach the confidential layer, and if a request is flagged, the transaction is not executed. Once funds are inside NEAR Intents, trade details stay confidential for every participant.

While SHIELD does not fully eliminate the flow of stolen funds, it significantly helps reduce NEAR Intents’ exposure to stolen funds and the risk of legitimate users’ funds settling alongside flows linked to known hacks.

Architecture: a policy service, not a kill switch

SHIELD is a dedicated incident and policy service. Authorized producers submit incidents, and integrated services query SHIELD before they continue executing. Decisions are scoped and made at request time, so the platform slows down only where it needs to instead of shutting down everywhere.

Three security modes, kept simple on purpose

  • Normal: no added friction.

  • Paranoid: delay windows and more scrutiny while a situation is assessed.

  • Under Attack: pauses only the affected functionality.

Three modes is deliberate. Under pressure, operators need clear posture changes, not fine-grained states.

Who can act, and how it’s checked

Each producer gets an explicit permission set, whether it’s a partner, an on-call operator, or internal anomaly detection. Authority is never inherited. Depending on its permissions, a producer can pause a single destination, flag an observation for review, raise the security mode, or only read status. Scope can be set by chain, bridge, token, address, or mode.

Actions are auditable in both directions: partners see their own history, and operators can review everyone’s.

AI-driven decision-making

A rule-based anomaly engine scores quotes against configured thresholds. Because it runs on rules rather than a model, its anomaly scores can be traced to the configured rules. Policy is designed to target a specific transaction, account, or flow while the rest of the system keeps running. Chain-health adapters, which are also in place, help translate each chain’s failure modes (stalled finality, reorgs, hashrate drops) into one shared model.

SHIELD Is Shared Security Infrastructure for the Cross-Chain Economy

Attackers move across chains, so defense has to as well

Stolen funds go to whichever venue doesn’t screen them. When one venue screens on its own, the risk moves somewhere else. When venues screen together, the places that an attacker can flee through can get smaller. While traditional card networks and internet security providers already share threat signals, the onchain economy has had no common layer for automated threat detection.

SHIELD is designed to serve as that layer, open to wallets, bridges, exchanges, solvers, and protocols. Any integrator that uses NEAR Intents benefits from SHIELD’s security system and the robust screening it applies to all transaction flows through NEAR Intents. Major chains, exchanges, and security firms are also now joining SHIELD to provide top-tier data sources to SHIELD’s detection system.

What partners get

  • A live status feed of incidents and degraded conditions across connected chains.

  • Scoped controls. A partner can pause the one chain or destination it cares about without escalating the whole platform.

  • An audit trail of its own actions.

What partners contribute

  • Incident submissions through an authenticated, scope-checked API.

  • Observations flagged for review, without forcing a change in security mode.

  • Chain-specific knowledge that improves the signals for everyone.

Build it with us

Intelligent Defense Is How the Onchain Economy Scales

NEAR’s technology is built to expand human agency and opportunity. Privacy is a right and a precondition for a user-owned world, but privacy that shelters crime undermines the system it’s meant to protect. As NEAR Co-founder Illia Polosukhin puts it, decentralization doesn’t mean disorganization. SHIELD aims to catch criminal and anomalous activity before funds enter NEAR Intents, whilst supporting confidential execution.

AI may make exploits faster and easier to run. It can also make defense faster, but only if defenders coordinate. Attackers already coordinate across chains, and the industry needs to do the same, now.

Join the community: