> 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/guides/encrypt-fhe.md).

# The Encrypt FHE surface

Andromeda proxies Encrypt's fully homomorphic encryption layer on Solana: ciphertexts, computation graphs, a small DSL, decryption requests, fee accounts and ownership controls. For the concept, see [Confidential computing (FHE)](/hub/andromeda/concepts/fhe.md).

{% hint style="warning" %}
This runs against the Encrypt pre-alpha network. There is no real confidentiality guarantee yet. High-level operations require the deployment's default graph bytes and network encryption key to be registered first; check [`/capabilities`](https://api.andromedainfra.pro/capabilities).
{% endhint %}

{% hint style="info" %}
Every mutating call is a `.../prepare` endpoint returning an unsigned transaction. You sign it client-side and submit via `POST /v1/graph/submit` (or `POST /v1/private-tx/submit`). Andromeda does not sign your Encrypt transactions. Exact bodies are in the [OpenAPI spec](https://api.andromedainfra.pro/openapi.json).
{% endhint %}

## Ciphertexts

* `POST /v1/ciphertext/create` (prepare): create a ciphertext from an input.
* `POST /v1/ciphertext/read`: read a ciphertext back.
* `GET /v1/ciphertext/account/{address}`: fetch a ciphertext by its Solana account.

## Graphs

A graph is a pipeline of FHE operations over ciphertext inputs.

* `POST /v1/graph/execute/prepare`: run a graph ad hoc.
* `POST /v1/graph/register/prepare`: register a graph so it can be re-run by reference.
* `POST /v1/graph/execute-registered/prepare`: run a previously registered graph.
* `POST /v1/graph/commit/prepare`: commit a graph result.
* `POST /v1/graph/submit`: submit the signed transaction for any of the above.
* `GET /v1/graph/status/{signature}`: check execution status.
* `GET /v1/graph/operations`: list available operations.
* `POST /v1/graph/operations/register-bytes`: register the raw bytes for an operation (deployment setup; high-level flows depend on the default operations being registered).

## DSL

A typed way to build operations without hand-assembling bytecode.

* `GET /v1/dsl/types`: list the available types.
* `POST /v1/dsl/op/prepare`: build a DSL operation.

## Decryption

* `POST /v1/decrypt/request/prepare`: request decryption of a ciphertext for an authorised party.
* `GET /v1/decrypt/poll/{account}`: poll for the decrypted result.

## Network encryption key

* `GET /v1/nek/current`: the public key the network uses for this deployment. You encrypt inputs against it.

## Authorities and fees

* `POST /v1/authority/add/prepare`, `POST /v1/authority/remove/prepare`: manage which keys may act on a confidential account.
* `POST /v1/authority/register-nek/prepare`: register a network encryption key for an account.
* `POST /v1/fees/deposit/create/prepare`, `.../top-up/prepare`, `.../withdraw/prepare`, `.../request-withdraw/prepare`, `.../reimburse/prepare`: manage the fee account that pays for graph execution.
* `POST /v1/fees/config/update/prepare`: update fee configuration.

## Ownership and events

* `POST /v1/ownership/transfer/prepare`, `.../copy/prepare`, `.../make-public/prepare`: transfer, copy, or publish ownership of a confidential resource. `make-public` changes the privacy model; do it deliberately.
* `POST /v1/events/emit/prepare`: emit an on-chain event.
* `GET /v1/events/by-signature/{signature}`: look up events from a transaction.

## Private transactions and wallet balance

* `POST /v1/private-tx/submit`: submit a signed private transaction.
* `GET /v1/private-tx/status/{signature}`: check its status.
* `POST /v1/wallet/balance/init`: initialise an encrypted balance for a wallet.

## Where this leads

To make an Ika signature conditional on an FHE evaluation, use the `fhe-gated` policy: see [Confidential workflows](/hub/andromeda/guides/confidential-workflows.md).


---

# 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/guides/encrypt-fhe.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.