Closed jokly closed 2 weeks ago
The hash is calculated based on the ABI, by adding traits (as explained in the repo's readme) you change your contract's ABI, so the hash changes. This is expected behavior.
Hello! Thank you for your reply.
Based on your answer, if contract NFTCollection
use contract NFTItem
I need to use build folder of NFTCollection
contract for both in wrappers:
export * from '../build/NFTCollection/tact_NFTCollection';
export * from '../build/NFTCollection/tact_NFTItem';
Is it right? I think it's not clear behavior Can you explain why does FunC code of NFTItem depends on NFTCollection code and its traits?
Description
Example project Contract structure: NFTItem -> NFTCollection
Problem
After compilation files with FunC code of NFTItem are different:
tact_NFTItem.code.fc
from NFTItem foldertact_NFTItem.code.fc
from NFTCollection folderDiff: