Add ERC: Dynamic Compliant Interop Security Token #67
Conversation
EIP number change Co-authored-by: Andrew B Coathup <28278242+abcoathup@users.noreply.github.com>
category change Co-authored-by: Andrew B Coathup <28278242+abcoathup@users.noreply.github.com>
eip-review-bot
changed the title
|
There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review. |
ERCS/erc-7518.md
Outdated
| [ERC-7518](./eip-7518.md) is a proposed token standard that extends [ERC-1155](./eip-1155.md) and combines its functionality with other existing token standards, introducing unique features for interoperability, cross-chain operation, and token wrapping. The standard aims to provide a flexible and efficient solution for managing real-asset security tokens. At its core, [ERC-7518](./eip-7518.md) introduces the concept of partitions, where each `tokenId` represents a distinct partition. A partition can have its own set of rights and privileges, making it suitable for various use cases, including but not limited to semi-fungible asset management. | ||
|
|
||
| One of the significant use cases of [ERC-7518](./eip-7518.md) is semi-fungible asset management, enabling the representation of different fractional ownership units within a single token. This facilitates the fractionalization of assets, allowing investors to own smaller portions of high-value assets. However, it is essential to note that `tokenId` can represent various partitions, each serving different purposes beyond share classes. | ||
|
|
||
| [ERC-7518](./eip-7518.md) addresses the need for enhanced cross-chain interoperability and flexible compliance management in the rapidly evolving landscape of security tokens. By leveraging the [ERC-7518](./eip-7518.md) standard, security tokens can seamlessly interact with the [ERC-7518](./eip-7518.md) ecosystem, enabling trustless transfers and integration with decentralized finance (DeFi) platforms. |
There was a problem hiding this comment.
Use "this proposal" instead of the number when talking about this document. Please make this change throughout, not just here.
| [ERC-7518](./eip-7518.md) is a proposed token standard that extends [ERC-1155](./eip-1155.md) and combines its functionality with other existing token standards, introducing unique features for interoperability, cross-chain operation, and token wrapping. The standard aims to provide a flexible and efficient solution for managing real-asset security tokens. At its core, [ERC-7518](./eip-7518.md) introduces the concept of partitions, where each `tokenId` represents a distinct partition. A partition can have its own set of rights and privileges, making it suitable for various use cases, including but not limited to semi-fungible asset management. | |
| One of the significant use cases of [ERC-7518](./eip-7518.md) is semi-fungible asset management, enabling the representation of different fractional ownership units within a single token. This facilitates the fractionalization of assets, allowing investors to own smaller portions of high-value assets. However, it is essential to note that `tokenId` can represent various partitions, each serving different purposes beyond share classes. | |
| [ERC-7518](./eip-7518.md) addresses the need for enhanced cross-chain interoperability and flexible compliance management in the rapidly evolving landscape of security tokens. By leveraging the [ERC-7518](./eip-7518.md) standard, security tokens can seamlessly interact with the [ERC-7518](./eip-7518.md) ecosystem, enabling trustless transfers and integration with decentralized finance (DeFi) platforms. | |
| This proposal is a proposed token that extends [ERC-1155](./eip-1155.md) and combines its functionality with other existing token standards, introducing unique features for interoperability, cross-chain operation, and token wrapping. The standard aims to provide a flexible and efficient solution for managing real-asset security tokens. At its core, This proposal introduces the concept of partitions, where each `tokenId` represents a distinct partition. A partition can have its own set of rights and privileges, making it suitable for various use cases, including but not limited to semi-fungible asset management. | |
| One of the significant use cases of this proposal is semi-fungible asset management, enabling the representation of different fractional ownership units within a single token. This facilitates the fractionalization of assets, allowing investors to own smaller portions of high-value assets. However, it is essential to note that `tokenId` can represent various partitions, each serving different purposes beyond share classes. | |
| This proposal addresses the need for enhanced cross-chain interoperability and flexible compliance management in the rapidly evolving landscape of security tokens. By leveraging this proposal standard, security tokens can seamlessly interact with this proposal ecosystem, enabling trustless transfers and integration with decentralized finance (DeFi) platforms. |
ERCS/erc-7518.md
Outdated
| In addition to the compatibility with [ERC-1155](./eip-1155.md), [ERC-7518](./eip-7518.md) introduces unique features specifically tailored for security tokens. These features include: | ||
|
|
||
| * Enhanced cross-chain interoperability: [ERC-7518](./eip-7518.md) enables security tokens to seamlessly interact with the [ERC-7518](./eip-7518.md) ecosystem, allowing for trustless transfers and integration with DeFi platforms across different blockchain networks. | ||
| * Semi-fungible share class management: [ERC-7518](./eip-7518.md) supports the management of semi-fungible share classes, providing flexibility in the representation of ownership and fractional shares of real-world assets. | ||
| * Token wrapping: [ERC-7518](./eip-7518.md) introduces token wrapping functionality, enabling the conversion of tokens from one standard to another, further enhancing interoperability and integration with various blockchain networks. | ||
| * Flexible compliance management: [ERC-7518](./eip-7518.md) offers a comprehensive compliance management solution, including off-chain verification, custom rules, regulations, and signature validation. This ensures that security tokens adhere to the necessary regulatory requirements while maintaining a high level of flexibility. | ||
| * Hard Asset such as Commercial Tower: [ERC-7518](./eip-7518.md) can be used to tokenize a commercial tower, allowing investors to own a fraction of the asset. Each `tokenId` can represent a unique share class, such as a percentage of the entire tower or individual floors. This enables greater liquidity and accessibility to real estate investments, as smaller investors can participate in owning a portion of a large commercial property | ||
| * Soft Asset such as Funds: [ERC-7518](./eip-7518.md) can be used to tokenize funds, especially in a Fund of Funds (FoF) business model. Each sub-fund within the FoF can be tokenized, with each `tokenId` representing a unique share class. This allows investors to directly invest in specific sectors, regions, or strategies based on their preferences. The semi-fungible share class management feature of [ERC-7518](./eip-7518.md) provides the flexibility to create and manage multiple share classes with varying rights and privileges. | ||
|
|
||
| By incorporating these additional features, [ERC-7518](./eip-7518.md) addresses the growing need for enhanced cross-chain interoperability and flexible compliance management in the rapidly evolving landscape of security tokens. This makes [ERC-7518](./eip-7518.md) a powerful and versatile token standard for the security token ecosystem. |
There was a problem hiding this comment.
These points aren't exactly relevant to backwards compatibility. They are more motivating examples, and could be put in the motivation section.
|
There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review. |
You can use |
|
There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review. |
Co-authored-by: Sam Wilson <57262657+SamWilsn@users.noreply.github.com>
|
There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review. |
|
Looks like there's still a few outstanding |
|
The commit 1069da4 (as a parent of 017b2fc) contains errors. |
| function forceTransfer(address from,address to,uint256 id,uint256 amount,bytes memory data) external returns (bool); | ||
| ``` | ||
|
|
||
| * MUST bypasses normal transfer restrictions and authorization checks. |
There was a problem hiding this comment.
| * MUST bypasses normal transfer restrictions and authorization checks. | |
| * MUST bypass normal transfer restrictions and authorization checks. |
| * MUST bypasses normal transfer restrictions and authorization checks. | ||
| * MUST revert if the `from` address is not Frozen. | ||
| * MUST revert if `to` address is Frozen. | ||
| * MUST only authorized entities have the capability to call this function. |
There was a problem hiding this comment.
| * MUST only authorized entities have the capability to call this function. | |
| * MUST ensure that only authorized entities have the capability to call this function. |
| Send payouts to single address, receiver will be receiving a specific amount of tokens. | ||
|
|
||
| ```solidity | ||
| function Payout(address calldata to,uint256 calldata amount) public returns (bool) |
There was a problem hiding this comment.
| function Payout(address calldata to,uint256 calldata amount) public returns (bool) | |
| function payout(address calldata to,uint256 calldata amount) public returns (bool) |
possibly?
| type: Standards Track | ||
| category: ERC | ||
| created: 2023-09-14 | ||
| requires: 165, 1155 |
There was a problem hiding this comment.
| requires: 165, 1155 | |
| requires: 165, 1155, 3643 |
To understand the section around line 347, I think ERC-3643 is required reading.
| --- | ||
| eip: 7518 | ||
| title: Dynamic Compliant Interop Security Token | ||
| description: A security token contract utilizing semi fungible partitioning focusing on dynamic compliance and interoperability. |
There was a problem hiding this comment.
What is this token compliant with? What does it interoperate with? What is a partition? What makes it dynamic?
Your description raises a lot of questions without really describing your standard well.
Two small suggestions are: don't repeat your title as much (that'll give you more room to include useful content here), and highlight the "core" of the proposal you mention in the abstract:
| description: A security token contract utilizing semi fungible partitioning focusing on dynamic compliance and interoperability. | |
| description: Group security tokens into partitions with rights/privileges for cross-chain interoperability and compliance management |
This is only a suggestion. I don't understand all the specifics of your proposal, so do what you will here!
| Extends and combines the functionalities of existing token standards like [ERC-1155](./eip-1155.md), addressing the unique requirements of security tokens, such as cross-chain interoperability, flexible compliance management, and token wrapping. | ||
| * Enhancing Interoperability and Compliance Management: | ||
|
|
||
| The proposal introduces unique features for cross-chain operations, semi-fungible share class management, and seamless interaction with the proposal ecosystem. It also provides a comprehensive compliance model for both on-chain and off-chain verification, ensuring adherence to various regulatory requirements and jurisdictional restrictions. |
There was a problem hiding this comment.
This paragraph isn't explaining the "why" of anything. The Rationale section should explain technical choices made within the proposal.
For example, if you were writing a proposal to build a tool shed, that proposal's Rationale section could explain why you chose wooden siding over vinyl.
| * Enhanced cross-chain interoperability: [ERC-7518](./eip-7518.md) enables security tokens to seamlessly interact with the [ERC-7518](./eip-7518.md) ecosystem, allowing for trustless transfers and integration with DeFi platforms across different blockchain networks. | ||
| * Semi-fungible share class management: [ERC-7518](./eip-7518.md) supports the management of semi-fungible share classes, providing flexibility in the representation of ownership and fractional shares of real-world assets. | ||
| * Token wrapping: [ERC-7518](./eip-7518.md) introduces token wrapping functionality, enabling the conversion of tokens from one standard to another, further enhancing interoperability and integration with various blockchain networks. | ||
| * Flexible compliance management: [ERC-7518](./eip-7518.md) offers a comprehensive compliance management solution, including off-chain verification, custom rules, regulations, and signature validation. This ensures that security tokens adhere to the necessary regulatory requirements while maintaining a high level of flexibility. | ||
| * Hard Asset such as Commercial Tower: [ERC-7518](./eip-7518.md) can be used to tokenize a commercial tower, allowing investors to own a fraction of the asset. Each `tokenId` can represent a unique share class, such as a percentage of the entire tower or individual floors. This enables greater liquidity and accessibility to real estate investments, as smaller investors can participate in owning a portion of a large commercial property | ||
| * Soft Asset such as Funds: [ERC-7518](./eip-7518.md) can be used to tokenize funds, especially in a Fund of Funds (FoF) business model. Each sub-fund within the FoF can be tokenized, with each `tokenId` representing a unique share class. This allows investors to directly invest in specific sectors, regions, or strategies based on their preferences. The semi-fungible share class management feature of [ERC-7518](./eip-7518.md) provides the flexibility to create and manage multiple share classes with varying rights and privileges. |
There was a problem hiding this comment.
Could you make it more clear what these features are backwards (in)compatible with? This just looks like a list of features of this proposal.
|
There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review. |
Dynamic Compliant Interop Security Token(DyCIST) is a proposed token standard that extends ERC-1155 and combines its functionality with other existing token standards, introducing unique features for interoperability, cross-chain operation, and token wrapping.