You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: lightning-network-tools/taproot-assets/first-steps.md
+33-85Lines changed: 33 additions & 85 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ This will add your asset to a minting queue called a batch, which allows multipl
32
32
33
33
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
34
34
35
-
`tapcli assets list --show_unconfirmed_mints` 
35
+
`tapcli assets list --show_unconfirmed_mints`
36
36
37
37
```json
38
38
{
@@ -181,30 +181,44 @@ Upon successful sync, information about existing assets should be retrieved, alo
As soon as your minted assets have one confirmation on the blockchain, you are able to send them. To send assets, you will need the recipient’s Taproot Assets address. This Taproot Assets address is specific to an asset and amount, so to generate an address, the recipient needs to know an asset’s `asset_id`, as well as be synced to the issuer’s universe. Taproot Assets address reuse should be avoided.
184
+
As soon as your minted assets have one confirmation on the blockchain, you are able to transfer them. You will first need the recipient’s Taproot Assets address. This address can either be interactive or non-interactive.
185
185
186
-
When generating a Taproot Assets address, the receiver will create their expected Merkle trees, and tweak a Taproot key with it. The resulting key is converted to a Taproot address, where the receiver waits for an incoming transaction.
To generate a Taproot Assets address requesting 21 beefbux, use the following command from the tapd instance of the receiver:
188
+
In situations where the asset ID is not known, for instance grouped assets, when the requested amount is flexible or a Taproot Assets address is meant to be reusable, interactive Taproot Assets addresses are preferable. The sender and recipient have to be both online to negotiate the transaction, although the final transaction may be submitted to the blockchain only at a later point.
189
+
190
+
To generate such an address, only the group key is required.
191
+
192
+
`tapcli addrs new --group_key 02875ce409b587a6656357639d099ad9eb08396d0dfea8930a45e742c81d6fc782`
193
+
194
+
#### Non-interactive Taproot Assets addresses
195
+
196
+
Non-interactive Taproot Assets addresses arespecific to an asset and amount, so to generate an address, the recipient needs to know an asset’s asset\_id, as well as be synced to the issuer’s universe. Reuse of non-interactive Taproot Assets address reuse should be avoided. This type of transfer is ideal when the asset ID is known and the amount is fixed. The recipient does not need to be online during the transfer.
189
197
190
198
`tapcli addrs new --asset_id b9ae86f52dcbdee7ea78e86b26320819c44c2f4f8a91b9c055ca0af4c4d1b22b --amt 21`
191
199
200
+
## Sending an asset <a href="#docs-internal-guid-5d8fd7ee-7fff-475c-a392-4855bf9afc85" id="docs-internal-guid-5d8fd7ee-7fff-475c-a392-4855bf9afc85"></a>
To send the asset in the interactive flow, the sender can then use the tapcli assets send command, using the generated taproot asset address and the amount, separated by a colon. For this type of send, address reuse is acceptable or even encouraged, but both the sender and the receiver are expected to be online simultaneously.
## Sending an asset <a href="#docs-internal-guid-5d8fd7ee-7fff-475c-a392-4855bf9afc85" id="docs-internal-guid-5d8fd7ee-7fff-475c-a392-4855bf9afc85"></a>
227
-
228
-
To send the asset, run the command below from the tapd instance of the sender. This will generate the appropriate Merkle trees for the recipient and their change outputs, sign the Taproot Assets transaction with their internal Taproot Assets key and publish the Bitcoin transaction. Note that you cannot send unconfirmed assets.
240
+
To send the asset to a non-interactive Taproot Asset address, run the command below from the tapd instance of the sender. This will generate the appropriate Merkle trees for the recipient and their change outputs, sign the Taproot Assets transaction with their internal Taproot Assets key and publish the Bitcoin transaction. Note that you cannot send unconfirmed assets.
You will notice the testnet3 transaction id (`bd311ca4dbd68c6717ed4656efe7beb9ff843abe50bf58aaf3b25325c0f098aa`) has two inputs. One input is the newly minted asset (easily identifiable by its 1000 sat amount), while the other is from LND’s internal wallet. This second input is used to pay the onchain fees. The output from `tapcli` as seen above will only show the one input and two outputs that hold the Taproot Assets.
295
-
296
-
There are three outputs. Two outputs of 1000 satoshis each and the change output of LND’s internal wallet. The two 1000 satoshi inputs anchor the proofs of the sender and receiver. Even when the sender spends all of their assets, such an output is still created to carry proof of the transfer.
244
+
You’ll also be able to inspect this address again anytime with the command `tapcli addrs query`
297
245
298
246
Once the transaction is confirmed on the Bitcoin Blockchain the sender will attempt to make the proofs available to the recipient via an [end-to-end encrypted mailbox](../lightning-terminal/lightning-node-connect.md), similar to Lightning Node Connect (LNC).
0 commit comments