> ## Documentation Index
> Fetch the complete documentation index at: https://docs.confi.cash/llms.txt
> Use this file to discover all available pages before exploring further.

# Testnet status and safety

> Verify the live Confi.cash testnet deployment and understand its experimental status.

Confi.cash currently runs on Stellar testnet. Testnet is intended for development and evaluation, not real economic activity.

<Warning>
  Do not use real funds. Confi.cash has not been independently audited, and testnet state or assets may be reset without the guarantees expected from production systems.
</Warning>

## Verify the deployment

* Open the [live health response](https://confi.cash/api/health) and confirm that `ok` is `true` and `network` is `testnet`.
* Confirm that the app header displays **Testnet**.
* Use the contract links in the Confi.cash footer to inspect the active deployment on a testnet explorer.
* Treat the signed deployment release reported by the app as the source of truth instead of copying contract IDs from an old screenshot or message.

## Current public status

The live health response publishes the active network, pool and verifier identifiers, amount-blind capability, threshold configuration, deployment release, and public privacy flags.

These fields are operational claims from the running service. They do not replace an independent audit or guarantee that your browser, wallet, network path, or the operator is uncompromised.

## Safer testing practices

* Use a separate testnet wallet account.
* Never enter a mainnet seed phrase into Confi.cash or any website.
* Review every wallet prompt and reject unexpected assets, amounts, recipients, or contract calls.
* Start with the smallest available standard test amount.
* Keep the app open while it generates proofs or reconciles an uncertain transaction.
* Use **Rescan** or **Check status** before retrying an interrupted value-moving action.
* Save transaction hashes when reporting a problem. Do not share private keys, wallet recovery phrases, note secrets, or encrypted recovery data.

## Availability expectations

Browser proving can take time and requires large WebAssembly and proving-key downloads. Testnet ledgers, RPC services, liquidity, committee members, and the Confi.cash operator can all be unavailable.

The amount-blind swap path is designed to fail closed. If its required committee or reviewed deployment configuration is unavailable, swaps should stop instead of falling back to a plaintext batch path.

<Info>
  A healthy service means its automated checks passed at that moment. It does not mean the protocol is production-ready.
</Info>