Home Bitcoin Do a number of issuances of a taproot asset, utilizing the identical group_key, depend conceptually as the identical asset, even when they’ve totally different asset_ids?

Do a number of issuances of a taproot asset, utilizing the identical group_key, depend conceptually as the identical asset, even when they’ve totally different asset_ids?

0
Do a number of issuances of a taproot asset, utilizing the identical group_key, depend conceptually as the identical asset, even when they’ve totally different asset_ids?

[ad_1]

I’m attempting to know the minting of Taproot Belongings.

Particularly I wish to perceive tips on how to mint extra of an present asset, i.e. add to the prevailing provide of that asset.

I’m experimenting with Taproot Belongings utilizing tapd model 0.3.2-alpha:

$ tapcli --version
tapcli model 0.3.2-alpha.rc1 commit=v0.3.2-beta.rc1-2-g3757262

I’ve managed to create belongings on Testnet utilizing the MintAsset API endpoint:

https://lightning.engineering/api-docs/api/taproot-assets/mint/mint-asset/

For instance, I can ship the next REST message to create an asset:

{
    "short_response": false,
    "asset": {
        "asset_type": 0, // Regular kind
        "asset_version": 1, // ASSET_VERSION_V1
        "identify": "My asset",
        "quantity": 1000,
        "asset_meta": {
            "knowledge": "123456", // Metadata related to the asset
            "kind": 0 // META_TYPE_OPAQUE
        },
        "new_grouped_asset": true
    }
}

This may efficiently enqueue the minting into the subsequent batch, and as soon as the batch is dedicated, 1000 models of the asset are created, with an asset_id and a group_key. As an instance the group_key was 0123456789ABCDEF.

Suppose I would like now to mint 500 extra models of the identical asset. If I ship the next to the MintAsset API:

{
    "short_response": false,
    "asset": {
        "asset_type": 0, // regular
        "asset_version": 1, // ASSET_VERSION_V1
        "identify": "My asset",
        "quantity": 500,
        "asset_meta": {
            "knowledge": "123456", // Metadata related to the asset
            "kind": 0 // META_TYPE_OPAQUE
        },
        "grouped_asset": true,
        "group_key": "0123456789ABCDEF", // the hypothetical group_key hex
    }
}

Then it will mint 500 models of a NEW asset_id, however utilizing the identical group_key.

I can now get the steadiness of the group (1500) with:

tapcli belongings steadiness --by_group --group_key 0123456789ABCDEF

Or I can get the steadiness ensuing from every issuance (1000 or 500) with

tapcli belongings steadiness --asset_id ABCDEF0123456789

And now my query:

  • Ought to I consider these two belongings (which have totally different asset_ids however the identical group_key), as one asset conceptually, as a result of they’re in the identical group now?
  • Or is there one other solution to subject extra of the identical asset, in order that a number of issuances have the identical asset_id?

I hope my query is sensible. Please let me know if I’ve misunderstood one thing, or if my query isn’t clear.

[ad_2]

LEAVE A REPLY

Please enter your comment!
Please enter your name here