Add ERC: Inscription In Smart Contract

[shalom-ins]

ERC7583: A framework for inscription assets within EVM.

This EIP proposes a standardized method for enabling tokens to be traded both as fungible tokens and non-fungible tokens on the Ethereum, providing the necessary flexibility for tokens to function in both capacities. Furthermore, this standard incorporates a standard to embed inscription data within event data. This addition allows for the inclusion of immutable, extra information directly on the Ethereum.

[eip-review-bot]

File ERCS/erc-7583.md

Requires 1 more reviewers from @axic, @g11tech, @samwilsn, @xinbenlv

[JXRow]

function inscribe(bytes calldata data) dosen't include transferTo, how to transfer to user?

[shalom-ins]

function inscribe(bytes calldata data) dosen't include transferTo, how to transfer to user?

You can integrate it with the ERC721 protocol to enable transaction functionality. Since inscriptions are not solely used for transactions, this proposal does not set forth any transaction-related specifications.

[JXRow]

function inscribe(bytes calldata data) dosen't include transferTo, how to transfer to user?

You can integrate it with the ERC721 protocol to enable transaction functionality. Since inscriptions are not solely used for transactions, this proposal does not set forth any transaction-related specifications.

I kown that, so I suggest that the function inscribe(bytes calldata data) should be function inscribe(address to, bytes calldata data), inscription needs the param "address to"

[yelihui1314]

5 of my ins were stolen, it happened on (Dec-29-2023 07:14:11 AM +UTC)，There are no such transactions in the table you provided。 My Wallet address:0x03615852733ef99b2dc5e400f8b9b234b17bb1f7

TokenID:18403,15026,4266,2323,855

Transaction Hash: 0xa02e37843b8c0ea08db039131983e0dbf3fddac0e6660254d4c3b75b4c304c44 0xf8da7df506a4380fa1724c2e2effa0ea7c4e682fae4e39e51590e5364661d6c3 0xebd871f3e85ef304330e4f8debdd8ec51a8c9c4db20509e035b7d225dfeffbec 0x4c1cd2621dadc4418ab9b4180697cc5601a444353e12e65068ad9e3f17364c69 0x75548d6a5e0f765dbfc846f86174a14d4dc67e0a85f72d9c2dc828fa90d502de

[shalom-ins]

function inscribe(bytes calldata data) dosen't include transferTo, how to transfer to user?

You can integrate it with the ERC721 protocol to enable transaction functionality. Since inscriptions are not solely used for transactions, this proposal does not set forth any transaction-related specifications.

I kown that, so I suggest that the function inscribe(bytes calldata data) should be function inscribe(address to, bytes calldata data), inscription needs the param "address to"

I believe that inscription id cannot be omitted because having an id allows for very flexible operations on inscriptions using the EVM, including the owner of inscriptions.

[github-actions[bot]]

The commit 583169ed7280914abc48c756e8e931a390811684 (as a parent of 04916632c01912e29f742d1d87ba489f30466761) contains errors. Please inspect the Run Summary for details.

[github-actions[bot]]

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.

[github-actions[bot]]

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.

[github-actions[bot]]

This pull request was closed due to inactivity. If you are still pursuing it, feel free to reopen it and respond to any feedback or request a review in a comment.