Oleg Gun

I mean erc721 wrapper for erc20

Please correct me if I'm wrong Context is used for transactions signed by one wallet (private key) and executed on behalf of another wallet. The most common thing I can...

I can't point to documentation because it does not exist, unfortunately( but can point to tests wyvern protocol https://github.com/wyvernprotocol/wyvern-v3/blob/master/test/5-wyvern-exchange-matching.js#L197 \eaport protocol https://github.com/ProjectOpenSea/seaport/blob/main/test/basic.spec.ts#L1308

@Amxx right and your implementation of ERC721 does https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC721/ERC721.sol#L168 so safeTransferFrom invoked by Seaport Zone will resolve _msgSender to the signer and not to Zone. the same will work if...

Thanks, I see my mistake. I thought it would work for any signed transaction executed by someone else

Hi @shypink I'm really interested in your solution because I was working with old contact and [found](https://github.com/OpenZeppelin/openzeppelin-contracts/issues/3740) out that it is impossible to expose _consecutiveMint function to mint the next...

@shypink thanks for the detailed explanation 1. that is what I tried to say it also looks like I can't do consecutive mints twice in the constructor with the current...

1 It has the same problem as your implementation, however, you check `require(balanceOf(owner) == 0)` and the current implementation does not 2 I will run both solutions and check gas...

that would not work anyway( the _owners and _balances are both private(

@scinftist Hey hey, still playing around with your PoC I want to match the interface of the original ER721Enumerable and have such safeMint function or something similar ```solidity function safeMint(address...