> For the complete documentation index, see [llms.txt](https://docs.useglade.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.useglade.org/architecture/onchain-contracts.md).

# The onchain contracts

Balances and transfers in Glade live in a confidential token contract deployed on Robinhood Chain. It is an ERC-20 wrapper whose balances are encrypted, built along the lines of Zether. Because the EVM offers no native way to transfer value confidentially, Glade built this layer itself, published the source, and verified the deployed code on-chain.

There is nothing running beside it. Glade keeps no private ledger and no internal record of who owns what, so reading the token contract tells you everything about how money moves.

***

## Storage inside the token contract

`ConfidentialToken` wraps an ordinary ERC-20, which on Robinhood Chain is USDG. For every registered account it stores the balance as an ElGamal ciphertext over the alt\_bn128 curve. Registration is a one-time call to `register` with the account's ElGamal public key. After that, the account's balance is one ciphertext made of two points:


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.useglade.org/architecture/onchain-contracts.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.