Skip to content
This repository has been archived by the owner on Sep 15, 2022. It is now read-only.

NFT crowd sale using custom contract on Polygon? #213

Open
stpoa opened this issue May 20, 2022 · 4 comments
Open

NFT crowd sale using custom contract on Polygon? #213

stpoa opened this issue May 20, 2022 · 4 comments

Comments

@stpoa
Copy link

stpoa commented May 20, 2022

Hi
Is it possible to do NFT crowdsale using Polygon? Like on Rinkeby with this manual: https://docs.opensea.io/docs/2-custom-item-sale-contract

I did a crowd sale using Rinkeby and testnets.opensea.com. After deploying the NFT contract and NFT contract factory I used the NFT contract factory address for the URL and it worked fine as described in docs:

testnets.opensea.io/address/rinkeby/{factoryAddress}/0

After deploying on polygon I tried to use and it doesn't work for some reason. I get 404.

opensea.io/address/matic/{factoryAddress}/0

For deployment on Polygon I used:

PROXY_REGISTRY_OPENSEA: "0x58807baD0B376efc12F5AD86aAc70E78ed67deaE"

Example
https://opensea.io/assets/matic/0xceA562B88299188Ab31aCAedf5a9B255C5921627/0

@wg-d
Copy link

wg-d commented May 22, 2022

@stpoa
Copy link
Author

stpoa commented May 23, 2022

I know that, but I asked about a crowd sale using custom Solidity contract. @wg-d

I followed this https://docs.opensea.io/docs/2-custom-item-sale-contract and It worked on Rinkeby, but It didn't work on Matic.

@stpoa stpoa changed the title NFT crowd sale on Polygon? NFT crowd sale using custom contract on Polygon? May 23, 2022
@stpoa
Copy link
Author

stpoa commented May 23, 2022

Similar to:
#106
#149

Please help with this, this problem is reported by multiple users.

@zhenmu
Copy link

zhenmu commented Jun 30, 2022

Hi Is it possible to do NFT crowdsale using Polygon? Like on Rinkeby with this manual: https://docs.opensea.io/docs/2-custom-item-sale-contract

I did a crowd sale using Rinkeby and testnets.opensea.com. After deploying the NFT contract and NFT contract factory I used the NFT contract factory address for the URL and it worked fine as described in docs:

testnets.opensea.io/address/rinkeby/{factoryAddress}/0

After deploying on polygon I tried to use and it doesn't work for some reason. I get 404.

opensea.io/address/matic/{factoryAddress}/0

For deployment on Polygon I used:

PROXY_REGISTRY_OPENSEA: "0x58807baD0B376efc12F5AD86aAc70E78ed67deaE"

Example https://opensea.io/assets/matic/0xceA562B88299188Ab31aCAedf5a9B255C5921627/0

same problems.

Finally, I added the function:

function supportsInterface(bytes4 interfaceId) public view virtual returns (bool)

such as:

    /**
     * @dev See {IERC165-supportsInterface}.
     */
    function supportsInterface(bytes4 interfaceId) public view virtual override(ERC165, IERC165) returns (bool) {
        return
            interfaceId == type(IERC721).interfaceId ||
            interfaceId == type(IERC721Metadata).interfaceId ||
            super.supportsInterface(interfaceId);
    }

or


    function supportsInterface(bytes4 interfaceId) public view virtual returns (bool) {
        bytes4 _ERC165_ = 0x01ffc9a7;
        bytes4 _ERC721_ = 0x80ac58cd;
        bytes4 _ERC2981_ = 0x2a55205a;
        bytes4 _ERC721Metadata_ = 0x5b5e139f;
        return interfaceId == _ERC165_ 
            || interfaceId == _ERC721_
            || interfaceId == _ERC2981_
            || interfaceId == _ERC721Metadata_;
    }

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants