SFTs on KleverChain: Should we go semi-fungible?

Klever Blockchain Feature Requests
, ,
21

@Andreas_Hennersdorf done

Transaction - a3d8c…62780 | Klever Explorer

1 Like
22

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. :raising_hands: :sweat_smile:

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:
:link: https://api.testnet.klever.org/v1.0/assets/sft/PMC-3OJB/1

grafik
grafik1881×875 15.1 KB

So my main question:
:backhand_index_pointing_right: 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)?

grafik
grafik1221×664 38.3 KB

Thanks in advance for clarifying this!
@Duka @Yuri

23

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:

grafik
grafik1328×401 16.6 KB

24

Hi @Andreas_Hennersdorf,

At the moment, it’s not yet possible to perform an updateMetadata operation for an SFT through Kleverscan. We’re currently developing this feature, and it will soon be available along with a detailed tutorial.

However, there’s already an alternative method using the operator tool if you need to update the metadata right now.
Unlike NFTs, the metadata of an SFT must be provided through the data/message field of the transaction, encoded in hexa.

if you only need to update the attributes field of the metadata, you can do it as follows:

./cmd/operator --key-file=./walletKey.pem kda trigger 8 \
	 --kdaID="WYLL-25HG" --nftID="1" --message="456c64726974636820426c617374" \
	 --node=https://node.testnet.klever.org --await --sign

Example: https://api.testnet.klever.org/v1.0/assets/sft/WYLL-25HG/1

If you need to modify both the name and attributes fields of the metadata, the message should be passed in the format <name-hex>@<attributes-hex>:

./cmd/operator --key-file=./walletKey.pem kda trigger 8 \
 --kdaID="WYLL-25HG" --nftID="2" --message="456c64726974636820426c617374@446f6c6f72" \
 --node=https://node.testnet.klever.org --await --sign

Example: https://api.testnet.klever.org/v1.0/assets/sft/WYLL-25HG/2

1 Like
26

Hey @Duka @Beroni
A few questions about SFTs. After creating our first one on mainnet, we’ve noticed a couple of minor issues.

  • It doesn’t appear to be possible to send them via Kleverscan. I flagged this on testnet as well.

  • Repro steps:

    1. Switch from Asset Trigger to Transfer—the transfer option appears

    2. Try to select an Asset ID—no SFTs show up.

    3. Click Custom Value—the field disappears entirely, and the SFT can’t be found via Select an Asset / collection.

      grafik
      grafik1122×610 31.4 KB

      grafik
      grafik1183×679 40.8 KB

      Second issue: K5 wallet visibility.
      You can add the SFT, but it doesn’t display the quantity or the asset/collection ID.

27

TY @Andreas_Hennersdorf We’ll on it…. I circle back to you soon….

1 Like
28

Thanks for fixing the transfer in Kleverscan.
Same error also for Marketplace Sell

grafik
grafik1102×827 40.3 KB

29

Yo @Andreas_Hennersdorf ,

So, at the moment, the native Marketplace KApp doesn’t support SFT transactions. This limitation isn’t due to a bug, but rather a conceptual difference: since SFTs combine both fungible and non-fungible characteristics, their trading logic differs from that of standard NFTs. The current Marketplace KApp was designed to handle purely non-fungible assets, so it doesn’t natively interpret the mixed behavior that SFTs introduce.

The good news? With the Klever Virtual Machine (KVM) now live, you now have full flexibility to build your own Smart Contract that extends the existing Marketplace KApp or even implements a fully customized version of it. This allows you to define custom trading logic for your SFTs that fits your business model perfectly.

If you decide to move in this direction, you can absolutely count on our support to guide you through the development and deployment of your custom contract.

TY again bro for your continuous support and feedbacks on the Klever Blockchain features.

Cheers

1 Like