Chain services
rpc.animica.org (JSON-RPC), explorer.animica.org, pool.animica.org (stratum :3333 / solo :3334), and the non-custodial wallet apps on /wallet (the former web wallet at wallet.animica.org was discontinued on 2026-07-11).
About
What Animica is
Animica is an open-source, proof-of-work Layer-1 blockchain whose accounts and transactions are signed with the post-quantum ML-DSA-65 scheme. It runs a deterministic Python smart-contract VM, an ANM-native Layer-2 rollup, and an AI-compute framework (AICF) that lets miners and GPU operators serve inference for ANM. Mainnet has been producing blocks since 6 April 2026.
The short version
Most blockchains in production today sign transactions with elliptic-curve schemes (ECDSA or Ed25519). Those schemes are expected to fail against a sufficiently large quantum computer, and anything recorded on a public ledger today can be attacked later. Animica took the opposite starting point: there is no elliptic-curve signature anywhere in consensus. Every account key is an ML-DSA-65 keypair (FIPS 204, the standardised form of Dilithium3), every transaction carries an ML-DSA-65 signature, and the address itself is derived from a SHA3-256 hash of the public key. The cost is size: a public key is 1,952 bytes and a signature 3,309 bytes, which is why the transaction format, the P2P layer, and the L2 rollup are all designed around large signatures rather than bolted on afterwards.
The second design choice is how blocks are accepted. Animica uses SHA3-256 proof-of-work with a scoring rule called PoIES (Proof-of-Integrated-External-Services). A block clears the threshold Θ when its hash work, plus any verified useful-work evidence, is high enough. The protocol defines how AI, quantum, storage and VDF proofs would add to that score. On mainnet today, however, blocks are accepted on hash work alone: the reference miner does not attach useful-work proofs, and the verification rule for them runs in shadow mode. We say this plainly because the difference between "the protocol supports X" and "X is enforced on mainnet" matters to anyone evaluating the chain.
The third choice is the contract language. Contracts are written in a strict, deterministic subset of Python, compiled to a small IR, and executed by a gas-metered interpreter. On-chain execution of contract calls activated at block 75,000 (release 9.6.0); before that height every CALL reverted.
Mainnet at a glance
| Parameter | Value |
|---|---|
| Chain id | 1 (mainnet) |
| Genesis time | 2026-04-06T00:00:00Z (header timestamp 1775433600) |
| Genesis hash | 0xa0892158cf997c56e91d0aa12e60c36037dae34800a2b54111a8fa17ec88b7de |
| Fork id | 3511060514 |
| Native coin | ANM, 9 decimals (1 ANM = 1,000,000,000 nANM) |
| Signatures | ML-DSA-65 (FIPS 204), scheme id 0x1003 |
| Addresses | bech32m, prefix anim1 |
| Block target | 60 seconds |
| Software line | 10.x (python/pyproject.toml: 10.4.4) |
Values can be checked against the public RPC with chain.getChainIdentity and
chain.getBlockByHeight [0, false]. The full parameter set and fork history is on the
Network page.
When mainnet launched and what has changed since
The canonical genesis header is timestamped 2026-04-06T00:00:00Z. Consensus rules have since been
tightened through forward-only, height-gated forks: post-quantum hardening and header root
commitments at block 40,000 (release 6.0.1), the address-freeze rule at 42,000 (7.0.0), the
85/15 miner/foundation subsidy split at 42,001 (7.1.0), state-commitment enforcement at 44,444
(7.1.9), the inert service-IOU settlement carve at 50,000 (8.0.1), and a bundle at 75,000
(9.5.0 to 9.6.0) that introduced a bounded retarget, a uniform 100-block reorg bound, value-carrying
CALL, on-chain VM execution and the 50/25/25 reward split between miner, treasury and inference
providers. Each of these is documented in docs/ANIMICA_2026_STATE.md,
docs/CHANGELOG.md and core/network_params.py, and summarised on the
Roadmap.
What is open source
The whole stack is public. The monorepo at
gitlab.com/Animica/animica-core
contains the node (core/, consensus/, p2p/, rpc/),
the Python VM (vm_py/), the L2 (l2/), AICF (aicf/), the
miners (mining/), wallets, SDKs, the explorer, the pool, and this website. A
node-focused mirror lives at
animicaorg/animica-core.
The runnable package is published to PyPI as
animica;
pip install animica installs the node, CLI, wallet, miner and the MCP server.
| Component | License |
|---|---|
| Node, consensus, VM, P2P, RPC, AICF, SDKs | Apache-2.0 (repo LICENSE); docs/legal/LICENSING.md also offers MIT for most packages |
| website/ (this site) | MIT |
| docs/ | CC BY-SA 4.0 unless a file says otherwise |
| Name, logo, wordmark | Not open-licensed; see docs/legal/TRADEMARKS.md |
The repository root LICENSE is Apache License 2.0. docs/legal/LICENSING.md
describes the per-package picture, including third-party notices for vendored components such as
Pyodide (MPL-2.0). Files with an explicit SPDX header follow that header.
How the project is run
Animica does not have a token-vote DAO. The documented process, in docs/governance/,
separates two kinds of change. Parameter governance covers dials that can move
without changing serialisation or state layout: the Θ retarget schedule, PoIES caps, fee floors,
gas tables, AICF SLA thresholds, DA and randomness parameters. Protocol upgrades
cover anything that changes encoding, state layout or consensus-critical behaviour, and ship as
versioned releases with a height-gated activation.
The community process (docs/governance/COMMUNITY.md) uses Animica Improvement
Proposals (AIP-####): a proposal issue with at least 72 hours of initial feedback, an
RFC pull request, a review window of 7 days for low or medium risk and 14 days for high risk or
upgrades, a 5-day last call, then enactment through a signed governance bundle with a timelock.
Reviewers are expected to cover security, economics, operations and protocol compatibility.
In practice, every consensus change on mainnet so far has been shipped by the core maintainers as
a release with a coordinated activation height and a public upgrade notice (for example, "run
7.1.1 before block 42,000"). The foundation treasury address that receives its subsidy share is
fixed in consensus/rewards.py and is visible on the explorer, so the split can be
audited by anyone.
Properties the project operates
AI and compute
animica.dev (free keyless OpenAI-compatible API at /v1), console.animica.org (AI API keys), x402.animica.dev (per-call agent payments).
Learning and building
academy.animica.org, studio.animica.org, pay.animica.dev (merchant payments, 2.00% fee).
Where ANM trades
ANM trades on NonKYC (ANM/USDT): nonkyc.io/market/ANM_USDT. There is no mainnet faucet. This site does not give investment advice; see the Terms.
Contact
- General: contact@animica.org
- Security reports: security@animica.org (see Security and security.txt)
- Bugs and feature requests: GitHub issues
- Announcements: @animicaorg on X
We do not currently list a Discord or Telegram channel. Be wary of anyone claiming to represent Animica on chat platforms, especially if they ask for seed phrases or "verification" payments.
Trademarks and licensing
The name "Animica", the logo and the wordmark are trademarks and are not covered by the code
licenses. You may use the name nominatively ("Wallet X for Animica", "runs on Animica") and link
to first-party properties; you may not ship a product named "Animica Something", alter the logo,
or imply endorsement. Forks must replace the marks. The full rules are in
docs/legal/TRADEMARKS.md, and the licensing summary with third-party notices is in
docs/legal/LICENSING.md, both in the repository.
Sources
docs/ANIMICA_2026_STATE.md · docs/governance/OVERVIEW.md · docs/governance/COMMUNITY.md · docs/legal/LICENSING.md · docs/legal/TRADEMARKS.md · core/network_params.py · LICENSE · python/pyproject.toml · live rpc.animica.org (chain.getChainIdentity, 2026-08-23)