> For the complete documentation index, see [llms.txt](https://docs.arcan.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcan.finance/development/overview.md). # Overview Write and test confidential contracts before you point them at Robinhood. The local stack deploys the same host contracts your app will call: the access list, the executor, and the input verifier. The local coprocessor evaluates the FHE so tests can encrypt, transfer, and decrypt. ## Guides * [Hardhat](/development/hardhat.md) for a JavaScript test suite and the Arcan SDK in the same repo. * [Foundry](/development/foundry.md) for Solidity tests. Both use `@arcan/solidity` for the library and `ArcanConfig` for addresses. In tests, the config points at the local host contracts, not at a public network. ## What a test should prove * An input with a bad proof is rejected. * A transfer changes the sender and recipient handles. * The plaintext amount never appears in the transaction receipt. * An account on the access list can decrypt. * An account that was not granted the handle cannot. * A `FHE.select` branch does not reveal which side was taken. ## Keys in tests Generate a throwaway key for the local node. Do not reuse a key that has ever held value. Do not commit a shared test mnemonic into 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.arcan.finance/development/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.