chain-signatures-primary-sources-2026-05-13

Chain Signatures primary-source snapshot

Fetched: 2026-05-13 UTC

1) Official NEAR docs overview

Source: https://docs.near.org/chain-abstraction/chain-signatures

Selected excerpts from the official docs:

Chain signatures enable NEAR accounts, including smart contracts, to sign and execute transactions across many blockchain protocols.

Keep in mind that Chain Signatures is a “one way” solution to sign and execute outbound transactions happening on other blockchains.

Controlling accounts and their assets on other blockchain platforms is made possible thanks to the interaction between three elements: Derivation Paths, Multichain Smart Contract, Multiparty Computation Service.

Additional signals from the docs:

• The official docs are unusually clear that Chain Signatures is an outbound signing primitive rather than a full cross-chain state-access system
• The main decomposition is explicit: derivation paths, signer contract, and MPC service are separate layers
• This makes Chain Signatures more useful as an account-control comparison point than as a generic bridge label

2) Official implementation docs

Source: https://docs.near.org/chain-abstraction/chain-signatures/implementation

Selected excerpts/signals from the implementation docs:

There are five steps to create a Chain Signature: deriving the foreign address, creating a transaction, requesting a signature, formatting the signature, and relaying the signed transaction.

There is an MPC contract available on both mainnet and testnet.

The MPC network is made up of 8 nodes.

Additional signals from the implementation docs:

• The transaction lifecycle is deliberately decomposed into address derivation, payload construction, signing, formatting, and relay rather than bundled into one opaque SDK call
• The docs show Chain Signatures as a cross-chain signing substrate with chain adapters for multiple ecosystems rather than only an EVM feature
• Relay remains a distinct downstream step, which is analytically important because broadcasting power can centralize separately from signing power

3) near/mpc repository README

Source: https://raw.githubusercontent.com/near/mpc/main/README.md

Selected excerpts from the repo:

This repository contains the code for the NEAR MPC node that powers Chain Signatures.

Each request is hashed and mapped to a specific node in the MPC network — the leader for that request. The leader initiates the signing process and submits the final signature back to the smart contract. If the leader is offline, a secondary leader can take over.

The node supports multiple threshold signature schemes, organized into domains.

Additional signals from the repo:

• The public implementation makes the operational control plane much clearer than the docs alone: leader selection, fallback, domain separation, and contract-watching are core parts of the system
• The repo documents both Secp256k1 and Ed25519 threshold-signing paths, reinforcing that Chain Signatures is meant as a multi-ecosystem signer substrate rather than a single-chain extension
• The same repo also documents adjacent capabilities like confidential key derivation and foreign-chain transaction verification, suggesting the signer network is evolving toward a broader execution-and-verification control plane

4) Chain gateway design notes

Source: https://raw.githubusercontent.com/near/mpc/main/docs/chain-gateway-design.md

Selected excerpts/signals from the design doc:

The MPC node relies heavily on the NEAR blockchain for coordination.

pending signature and CKD requests … TEE related information, such as the current docker image hashes of launcher and node

The Chain Gateway … subscribe to view methods of contracts, forward transactions to the NEAR blockchain, [and] monitor non-finalized blocks for transactions matching a user-specified pattern.

Additional signals from the design doc:

• This material is valuable because it surfaces hidden control surfaces: contract-state watches, TEE image allowlists, migration handling, and block-stream filtering
• The signer network is not just a black-box threshold cryptography service; it is a contract-coordinated operational system with software-policy and observability layers
• That helps separate cryptographic decentralization from operational and software-deployment centralization

5) Historical chainsig-lib repo

Source: https://raw.githubusercontent.com/near/chainsig-lib/master/README.md

Selected excerpts from the historical library docs:

NEAR’s Chain Signatures protocol allows any NEAR account to sign transactions for any chain.

The signing step is a method call … This is executed by a NEAR smart contract that returns the signature to the client.

The client then combined this signature with their transaction payload and broadcasts it to the network of their choice.

Additional signals from the historical library docs:

• Even though the repo is marked deprecated, it preserves the lower-layer transaction model very clearly
• It shows the split between signing and broadcasting that later UX layers can flatten away
• It also hints at API churn and rapid surface-area evolution, which matters when judging whether the stable control plane is really the SDK, the contract, or the signer network itself

6) Multichain gas-station contract

Source: https://raw.githubusercontent.com/near/multichain-gas-station-contract/master/README.md

Selected excerpts from the repo:

This smart contract accepts payments in NEAR tokens in exchange for gas funding on non-NEAR foreign chains.

[It] facilitates the signing, gas funding, and relaying of the signed transactions to their destination chains.

The multichain relayer server will be monitoring this gas station contract and relaying the signed transactions in the proper order as they become available.

Additional signals from the repo:

• The gas-station materials expose another important layer beyond Chain Signatures itself: paymaster funding and ordered relay
• This is useful for the corpus because many cross-chain account systems really depend on signer plus paymaster plus relay coordination rather than one uniform trust surface
• The docs also show how deterministic path-based signing can be embedded in transferable key or approval systems instead of being fixed to one wallet model

Notes

• Chain Signatures is best understood as multichain signer middleware and a chain-abstraction primitive, not as a full bridge or generic wallet.
• The key reusable split is between deterministic foreign-address derivation, NEAR-side authorization, threshold signing, optional paymaster funding, and destination-chain relay.
• The strongest primary materials in this pass were the official NEAR docs plus the public near/mpc, chainsig-lib, and multichain gas-station repositories.