Entropy

  • Name: Entropy
  • URL: https://docs.entropy.xyz/
  • Category: programmable signer infrastructure / chain-agnostic custody middleware / threshold-signing control plane
  • Summary: Entropy is most useful not as another MPC wallet or appchain, but as a programmable signing control plane: a dedicated chain stores per-account WASM programs and validator/keyshare assignments, while offchain signing committees only produce signatures if the onchain-selected program returns success for a given request. The analytically important split is that key custody, signing-policy evaluation, relaying, and target-chain execution are separate layers. That makes Entropy a strong comparison point for Wamu, Chain Signatures, Safe-style multisig policy layers, and custody products that flatten policy logic, signer operation, and cross-chain execution into one generic wallet surface.
  • What it does:
    • Runs a proof-of-stake Substrate chain whose validators also operate threshold-signing clients holding secret key shares
    • Lets users register accounts whose signing behavior is governed by onchain-associated WebAssembly programs rather than a fixed wallet policy surface
    • Uses signing committees plus relayer validators: users send a message to a relayer, the relayer forwards to signers, each signer evaluates the latest account program, and only then does the committee run the threshold-signing protocol
    • Uses threshold ECDSA, with docs framing support for EVM transactions plus arbitrary data signing and future expansion to other schemes
    • Stores or references account policy onchain while keeping the actual signature path offchain, so normal signing does not require an Entropy-chain transaction once the user is registered
    • Exposes a lower-layer program model where deployed WASM components can check auxiliary data, oracle-fed chain data, allowed signer keys, and custom hashing rules, but cannot call external chains or use nondeterministic inputs
  • Key claims:
    • The core reusable mechanism is not merely MPC signing; it is policy-gated threshold signing where the policy itself is a mutable onchain program surface. That makes Entropy more useful as a control-plane comparison point than as a generic custody product.
    • The docs make the relayer/signer/program split explicit. Relayers do initial checks and route requests, but signing nodes independently fetch and execute the latest program before participating in signing. This is analytically important because request routing, policy interpretation, and keyshare custody are distinct chokepoints.
    • Entropy’s program system is unusually legible. Programs are WASM components that return success/failure, may include custom hashing and config, and can chain multiple checks conceptually, but cannot fetch arbitrary offchain data. That turns signing policy into a constrained middleware layer rather than an opaque hosted rules engine.
    • The Synedrion repo is important because it surfaces the cryptographic substrate directly: CGGMP-style threshold ECDSA with identifiable aborts, key refresh, distributed key generation, and fault evidence. That means slashing or committee replacement is not an afterthought but part of the signing-failure model.
    • Entropy belongs in the active corpus because it cleanly separates chain-level coordination, policy-program authorship, relayer routing, threshold-key custody, and destination-chain execution. That decomposition would be lost if it were filed only as a generic MPC wallet, custody chain, or automation project.
  • Whitepaper: No single canonical Entropy whitepaper was found in this pass. The strongest primary materials were the official docs plus the public Synedrion implementation repository; see ../whitepapers/entropy-primary-sources-2026-05-13.md.
  • Sources:

Internal linkages

  • Strongest comparisons: chain-signatures, turnkey, and safe.

  • Use Entropy when the real question is whether signing policy lives in an onchain program, an offchain signer stack, or a vendor console.

  • Last reviewed: 2026-05-30 UTC