GITBOOK-391: change request with no subject merged in GitBook

lightning-network-tools/taproot-assets/collectibles.md

@@ -20,13 +20,13 @@ Example:
 
 ## Collections
 
-Multiple collectibles can be grouped together into a collection. Each asset has its own asset ID, while the collection itself can be identified by its group key. To create such a collection, the `--enable_emission` flag has to be set, and each subsequent collectible has to reference the first collectible by its name. Multiple collectibles can be minted in a batch.
+Multiple collectibles can be grouped together into a collection. Each asset has its own asset ID, while the collection itself can be identified by its group key. To create such a collection, the `--new_group_emission` flag has to be set, and each subsequent collectible has to set the `--grouped_asset` flag as well as reference the first collectible by its name. Multiple collectibles can be minted in a batch.
 
-`tapcli assets mint --type collectible --name member001 --meta_bytes 546170726f6f742041737365747320436c7562204d656d62657220303031 --supply 1 --enable_emission`
+`tapcli assets mint --type collectible --name member001 --meta_bytes 546170726f6f742041737365747320436c7562204d656d62657220303031 --supply 1 --new_group_emission`
 
-`tapcli assets mint --type collectible --name member002 --meta_bytes 546170726f6f742041737365747320436c7562204d656d62657220303032 --supply 1 --group_anchor member001`
+`tapcli assets mint --type collectible --name member002 --meta_bytes 546170726f6f742041737365747320436c7562204d656d62657220303032 --grouped_asset --supply 1 --group_anchor member001`
 
-`tapcli assets mint --type collectible --name member003 --meta_bytes 546170726f6f742041737365747320436c7562204d656d62657220303033 --supply 1 --group_anchor member001`
+`tapcli assets mint --type collectible --name member003 --meta_bytes 546170726f6f742041737365747320436c7562204d656d62657220303033 --grouped_asset --supply 1 --group_anchor member001`
 
 `tapcli assets mint finalize`
 

lightning-network-tools/taproot-assets/first-steps.md

@@ -8,15 +8,15 @@ description: >-
 
 ## Minting assets <a href="#docs-internal-guid-3eb3e547-7fff-da1b-7a6b-6865cc97ba7e" id="docs-internal-guid-3eb3e547-7fff-da1b-7a6b-6865cc97ba7e"></a>
 
-Use `tapcli` to begin minting your first asset. We are minting a normal, fungible asset and we'll allow ourselves to increase the supply of this asset in the future by setting the `--enable_emission` flag.
+Use `tapcli` to begin minting your first asset. We are minting a normal, fungible asset and we'll allow ourselves to increase the supply of this asset in the future by setting the `--new_grouped_asset` flag.
 
-`tapcli assets mint --type normal --name beefbux --supply 100 --meta_bytes` 66616e746173746963206d6f6e6579 `--enable_emission`
+`tapcli assets mint --type normal --name beefbux --supply 100 --meta_bytes` 66616e746173746963206d6f6e6579 `--new_grouped_asset`
 
 This will add your asset to a minting queue called a batch, which allows multiple assets to be created in a single minting transaction. This saves fees and conserves blockspace. To execute the batch and publish your mint transaction to the blockchain run:
 
 `tapcli assets mint finalize`
 
-Inspect the newly created asset(s) by calling the command
+You will be given a batch txid, which will have to be included in a block before you can spend your newly created assets. You can also inspect the newly created asset(s) by calling the command
 
 `tapcli assets list`
 
@@ -102,13 +102,13 @@ The output of this command can be explained as follows:
 
 ## Minting asset groups <a href="#docs-internal-guid-326a3acb-7fff-c694-2400-496ff7278e63" id="docs-internal-guid-326a3acb-7fff-c694-2400-496ff7278e63"></a>
 
-Assets that were minted with the flag `--enable_emission` do not have a fixed supply. A new batch of this asset can be minted later in a way that the two assets are considered of the same asset group, and therefore fungible.
+Assets that were minted with the flag `--new_grouped_asset` do not have a fixed supply. A new batch of this asset can be minted later in a way that the two assets are considered of the same asset group, and therefore fungible.
 
 **Note: At the moment it is not possible to spend two assets with different asset IDs, even if they belong to the same asset group.**
 
 To increase the supply of such an asset, we will need its `tweaked_group_key`.
 
-`tapcli assets mint --type normal --name beefbux --supply 100 --group_key 02c6ca1985ae9ef257af33bb5e3389f28e798711abcb5326d8f760fdeb90c387b5`
+`tapcli assets mint --type normal --name beefbux --supply 100 --grouped_asset --group_key 02c6ca1985ae9ef257af33bb5e3389f28e798711abcb5326d8f760fdeb90c387b5`
 
 We again have to publish the new mint transaction with:
 
@@ -153,6 +153,8 @@ Now we can check our groups with:
 
 ```
 
+To inspect your balances, run `tapcli assets balance`. To show the cumulative balance across asset groups, run `tapcli assets balance --by_group`
+
 ## Synchronizing with a universe <a href="#docs-internal-guid-c0745e5e-7fff-7933-c248-d3445ea631b1" id="docs-internal-guid-c0745e5e-7fff-7933-c248-d3445ea631b1"></a>
 
 Taproot Assets uses universes to communicate information about which assets exist and where in the blockchain they are anchored. A universe can be thought of as a virtual mempool, an explorer or a repository.

lightning-network-tools/taproot-assets/get-tapd.md

@@ -22,7 +22,7 @@ Compile Taproot Assets from source by cloning the taproot-assets repository. [Go
 
 `git clone https://github.com/lightninglabs/taproot-assets.git`\
 `cd taproot-assets`\
-`checkout v0.3.0`\
+`checkout <latest version>`\
 `make install`
 
 ## Configuration: <a href="#docs-internal-guid-8aa3849c-7fff-4b8e-530a-a563b8d9d0b8" id="docs-internal-guid-8aa3849c-7fff-4b8e-530a-a563b8d9d0b8"></a>