Issue on docs with Path: /hedera/tutorials/token/create-and-transfer-an-nft-using-a-solidity-contract.

[NashidForbes]

Path: /hedera/tutorials/token/create-and-transfer-an-nft-using-a-solidity-contract.

Currently the java code version gives CONTRACT_REVERT_EXECUTED.
This is on JDK 17, with Hedera SDK 2.60.0 on testnet and previewnet.

Has primary code maintainer(s) actually run the latest main branch code recently on the HTS to confirm it still works?

[emiliyank]

I managed to reproduce this on localnet and testnet.
I compiled the NFTCreator Solidity contract in order to get the bytecode. To compile successfully, it requires 5 imports (other .sol files located in the hedera-smart-contracts repository). The issue is that these dependency files exist in different versions within the repository—specifically, there are copies located in a 'v2' folder and others in a standard folder without the version suffix. When I compiled using the files from the 'v2' folder, I got the error: CONTRACT_REVERT_EXECUTED. However, once I switched to the files from the non-v2 folder, the example executed successfully.

[rwalworth]

@emiliyank what would you recommend for fixing this here?

[emiliyank]

The v2 files are not production-ready and should not be used at this time. The Smart Contracts team has indicated they will be revisiting them, so the current recommendation is to continue using the following files from contracts/system-contracts/hedera-token-service: ExpiryHelper.sol, HederaTokenService.sol, IHederaTokenService.sol, and KeyHelper.sol, along with HederaResponseCodes.sol from the contracts/system-contracts directory. Then create and compile the “NFT Creator” smart contract as described in the official documentation.
The functional difference between the two versions is the contract address: address(0x16c) is the legacy Hedera Token Service precompile, while address(0x167) is the newer system contract address.

[rwalworth]

Would you be able to assist in coming up with a new example here for this tutorial?

[emiliyank]

We do not need any changes to the example code to fix the error. The Java SDK logic is correct as is. The only change required is in the compilation step before running the code. We just need to compile the NFTCreator.sol file using the standard (non-v2) dependency files to generate the correct bytecode and then use it.