> For the complete documentation index, see [llms.txt](https://nocturne-xyz.gitbook.io/nocturne/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nocturne-xyz.gitbook.io/nocturne/protocol-details/contracts/teller.md). # Teller The Teller contract stores deposited funds and serves as the entry-point for processing bundles of operations. More specifically, the Teller is in charge of two things: non-custodially holding user funds and verifying JoinSplit proofs when processing a bundle of operations. After verifying the JoinSplit proofs, actual execution of the operations is delegated to the Handler contract. **Storing Funds** When a deposit is completed from the Deposit Manager, the Teller receives the deposit assets. It also calls the Handler contract (see next section) to insert a new note into the commitment tree corresponding to the deposit. Later on, when the Handler needs to take up assets for executing an operation, it will call the Teller's `requestAssets` method to gather the funds needed during operation execution. **Entrypoint / Validating Proofs** When a bundler calls `processBundle` on the Teller, the Teller will batch-verify all joinsplit proofs contained within the bundle to amortize gas costs. If the batched proof verification passes, it will pass operations to the Handler contract one-by-one for processing and execution. --- # 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, and the optional `goal` query parameter: ``` GET https://nocturne-xyz.gitbook.io/nocturne/protocol-details/contracts/teller.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.