> For the complete documentation index, see [llms.txt](https://docs.coti.io/coti-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coti.io/coti-documentation/coti-privacy-portal/developer-guide/privateerc20.sol.md).

# PrivateERC20.sol

### Overview

[`PrivateERC20`](https://github.com/coti-io/coti-contracts/blob/main/contracts/token/PrivateERC20/PrivateERC20.sol) is an abstract Solidity contract that implements a fully encrypted ERC20 token on the COTI network.

Unlike a standard ERC20, where balances and transfer amounts are publicly visible on-chain, `PrivateERC20` stores balances and allowances as ciphertexts (encrypted values).

These values:

* can only be decrypted by the token holder
* use a personal AES key managed via the COTI Snap

All token operations, such as transfers, minting, and burning, are performed directly on encrypted data.

### Encrypted Computation

Encryption and arithmetic on encrypted values are handled by COTI's [`MpcCore`](/coti-documentation/how-coti-works/advanced-topics/precompiles.md) precompile at address `0x64`.

This precompile enables the network to perform operations such as:

* addition
* subtraction
* comparisons

on encrypted numbers without revealing the underlying plaintext, including to validators.

### How PrivateERC20 differs from ERC20

PrivateERC20 follows the ERC20 interface, but changes how data is stored and exposed.

| Feature                            | Standard ERC20 | PrivateERC20                            |
| ---------------------------------- | -------------- | --------------------------------------- |
| Balances visible on-chain          | Yes (public)   | No (encrypted ciphertext)               |
| Transfer amounts visible           | Yes            | No                                      |
| Allowances visible                 | Yes            | No                                      |
| `totalSupply()` returns real value | Yes            | No — always returns `0` for privacy     |
| Requires AES key to read balance   | No             | Yes                                     |
| Supports plain uint256 operations  | Yes            | Yes                                     |
| Supports encrypted operations      | No             | Yes (`itUint256`, `gtUint256` variants) |

### How it works

#### Balances

Balances are stored on-chain as `ctUint256` (ciphertext). Each account maintains two ciphertext values:

* `ciphertext` - used by the MPC network
* `userCiphertext` - re-encrypted for the user

#### Transfers

Transfers are executed via the MPC precompile using `MpcCore.transfer()`, which atomically updates both sender and receiver balances in encrypted form.

#### Reading your balance

To read a balance:

* call `balanceOf(address)` to retrieve the ciphertext
* decrypt it locally using your AES key via the COTI SDK

#### Writing encrypted amounts

Operations such as transfer, approve, mint, and burn require constructing an `itUint256`:

* an AES-encrypted value
* plus an ECDSA signature

This allows the MPC network to verify that the input was created by the rightful key holder.

#### Onboarding

Onboarding registers your wallet's encryption address on-chain via `setAccountEncryptionAddress()`.

This enables the contract to re-encrypt balances specifically for your AES key.


---

# 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://docs.coti.io/coti-documentation/coti-privacy-portal/developer-guide/privateerc20.sol.md?ask=<question>&goal=<endgoal>
```

`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.