Passar al contingut principal

Ajudeu a traduir aquesta pàgina

🌏

Esteu veient aquest pàgina en anglès perquè encara no l'hem traduïda. Ajudeu-nos a traduir aquest contingut.

Traduïu la pàgina

No conté errors!🐛

Aquesta pàgina no està essent traduïda. De moment hem deixat aquesta pàgina intencionadament en anglès.

Aquesta pàgina és incompleta i ens encantaria que ajudéssiu. Editeu aquesta pàgina i afegiu qualsevol cosa que cregueu útil per als altres.

Ethereum Development Standards

Darrera edició: , Invalid DateTime
Edita la pàgina

Standards overview

The Ethereum community has adopted many standards that help keep projects (such as Ethereum clients and wallets) interoperable across implementations, and ensure smart contracts and dapps remain composable.

Typically standards are introduced as Ethereum Improvement Proposals (EIPs), which are discussed by community members through a standard process.

Types of standards

There are 3 types of EIPs:

  • Standards Track: describes any change that affects most or all Ethereum implementations
  • Meta Track: describes a process surrounding Ethereum or proposes a change to a process
  • Informational Track: describes an Ethereum design issue or provides general guidelines or information to the Ethereum community

Furthermore, the Standard Track is subdivided into 4 categories:

  • Core: improvements requiring a consensus fork
  • Networking: improvements around devp2p and Light Ethereum Subprotocol, as well as proposed improvements to network protocol specifications of whisper and swarm.
  • Interface: improvements around client API/RPC specifications and standards, and certain language-level standards like method names and contract ABIs.
  • ERC: application-level standards and conventions

More detailed information on these different types and categories can be found in EIP-1

Token standards

  • ERC-20 - A standard interface for fungible (interchangeable) tokens, like voting tokens, staking tokens or virtual currencies.
    • ERC-1363 - Defines a token interface for ERC-20 tokens that supports executing recipient code after transfer or transferFrom, or spender code after approve
  • ERC-721 - A standard interface for non-fungible tokens, like a deed for artwork or a song.
    • ERC-2309 - A standardized event emitted when creating/transferring one, or many non-fungible tokens using consecutive token identifiers.
    • ERC-4400 - Interface extension for EIP-721 consumer role
    • ERC-4907 - Add a time-limited role with restricted permissions to ERC-721 tokens.
  • ERC-777 - (NOT RECOMMENDED) A token standard improving over ERC-20.
  • ERC-1155 - A token standard which can contain both fungible and non-fungible assets.
  • ERC-4626 - A tokenized vault standard designed to optimize and unify the technical parameters of yield-bearing vaults.

Learn more about token standards.

Further reading

Know of a community resource that helped you? Edit this page and add it!

Ajuda'ns amb aquesta pàgina

Si ets un expert en el tema i vols contribuir, edita aquesta pàgina i escriu tot el que saps.

Seràs reconegut i estaràs ajudant a la comunitat Ethereum!

Utilitza aquesta opció flexible plantilla de documentació

Dubtes? Pregunta'ns al canal #content al nostre Servidor Discord

Edita la pàgina

Ha estat útil aquest article?