Smart Contract Standards
The plugin comes with a variety of common Ethereum Smart Contract Standards. This page will give you an overview of what is included and ready-to-use.
note
Remember, you are not limited by the Smart Contract Standards that come with this plugin. You can always add your own Contract ABI data assets to support any Smart Contracts you wish to use.
Please let us know if there are any standards that would be relevant to you and your projects, so we could add them in the near future for everyone.
Legend
| Standard Prefix | Description |
|---|---|
| ERC | Ethereum Request for Comment |
| EIP | Ethereum Improvement Proposal |
| LSP | Lukso Standard Proposal |
ERCs
| Standard | Simple Summary |
|---|---|
| ERC-20 Token Standard | A standard interface for tokens. |
| ERC-165 Standard Interface Detection | Creates a standard method to publish and detect what interfaces a smart contract implements. |
| ERC-721 Non-Fungible Token Standard | A standard interface for non-fungible tokens, also known as deeds. |
| ERC-725 General data key-value store and execution | ERC 725 describes proxy smart contracts that can be controlled by multiple keys and other smart contracts. ERC 735 is an associated standard to add and remove claims to an ERC 725 identity smart contract. These identity smart contracts can describe humans, groups, objects, and machines. ERC 725 lives on the Ethereum blockchain. |
| ERC-998 Composable Non-Fungible Token | Extends a ERC-721 to own other ERC-721 and ERC-20 tokens. |
| ERC-1155 Multi Token Standard | A standard interface for contracts that manage multiple token types. A single deployed contract may include any combination of fungible tokens, non-fungible tokens or other configurations (e.g. semi-fungible tokens). |
| ERC-1271 Standard Signature Validation Method for Contracts | Standard way to verify a signature when the account is a smart contract. |
| ERC-2981 NFT Royalty Standard | A standardized way to retrieve royalty payment information for non-fungible tokens (NFTs) to enable universal support for royalty payments across all NFT marketplaces and ecosystem participants. |
| ERC-6551 Non-fungible Token Bound Accounts | An interface and registry for smart contract accounts owned by non-fungible tokens. |
EIPs
| Standard | Simple Summary |
|---|---|
| EIP-3085 Wallet Add Ethereum Chain RPC Method | An RPC method for adding Ethereum chains to wallet applications. |
LSPs
| Standard | Simple Summary |
|---|---|
| LSP-0 ERC-725 Account | This standard describes a version of an ERC725 smart contract, that represents a blockchain account. |
| LSP-1 Universal Receiver + Delegate | An entry function enabling a contract to receive arbitrary information. |
| LSP-4 Digital Asset Metadata | This standard describes a set of ERC725Y data key-value pairs that describe a digital asset. |
| LSP-6 Key Manager | This standard describes a KeyManager contract with a set of pre-defined permissions for addresses. A KeyManager contract can control an ERC725Account like account, or any other ERC725 smart contract. |
| LSP-7 Digital Asset | A standard interface for digital assets, for either fungible or non-fungible tokens. |
| LSP-8 Identifiable Digital Asset | A standard interface for identifiable digital assets, allowing for tokens to be uniquely traded and given metadata using ERC725Y. |
| LSP-9 Vault | This standard describes a version of an ERC725 smart contract, that represents a blockchain vault. |
| LSP-11 Basic Social Recovery | This standard describes a basic social recovery contract that can recover access to ERC725 contracts through a LSP6-KeyManager. |
| LSP-14 Ownable 2-Step | This standard describes an extended version of EIP173 that uses a 2-step process to transfer or renounce ownership of a contract, instead of instant execution. |
| LSP-16 Universal Factory | This standard defines a universal factory smart contract, that will allow to deploy different types of smart contracts using CREATE2 opcode after being deployed with Nick Factory in order to produce the same address on different chains. |
| LSP-20 Call Verifier | This standard introduces a mechanism for delegating the verification of a function call to another contract. |
| LSP-23 Linked Contracts Factory | This standard describes a smart contract factory that can deploy linked contracts and have an optional post-deployment execution. |
| Universal Profile + Init | A Universal Profile is an owned smart contract. Ownership means that such a contract has a separate owner. |
OpenSea
| Standard | Simple Summary |
|---|---|
| OpenSea Metadata Standard | Providing asset metadata allows applications like OpenSea to pull in rich data for digital assets and easily display them in-app. Digital assets on a given smart contract are typically represented solely by a unique identifier (e.g., the token_id in ERC721), so metadata allows these assets to have additional properties, such as a name, description, and image. |