Anoma primary-source snapshot

Fetched: 2026-04-26 UTC

1) Official website

Source: https://anoma.net/

Selected excerpts from the official site:

Anoma is a distributed operating system for intent-centric applications. It unifies underlying blockchains into a single development environment

Apps that work like magic

Additional signals from the site:

  • The homepage markets Anoma as an intent-centric operating system rather than as a single chain, wallet, or app
  • The first-party framing emphasizes abstraction over existing chains, composability, and user-centric application design
  • The site is high-level, so it needs to be paired with specs, roadmap, and repos to understand the actual protocol surface

2) Docs overview

Source: https://docs.anoma.net/

Selected excerpts from the docs:

Anoma is the Distributed Operating System (DOS) which abstracts the complexities of existing blockchains away, providing one unified interface for users to interact with, and unified interface for developers to build on.

Blockchains like Bitcoin, Ethereum, Solana, Zcash, zkVMs, etc. are abstracted away and turned into resources for applications.

Additional signals from the docs:

  • The docs present Anoma as an abstraction and coordination layer above many chains, not just a standalone execution environment
  • The materials explicitly tie the project to intents, privacy, interoperability, and scaling
  • The “world computer” framing helps explain why the project’s operating-system language is central rather than superficial marketing

3) Roadmap

Source: https://anoma.net/roadmap

Selected excerpts from the roadmap:

Mainnet Phase 1 … The Anoma protocol adapter is deployed on Ethereum mainnet and key L2s, enabling support for settling intents across the Ethereum ecosystem.

Support for additional chains and ecosystems beyond Ethereum are rolled out over time, as well as new functionality, including private solving, FHE, MPC, threshold encryption, and Chimera chains.

Additional signals from the roadmap:

  • The roadmap clarifies that Anoma is approaching rollout through adapters and ecosystem integration rather than waiting for a single monolithic launch state
  • The participant model explicitly includes operators, developers, solvers, and users, which is useful for categorizing the project as solver/coordination infrastructure
  • Later-phase mentions of privacy, MPC, threshold encryption, and chimera chains reinforce that the protocol surface is broader than “intents” alone

4) Protocol specification

Source: https://specs.anoma.net/latest/

Selected excerpts from the spec index:

Anoma is a distributed operating system for intent-centric applications.

The Anoma protocol architecture … supports interoperability at state, network, and application levels without restricting the types of intents or computational methods used to solve them.

Additional signals from the spec:

  • The spec is a stronger source of truth than the homepage for understanding Anoma’s architectural claims
  • The entity definitions distinguish the protocol, network, and foundation, which helps avoid collapsing all “Anoma” references into one thing
  • The spec positions heterogenous trust, coordination, and resource-oriented state updates as first-class design goals

5) Research portal

Source: https://anoma.net/research

Selected signals from the research surface:

  • The research archive includes substantial first-party writing on distributed key generation, recursive proofs, heterogeneous Paxos, chimera chains, private solving, intent topologies, and the Anoma Resource Machine
  • This is a stronger-than-usual signal that the project’s real source of truth is a living combination of specs, research, and implementation repos rather than a single launch paper
  • The breadth of topics suggests a protocol family or coordination architecture, not just an app layer or cross-chain router

6) Official GitHub organization and main repo

Source: https://github.com/anoma Source: https://raw.githubusercontent.com/anoma/anoma/master/README.md

Selected excerpts from the repo materials:

This is an implementation of the Anoma protocol, whose specs can be found here

A protocol adapter contract written in Solidity enabling Anoma Resource Machine transaction settlement on EVM-compatible chains.

Anoma Abstract Resource Machine Implementation using RISC Zero zkVM

Additional signals from the repos:

  • The public repo inventory shows active work across the reference implementation, EVM adapters, ARM experiments, SDKs, and formal/spec-oriented tooling
  • The implementation posture spans both research-heavy protocol design and production-adjacent settlement infrastructure
  • The repo surfaces make it clear that Anoma is not just a research brand; there is substantial code under active development

Notes

  • This pass did not find a single canonical Anoma whitepaper that served as the primary source of truth.
  • The strongest first-party materials were the homepage, docs, roadmap, protocol specification, research archive, and active GitHub repositories.
  • Anoma appears best categorized as intent-centric operating system / interoperability architecture / solver-based coordination infrastructure.