Fix: issue #76

[Antoninich]

It is more correct to change the description line in signum-node.

[pir8radio]

I would rather not do one off things, i hope that the devs change this description to match SRC44 so we can just decode it like we do everything else in the explorer.

Example this:

Becomes this:

[ohager]

I would rather not do one off things, i hope that the devs change this description to match SRC44 so we can just decode it like we do everything else in the explorer.

Example this:

Becomes this:

I mentioned it here... The NFT was created before SRC44... the contracts descriptor is not SRC44 compatible, but if you resolve the IPFS hash in the descriptor you get a JSON with all media data. Changing the descriptor for NFT contracts now, is much more effort than treating it in the explorer tbh. We have an entire backend and some additional tools that uses the non-SRC44 format

Here is an example of the JSON in referenced in NFT descriptor field.
https://ipfs.io/ipfs/bafkreifgan3pg344vhz3tnjq26mzfmt4cmxy5lb6y74jkxobrz4xzq54lm

from this NFT https://chain.signum.network/at/2978638295822152791

[ohager]

We are changing the NFTs description to be SRC44 compatible... I think we can close this PR.

[pir8radio]

closing, thanks @ohager