> For the complete documentation index, see [llms.txt](https://shinkalabs.gitbook.io/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shinkalabs.gitbook.io/hub/andromeda/reference/limitations.md).

# Known limitations

The honest list of what does not work yet or works in a reduced form. See also [Status & disclaimers](/hub/andromeda/status.md).

## Network and environment

* **Devnet only.** There is no mainnet endpoint. Do not custody real value.
* **Mock signer on the Ika side.** The integration runs against the pre-alpha validator network with a single mock signer. There is no real MPC threshold guarantee yet.
* **Encrypt is pre-alpha.** There is no real FHE confidentiality guarantee yet. Do not describe confidential flows as private to end users.
* **State may be wiped.** Backend caches, identity records and session metadata will be reset when the underlying networks move to Alpha.
* **No third-party audit yet.** The eight on-chain programs were audited internally in May 2026; a third-party audit is pending before any mainnet move.

## On-chain schemes

* **No on-chain validation for sr25519, Ristretto, or pure Bitcoin Taproot.** Runtime precompiles do not exist for these, and Andromeda will not bridge them with an off-chain attestor. Substrate users enroll recovery owners with Ed25519 or Secp256k1 (both native to Substrate); Bitcoin users prove ownership via BIP-137 message signing (Secp256k1). See [Zero attestor](/hub/andromeda/concepts/zero-attestor.md).
* **Full WebAuthn is quorum-members-only.** A full WebAuthn assertion is large; it fits in a member's own contribution transaction but not in the single-transaction primary-recovery path. For the primary slot, a passkey is used in compact raw-P-256 form (Secp256r1). See [Precompile validation](/hub/andromeda/on-chain-programs/precompiles.md).

## FHE surface

* **High-level operations require setup.** A deployment's default graph operation bytes and network encryption key must be registered before the high-level FHE flows work. Check [`/capabilities`](https://api.andromedainfra.pro/capabilities).
* **You assemble the destination side.** For the Encrypt surface, Andromeda returns unsigned transactions; you sign and submit. Andromeda does not sign your Encrypt transactions.

## Identity and data

* **PII encryption-at-rest is being hardened.** Identity records, account links and email tokens are wrapped with AES-256-GCM, but this is still being hardened during pre-alpha; do not assume a database leak is fully PII-safe yet.
* **Deleting identity data does not delete the on-chain dWallet.** `DELETE /me` purges Andromeda-side records; the dWallet lives on Solana and persists. This is stated to the user.

## Feature availability

* **Identity and recovery are opt-in per deployment.** Do not assume they are present; check [`/capabilities`](https://api.andromedainfra.pro/capabilities).

## Documentation

* **The OpenAPI spec is canonical.** Where this documentation and the [spec](https://api.andromedainfra.pro/openapi.json) disagree, the spec wins. If you spot a discrepancy, see [Responsible disclosure](/hub/andromeda/security/disclosure.md) or open an issue on the repository.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://shinkalabs.gitbook.io/hub/andromeda/reference/limitations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.