dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0020
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0020 [2020/05/20 14:23] char |
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0020 [2021/08/18 11:21] (current) murphy |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ==== EIP 20: ERC-20 Token Standard ==== | ==== EIP 20: ERC-20 Token Standard ==== | ||
| - | [[dido:public:ra:xapend.stds:defact:ethereum:eip| Return to Ethereum ERCs ]] | + | [[dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip| Return to Ethereum ERCs ]] |
| : **Note**: The following is an excerpt from the official Ethereum site. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference. | : **Note**: The following is an excerpt from the official Ethereum site. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference. | ||
| === Overview === | === Overview === | ||
| - | ://It is the most common and well-known standard within all crypto community. 99% (if not all) issued ICO tokens on top of the Ethereum implements this standard. The key benefit we get here is that any application or other smart contracts can interact with a token in a standard manner without a need of knowing other details about the token. Therefore, we have a very pleasant way to create any ICO token and have a standard way to interact with all of them like they are all the same. For instance, crypto wallet developers can avoid custom development and integrations to add new tokens. All they need to know is the Ethereum Token address that implements the standard.// | + | ://It is the most common and well-known standard within all crypto community. 99% (if not all) issued [[dido:public:ra:xapend:xapend.a_glossary:i:ico]] [[dido:public:ra:xapend:xapend.a_glossary:t:tokens|tokens]] on top of the Ethereum implements this standard. The [[dido:public:ra:xapend:xapend.a_glossary:k:key|key]] benefit we get here is that any [[dido:public:ra:xapend:xapend.a_glossary:a:application|application]] or other smart contracts can interact with a token in a standard manner without a need of knowing other details about the token. Therefore, we have a very pleasant way to create any ICO token and have a standard way to interact with all of them like they are all the same. For instance, crypto [[dido:public:ra:xapend:xapend.a_glossary:w:wallet|wallet]] developers can avoid custom development and integrations to add new tokens. All they need to know is the Ethereum Token address that implements the standard.// |
| : Source: [[https://hackernoon.com/5-erc-standards-every-ethereum-developer-should-know-about-c1ea79d3483e]] | : Source: [[https://hackernoon.com/5-erc-standards-every-ethereum-developer-should-know-about-c1ea79d3483e]] | ||
| Line 20: | Line 20: | ||
| === Abstract === | === Abstract === | ||
| - | The following standard allows for the implementation of a standard API for tokens within smart contracts. This standard provides basic functionality to transfer tokens, as well as allow tokens to be approved so they can be spent by another on-chain third party. | + | The following standard allows for the implementation of a standard [[dido:public:ra:xapend:xapend.a_glossary:a:api|API]] for tokens within smart contracts. This standard provides basic functionality to transfer tokens, as well as allow tokens to be approved so they can be spent by another on-chain third party. |
dido/public/ra/xapend/xapend.b_stds/defact/ethereum/eip/erc_0020.1589999021.txt.gz · Last modified: 2020/05/20 14:23 by char
