# ERC725 Smart Contract Based Account

## Simple explanantion

Identity standard for publishing and managing an iddentity via smart contract on an EVM-based blockchain, the identity is represented by its chain address.

> Relates to ERC735 which ERC725 supports. [ERC735](https://github.com/ethereum/EIPs/issues/735) deals with management of claims made about ERC725 identity

### EIP Explanation

Interface standard for a smart contract based account with attachable key value store

"Standardizing a minimal interface for a smart contract based account allows any interface to operate through these account types. Smart contact based accounts following this standard have the following advantages:

* can hold any asset (native token, e.g. ERC20 like tokens)
* can execute any smart contract and deploy smart contracts
* have upgradeable security (through owner change, e.g. to a Gnosis safe)
* are basic enough to work for a long time
* are extensible through additional standardization of the key/value data.
* can function as an owner/controller or proxy of other smart contracts"- EIP Author

Implementation: <https://eips.ethereum.org/EIPS/eip-725>

## Implementation project

ERC725 implementation is used on Universal Profiles which is live on Test network, [Project link](https://universalprofile.cloud/)

### Further reading

* First impressions with ERC 725 and ERC 735 — identity and claims: <https://hackernoon.com/first-impressions-with-erc-725-and-erc-735-identity-and-claims-4a87ff2509c9>
* ERC725 Alliance <https://erc725alliance.org/>
* Projects implemented ERC725: <https://github.com/ERC725Alliance/ERC725/blob/master/docs/use-cases.md>


---

# Agent Instructions: 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:

```
GET https://nft-standards.gitbook.io/nft-standards-wiki/standards/erc725-smart-contract-based-account.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.