> For the complete documentation index, see [llms.txt](https://plabs.gitbook.io/plabs-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://plabs.gitbook.io/plabs-docs/privacy-core/perc20/eip-8302.md).

# ERC-8302 approved spending extension

**ERC-8302 — Private Fungible Tokens** is the **current ERC submission** that extends the earlier pERC20 design with **ERC-20 approved spending** (`approve`, `allowance`, `transferFrom`) via ZIP-32 subaccounts.

## Metadata

| Field       | Value                                                                                    |
| ----------- | ---------------------------------------------------------------------------------------- |
| ERC         | **8302**                                                                                 |
| Title       | Private Fungible Tokens                                                                  |
| Status      | Draft                                                                                    |
| ERCs PR     | [ethereum/ERCs #1817](https://github.com/ethereum/ERCs/pull/1817)                        |
| Discussions | [Magicians #28796](https://ethereum-magicians.org/t/perc20-private-token-standard/28796) |

## What this proposal adds

This revision **extends** the pERC20 protocol published in [ERCs PR #1796](https://github.com/ethereum/ERCs/pull/1796) (ERC-8287). The main delta:

| Addition                         | Mechanism                                         |
| -------------------------------- | ------------------------------------------------- |
| `approve(spender, N)`            | ZIP-32 subaccount; fund via on-chain `transfer`   |
| `allowance(owner, spender)`      | Off-chain scan of subaccount balance              |
| `transferFrom(from, to, amount)` | Spender spends subaccount; on-chain = `transfer`  |
| On-chain indistinguishability    | All movement collapses to `transfer(PrivacyCall)` |

The result is **capability-complete with** [**ERC-20**](https://eips.ethereum.org/EIPS/eip-20) but **not byte-compatible** (different ABI, no public balances, no `Transfer`/`Approval` events).

→ Deep dive: [Approved spending](/plabs-docs/privacy-core/perc20/approved-spending.md) · `docs/zip-32-approve-extend.md`

## Relationship to ERC-8289

| ERC                                                     | Role                                                                                                                                             |
| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| [ERC-8289](/plabs-docs/privacy-core/perc20/eip-8289.md) | Earlier draft number used in this repo’s `docs/eip-draft.md` before editor assignment                                                            |
| **ERC-8302**                                            | **Assigned sequential number** by EIP editors ([review on #1817](https://github.com/ethereum/ERCs/pull/1817)); canonical file `ERCS/erc-8302.md` |

Content-wise, **8302 is the full normative spec** (Privacy Core + pERC20 + approve). The 8289 → 8302 change is a **number reassignment**, not a separate token standard.

## Canonical sources

| Source                         | Path                                                                         |
| ------------------------------ | ---------------------------------------------------------------------------- |
| ERCs repository (submission)   | `ERCS/erc-8302.md` in [PR #1817](https://github.com/ethereum/ERCs/pull/1817) |
| Reference implementation draft | `docs/eip-draft.md` in PERC20 repo (update `eip:` to 8302 when synced)       |

## GitBook ↔ spec

| GitBook                                                                       | ERC-8302 section                             |
| ----------------------------------------------------------------------------- | -------------------------------------------- |
| [Privacy Core](/plabs-docs/privacy-core/overview.md)                          | Underlying Protocol, Call Format             |
| [Interface mapping](/plabs-docs/privacy-core/perc20/interface-and-erc20.md)   | Interface Overview                           |
| [Operations](/plabs-docs/privacy-core/perc20/operations.md)                   | mint / transfer / burn                       |
| [**Approved spending**](/plabs-docs/privacy-core/perc20/approved-spending.md) | **approve / transferFrom (this PR’s focus)** |
| [Compliance freeze](/plabs-docs/privacy-core/compliance-freeze.md)            | cmxFrozenRoot                                |

## Reference implementation

* `contracts/ptoken/PERC20.sol`
* GitHub: `PERC20Labs/pERC20_`

## Related

* [ERC-8289 index](/plabs-docs/privacy-core/perc20/eip-8289.md) — prior draft number / repo copy
* [ERC-8287 / PR #1796](https://github.com/ethereum/ERCs/pull/1796) — earlier pERC20 without approve extension
* [EIP-20](https://eips.ethereum.org/EIPS/eip-20) — public fungible token
* [EIP-8182](https://eips.ethereum.org/EIPS/eip-8182) — protocol shielded pool (complementary)


---

# 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://plabs.gitbook.io/plabs-docs/privacy-core/perc20/eip-8302.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.