-
Notifications
You must be signed in to change notification settings - Fork 11.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERC1155 feature pending tasks #2014
Conversation
* Initial ERC1155 implementation with some tests * Remove mocked isERC1155TokenReceiver * Revert reason edit nit * Remove parameters associated with isERC1155TokenReceiver call * Add tests for approvals and single transfers * Add tests for transferring to contracts * Add tests for batch transfers * Make expectEvent.inTransaction tests async * Renamed "owner" to "account" and "holder" * Document unspecified balanceOfBatch reversion on zero behavior * Ensure accounts can't set their own operator status * Specify descriptive messages for underflow errors * Bring SafeMath.add calls in line with OZ style * Explicitly prevent _burn on the zero account * Implement batch minting/burning * Refactored operator approval check into isApprovedForAll calls * Renamed ERC1155TokenReceiver to ERC1155Receiver * Added ERC1155Holder * Fix lint issues
|
FWIW, I have a very simple catch-all implementation of the metadata URI interface in KaiRo-at@859f6e7 (a second should probably follow that allows a different URI per id, the catch-all solution is for using the {id} placeholder in the URI), should this go into this PR or its own? |
@KaiRo-at Please submit in its own PR to the |
Thanks, created #2029 but tests are still missing. |
Added some minor changes to the test in the PR #2107 ( In the Also, there is a warning telling that |
* port ERC1155 to Solidity 0.6 * make ERC1155 constructor more similar to ERC721 one * also migrate mock contracts to Solidity 0.6 * mark all non-view functions as virtual
Working on the different ERC1155 PRs is becoming a bit of a mess, which I think we can simplify by merging current work into This may be entirely avoidable and our fault for not properly handling release branches, but since v3.1 is expected to include ERC1155 anyway I don't think merging now will be a problem. I created #2230 to replace this PR as the place to track progress. |
This PR tracks the tasks pending to merge
feature-erc1155
, introduced in #1803.More tasks may come out of the review.