However, HexToBytes converts these directly to byte array w/o reversing the order.
2115 PUSHDATA1 DE-5F-57-D4-30-D3-DE-CE-51-1C-F9-75-A8-D3-78-48-CB-9E-05-25 # as script hash: 0x25059ecb4878d3a875f91c51ceded330d4575fde
2138 PUSHDATA1 66-8E-0C-1F-9D-7B-70-A9-9D-D9-E0-6E-AD-D4-C7-84-D6-41-AF-BC # as script hash: 0xbcaf41d684c7d4ad6ee0d99da9707b9d1f0c8e66
So when the Mint operation attempts to compare the script hashes from the notifications array to the NEO/GAS
script hashes stored in the contract, they never match
From the NEP 5 template:
However, HexToBytes converts these directly to byte array w/o reversing the order.
So when the Mint operation attempts to compare the script hashes from the notifications array to the NEO/GAS script hashes stored in the contract, they never match