在特定功能后，与Create2停止部署的ERC721合同称为

Question

因此，我正在研究NFT市场智能合约，并且该市场的功能之一使用户可以部署自己的收藏（这基本上是一份智能合约，可扩展ERC721规格）。为此，我正在利用Create2 Opcode。它在测试网络测试时很好地部署了（除了疯狂的巨大气体需求之外），但问题是，我只能在本合同中调用一次功能。这是扩展ERC721的合同：

pragma solidity ^0.8.0;

import '@openzeppelin/contracts/token/ERC721/extensions/ERC721URIStorage.sol';
import '@openzeppelin/contracts/token/ERC721/IERC721.sol';
import '@openzeppelin/contracts/security/ReentrancyGuard.sol';
import '@openzeppelin/contracts/utils/Counters.sol';
import './interfaces/IDeployableCollection.sol';

contract DeployableCollection is IDeployableCollection, ERC721URIStorage, ReentrancyGuard {
  using Counters for Counters.Counter;

  Counters.Counter private _tokenIds;
  address public _collectionOwner;
  bytes32 public _category;
  address payable public _paymentReceiver;
  string public _collectionURI;
  mapping(address => uint256) public lastMintedForIDs;

  constructor(
    string memory name_,
    string memory symbol_,
    address collectionOwner_,
    string memory category_,
    address paymentReceiver_,
    string memory collectionURI_
  ) ERC721(name_, symbol_) {
    _collectionOwner = collectionOwner_;
    _category = keccak256(abi.encode(category_));
    _paymentReceiver = payable(paymentReceiver_);
    _collectionURI = collectionURI_;
  }

  function mintFor(string memory _tokenURI, address to) external nonReentrant returns (uint256 _tokenId) {
    _tokenIds.increment();
    _tokenId = _tokenIds.current();
    _mint(to, _tokenId);
    _setTokenURI(_tokenId, _tokenURI);
    lastMintedForIDs[to] = _tokenId;
  }
}

这是部署合同的行：

function deployCollection(
    string memory name_,
    string memory symbol_,
    string memory category_,
    address paymentReceiver_,
    string memory _collectionURI
  ) external payable nonReentrant {
    uint256 _fee = _utilityToken != address(0) && IERC20(_utilityToken).balanceOf(_msgSender()) >= _requiredHold
      ? _collectionDeployFeeInEther.sub((uint256(_percentageDiscount).mul(_collectionDeployFeeInEther)).div(100))
      : _collectionDeployFeeInEther;
    require(msg.value >= _fee, 'FEE_TOO_LOW');
    bytes memory _byteCode = abi.encodePacked(
      type(DeployableCollection).creationCode,
      abi.encode(name_, symbol_, _msgSender(), category_, paymentReceiver_, _collectionURI)
    );
    bytes32 _salt = keccak256(abi.encode(name_, _msgSender()));
    address _collection;

    assembly {
      _collection := create2(0, add(_byteCode, 32), mload(_byteCode), _salt)
    }
    emit CollectionDeployed(_collection, _msgSender(), block.timestamp, name_, category_, symbol_);
  }

现在可以正常工作，除非我致电 mintfor 且NFT被铸造出来，合同停止了工作。即使创建了NFT，它也显示了Block Explorer上零（0）的总供应（我只能创建具有1个ID的NFT）。我也无法再次调用任何功能，因为它会引起例外（其原因未知）。这是工厂合同中进行实际铸造的行：

  function mintNFT(
    address collection,
    string memory tokenURI_,
    address _for
  ) external payable nonReentrant returns (bool) {
    uint256 _fee = _utilityToken != address(0) && IERC20(_utilityToken).balanceOf(_msgSender()) >= _requiredHold
      ? _mintFeeInEther.sub((uint256(_percentageDiscount).mul(_mintFeeInEther)).div(100))
      : _mintFeeInEther;

    require(msg.value >= _fee, 'FEE_TOO_LOW');

    address _paymentReceiver = IDeployableCollection(collection)._paymentReceiver();
    uint256 _feeForOwner = (uint256(_percentageForCollectionOwners).mul(_fee)).div(100);

    _safeMintFor(collection, tokenURI_, _for);
    _safeTransferETH(_paymentReceiver, _feeForOwner);

    uint256 _tokenId = IDeployableCollection(collection).lastMintedForIDs(_msgSender());
    emit Mint(collection, _tokenId, block.timestamp, tokenURI_, _msgSender());
    return true;
  }

我猜想使用 1 运行时的优化在部署时使用Create2应用（如果这很愚蠢，请原谅我），但我也认为这不太可能，因为我也在使用Nodejs后端观看智能合同上的事件，当事件数据传播到我的后端应用程序时，我可以调用'_collectionuri（）'调用 mintfor 之前。我很困惑！请帮忙！

这是探险家的合同信息的链接：