Convert the singular ERC-721 collection into ERC-1155 multi-token collection

[drewcook]

Use ERC-1155 Multi-token Collections for NFTs

User Story

As a user, I should be able to see each Arbor project as its own collection with different token IDs representing versions of that project.

Acceptance Criteria

• The PolyechoNFT.sol contract should be renamed to ArborCollection.sol
• The collection contract should implement an ERC-1155 multi-token standard
  • Should use OpenZeppelin since we are already using their contracts
• The collection should include royalty splits
• The collection should work with NFT marketplaces like OpenSea and Rarible
• Should minimize gas costs as much as possible, improving the existing contract’s usage
• The contract is deployed on all the relevant networks
• The contract address is updated on all documentation
• The contract is verified on Etherscan and other block scanners

Notes

• EIP-1155: https://eips.ethereum.org/EIPS/eip-1155
• OpenZeppelin v4 implementation: https://docs.openzeppelin.com/contracts/4.x/erc1155

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like

A clear and concise description of what you want to happen.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

[drewcook]

@noahdahlman @Harsh8196 - please fill in any details from the meeting