Skip to content
Support

Getting help with Animica

Animica is an open-source project run by a small group of maintainers. Most questions are answered faster by the written guides than by email, so this page points you at the right document first, explains how to report bugs and security issues, and tells you what to include.

Read the FAQ Open a GitHub issue Report a vulnerability
Where to look

Guides and explainers

Long-form, source-grounded articles: mining, running a node, wallets, transactions, the RPC API, contracts, L2 and AICF. Start with the FAQ and the mining and node guides.

animica.org/learn

Documentation hub

Reference pages rendered from the repository, plus the EVM- and Bitcoin-compatible RPC notes. The canonical docs live under docs/ in the monorepo.

animica.org/docs

Email

General questions, partnership and listing enquiries, and anything that should not be public. Security reports go to a separate address (below).

contact@animica.org

Troubleshooting guides by topic

These are the pages that resolve the majority of support requests. Each one is written from the repository documentation and kept in step with the current 10.x release line.

  • Mining guide: installing animica, running animica up, pointing an external miner at stratum+tcp://pool.animica.org:3333 (PPS) or :3334 (solo), reading pool statistics, and why rewards take time to appear.
  • Running a node: animica node up, ports 8545 (RPC) and 30333 (P2P), data directories, sync behaviour, and the animica node doctor checks.
  • Wallets and recovery: which wallet to use, how the 12/24-word mnemonic maps to an anim1zqp… address, and why an address from a different derivation path is not "lost".
  • Transactions and fees: the 21,000 nANM transfer fee, the validAfter/validUntil window, and what each RPC error code means.
  • Reading the explorer: confirmations versus "finalized", what a zero stateRoot in the head means, and how to verify a payment.
  • Extended FAQ: the long-form version of the site FAQ, covering protocol, mining, building and economics.

Before you ask: a short checklist

Including the following in a first message usually turns a multi-day back-and-forth into a single reply. None of it requires sharing secrets.

  1. Which version you are running: pip show animica (the current line is 10.x) and, for a wallet, the app version from its About screen.
  2. The network: mainnet is chain id 1. Testnet and devnet use different chain ids and different ports, and a transaction signed for one will be rejected on another (error -32011).
  3. The exact command you ran and the exact error text. Copy the JSON-RPC error object if there is one; the code (for example -32013 insufficient funds, -32017 fee too low) usually identifies the cause.
  4. A transaction hash or address when the question is about a payment, so it can be checked on explorer.animica.org. Never include a seed phrase, private key or keystore file.
  5. The output of animica node doctor (node problems) or animica ena doctor (ENA problems), and whether curl -X POST https://rpc.animica.org/rpc with chain.getHead works from the same machine.
  6. What you expected to happen and what happened instead, including timestamps, so logs on our side can be correlated.

Reporting a bug

Open an issue at gitlab.com/Animica/animica-core/-/issues. Give it a title that names the component (rpc, mining, wallet-extension, vm_py, l2, aicf, website) and the symptom. Paste the checklist items above. If the problem is a wallet balance or a missing payout, include the address and transaction hash; if it is a node that will not sync, include the head height from animica node status and from the public explorer so the gap is visible. Pull requests are welcome for documentation fixes and small, well-tested changes; discuss larger changes in an issue first.

Security disclosure

Do not file security vulnerabilities as public issues. Email security@animica.org with the affected component, version or commit, reproduction steps, and your assessment of impact. The published policy (docs/legal/SECURITY_POLICY.md) commits to acknowledging reports within 3 business days, an initial severity assessment (CVSS v3.1) within 7 days, and a fix window that is typically 30 to 90 days depending on severity. Good-faith research that avoids privacy violations, service degradation and data exfiltration is covered by the policy's safe harbour. The machine-readable contact record is at /.well-known/security.txt. The Security page has the scope, the threat-model summary and key-handling advice for users.

What to expect

There is no paid support tier and no service-level agreement for community support. GitHub issues are read by the maintainers; clear, reproducible reports are usually answered within a few days, and fixes ship in the next animica release on PyPI. Email to contact@animica.org is answered on a best-effort basis. Security reports follow the timelines above. Hosted services (the public RPC, explorer, pool and wallet) are operated by the project and their live state is visible on the Status page; if one of them is down, that page is the fastest way to confirm it before reporting.

We cannot recover funds sent to the wrong address, reverse a confirmed transaction, or restore a wallet without its mnemonic. Animica wallets are non-custodial: the project never holds your keys and cannot move your ANM.

Things we will never ask for

  • Your seed phrase, private key, keystore file or wallet password.
  • A payment to "verify", "unlock" or "synchronise" a wallet.
  • Remote access to your machine.

We do not currently operate a Discord or Telegram channel. Official announcements are posted on @animicaorg and in GitHub releases.

Sources

docs/legal/SECURITY_POLICY.md · docs/security/RESPONSIBLE_DISCLOSURE.md · docs/TROUBLESHOOTING.md · docs/MINING_TROUBLESHOOTING.md · docs/network-docker-compose.md · website/public/.well-known/security.txt