When building a transfer instruction for compressed NFTs, developers and sdks are required to get a valid proof via the getAssetProof method. But also the asset's data_hash and creator_hash from the getAsset method too.
The end result is that nearly every time a developer needs to build the transfer instruction, they have to make 2 RPC calls to get all the data that is needed to completely build the transfer instruction (or they have to already have some values cached elsewhere).
Solution
When fetching data via the getAssetProof method, I recommend adding the asset's current data_hash and creator_hash within the response.
Maybe even include the entire compression field data from the getAsset method?
nickfrosty
commented
1 year ago
Problem
When building a transfer instruction for compressed NFTs, developers and sdks are required to get a valid proof via the
getAssetProofmethod. But also the asset'sdata_hashandcreator_hashfrom thegetAssetmethod too.The end result is that nearly every time a developer needs to build the transfer instruction, they have to make 2 RPC calls to get all the data that is needed to completely build the transfer instruction (or they have to already have some values cached elsewhere).
Solution
When fetching data via the
getAssetProofmethod, I recommend adding the asset's currentdata_hashandcreator_hashwithin the response.Maybe even include the entire
compressionfield data from thegetAssetmethod?