Recommend addition to the getAssetProof response

[nickfrosty]

Problem

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. This would allow 1 less round trip to the ReadApi for not that much extra data in the original response.

Maybe even include the entire compression field data from the getAsset method? But this is a less good option.

[austbot]

This is a great suggestion!
I agree with it, want to make a pr?