SFTs on KleverChain: Should we go semi-fungible?

[Duka]

@Andreas_Hennersdorf done

Transaction - a3d8c…62780 | Klever Explorer

[Andreas_Hennersdorf]

Thanks again for the test KLV!
Quick feedback and a few deeper questions.

Creating SFTs works perfectly, as does minting new collections (nonces) or minting within an existing nonce.
I was also able to successfully add the main image and no issues there.

However, I ran into a problem when trying to add metadata for individual nonces.
I attempted to handle it the same way as with NFTs by providing metadata URIs, but the API doesn’t seem to recognize them:
https://api.testnet.klever.org/v1.0/assets/sft/PMC-3OJB/1

So my main question:
Is it no longer possible to self-host SFT metadata and link it via URI (so KleverChain can fetch and display it per nonce, as it currently does with NFTs on mainnet)?

I noticed that it’s now possible to edit the metadata of individual nonces directly in KleverScan.
Is that the intended approach going forward?

Also, it requests an NFT holder address during that process.
Am I right in assuming that it would update all 100,000 items in the nonce when doing so (as seen in the screenshot)?

Thanks in advance for clarifying this!
@Duka @Yuri

[Andreas_Hennersdorf]

By the way, it always seems to want to update the last nonce when updating URIs.
It is not possible to make changes in Kleverscan;
I thought it would enter it as a URI for the entire SFT.
But neither is the case!
Hash:

KleverChain