How NEAR Chain Signatures Turn Accounts Into Cross-Chain Signers

NEAR Intents define what should happen; Chain Signatures provide the cryptographic mechanism to authorize and execute outcomes across multiple blockchains. This requires execution to be understood at the cryptographic layer rather than solely at the smart contract layer.

Chain Signatures are built on a decentralized Multi-Party Computation (MPC) system and threshold cryptography, allowing NEAR accounts to produce valid signatures for external chains such as Bitcoin, Ethereum, and Solana.^[1]

1. Cryptographic Foundation

The system operates under a threshold cryptography model in which no single participant can independently produce a valid external-chain signature. Signing authority is distributed across a decentralized MPC network using Threshold Signature Schemes (TSS) and Distributed Key Generation (DKG). Key material is generated collaboratively and represented as cryptographic shares distributed across independent nodes, ensuring that no participant ever holds a complete private key.^[1][2]

Each node operates on an isolated share of the signing process. A threshold subset of participants is required to generate a valid signature through locally computed partial signature components, which are then aggregated into a standard ECDSA or Ed25519 signature depending on the target chain. External chains validate only the final signature output. The coordination process that produced the signature is not visible at the protocol level of the destination chain.

2. Cross-Chain Account Model

Scaling this model requires separating user identity from private-key custody. NEAR Chain Signatures achieve this by mapping a NEAR account and signing context to an external-chain execution target, without introducing wrapped assets or synthetic representations. Instead, a NEAR-controlled signing context authorizes native transactions on external networks.^[1]

A deterministic mapping defined by chain_id, NEAR_account_id, and derivation_path establishes the external signing context. This allows a NEAR account to consistently reference execution targets on external chains without requiring users to manage separate private keys for each network. The system functions as a coordination layer over signing authority rather than a traditional key custody model.

3. From Signing Request to External Transaction

Figure 1 summarizes the basic execution path.

USER / SMART CONTRACT (NEAR)
        |
        v
+------------------------+
|  NEAR CONTRACT LAYER   |
|  - signing request     |
|  - authorization logic |
+------------------------+
        |
        v
+------------------------+
|   MPC SIGNING LAYER    |
|  - distributed shares  |
|  - threshold signing   |
|  - partial signatures  |
|  - t-of-n coordination |
+------------------------+
        |
        v
+------------------------+
|   RELAYER LAYER        |
|  - attach signature    |
|  - broadcast tx        |
+------------------------+
        |
        v
BTC / ETH / SOL / others

A signing request can originate from a user or a smart contract on NEAR. The request contains an unsigned transaction payload for an external chain and a specified signing context. The MPC network observes the request, validates it under the relevant protocol rules, and performs threshold signing over the payload. Once the signature is produced, the external chain remains unaware of the NEAR-side coordination process.^[1]

A relayer or application layer can then attach the finalized signature to the transaction payload and submit it to the target chain. The important separation is that signature generation is not the same as transaction propagation. NEAR coordinates the signing process. The external chain processes the signed transaction according to its own rules.

4. Security Model

Security comes from the interaction of cryptographic threshold assumptions, network coordination, and economic constraints. At the cryptographic layer, the system assumes a threshold adversary model. As long as an attacker cannot control the threshold required to produce a signature, no valid unauthorized signature should be generated. No single participant should be able to reconstruct complete signing authority.^[2]

At the coordination layer, signing requests must be bound to explicit payloads and signing contexts. This prevents a valid threshold signing system from becoming an open-ended permission surface.

At the economic layer, the security model depends on the incentives and accountability of the participants running the signing service. Staking, validator incentives, governance, and operational security matter because MPC is not merely cryptography in the abstract. It is cryptography operated by real network participants.

Economic constraints do not replace cryptographic correctness. They make sustained adversarial coordination more expensive and harder to maintain.

5. What Chain Signatures Change

Chain Signatures implement a distributed signing primitive that enables NEAR to coordinate execution across external blockchains without custody, wrapped assets, or centralized bridge operators.

NEAR does not operate as the execution environment for external chains. Instead, it functions as a coordination layer that enables accounts and applications to produce valid external-chain signatures. Chain Signatures extend NEAR beyond a single-chain execution model by abstracting cross-chain execution into a distributed signing problem.

References

1. NEAR Documentation, "Chain Signatures," accessed June 2026. https://docs.near.org/chain-abstraction/chain-signatures
2. National Institute of Standards and Technology, "Threshold Cryptography Project," accessed June 2026. https://csrc.nist.gov/projects/threshold-cryptography