Agoric

• Name: Agoric
• URL: https://agoric.com/
• Category: JavaScript smart-contract platform / cross-chain orchestration infrastructure / Cosmos-based Layer 1
• Tags: cosmos-ecosystem
• Summary: Agoric is a Cosmos-based smart-contract chain whose real angle is orchestration, not the old JavaScript on a blockchain pitch by itself. The important part is that it packages long-lived cross-chain coordination, time-based execution, and first-party economic primitives like Zoe and ERTP into one developer stack. That makes it a useful control-plane note for cross-chain application logic, even if much of the surrounding rhetoric still sounds broader than the thing.
• What it does:
  • Runs a Cosmos-based chain where contracts are written in hardened JavaScript
  • Packages cross-chain orchestration so contracts can initiate external actions, wait across blocks, and continue later
  • Uses IBC and related interoperability paths to move messages and assets across chains
  • Ships a full builder stack around the chain, including the SDK, CLI, tutorials, example dapps, UI tooling, and API references
  • Treats Zoe and ERTP as first-party safety and asset-accounting primitives rather than leaving that layer entirely to application code
  • Supports staking and governance with BLD while current docs frame IST as the fee token
• Key claims:
  • The docs explicitly define Agoric as a Cosmos-based Layer 1 for cross-chain smart contracts in JavaScript, which is the cleanest short description of the stack
  • The asynchronous multi-block model matters more than the language branding: contracts can wait on cross-chain responses and scheduled events instead of pretending everything important happens in one transaction
  • Zoe and ERTP are the strongest reason not to file Agoric as just another appchain. They expose a deliberate economic-safety and asset-primitive layer inside the platform itself
  • The current homepage pushes Agoric Orchestration, but the docs and repos still show a broader developer platform with contract tooling, API surfaces, examples, and network operations software
  • The papers archive is still analytically useful because it keeps the capability-security and robust-composition lineage visible instead of reducing the project to recent orchestration marketing
• Whitepaper: No single current canonical Agoric whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official docs corpus, SDK repositories, and the first-party papers archive at papers.agoric.com; see ../whitepapers/agoric-primary-sources-2026-04-30.md.
• Sources:
  • https://agoric.com/
  • https://docs.agoric.com/what-is-agoric
  • https://docs.agoric.com/guides/getting-started/
  • https://github.com/Agoric/
  • https://github.com/Agoric/agoric-sdk
  • https://github.com/Agoric/agoric-sdk/blob/master/README.md
  • http://papers.agoric.com/papers/

Internal linkages

• Best application-architecture comparison: anoma
• Best outbound-control contrast: chain-signatures
• Best broader interop-network contrast: axelar

Control surface

• The chain, Zoe/ERTP primitives, contract execution, and BLD / IST network mechanics are the legible part.

• The harder power sits around validator governance, connector paths, relayers, orchestration defaults, and the tooling stack developers actually inherit.

• Read Agoric as a coordination stack first. If the orchestration layer stays operator-heavy, the JavaScript smart contracts pitch is mostly presentation wrapped around routing policy.

• Last reviewed: 2026-06-01 UTC