Taproot Assets Channels

Taproot Assets can be deposited into Lightning Network channels, where they can be transferred instantly at low fees.

While tapd is used to mint and transfer Taproot Assets on the Bitcoin blockchain, lnd is used to open channels and handle Lightning Network payments. To communicate between tapd and lnd, litd is required. For the moment, litd needs to be run in integrated mode, meaning lnd, tapd and litd are run as a single binary.

Configuration

To be able to make use of Taproot Assets on the Lightning Network, the following configuration options are needed as part of lit.conf

lnd.protocol.option-scid-alias=true
lnd.protocol.zero-conf=true
lnd.protocol.simple-taproot-chans=true
lnd.protocol.simple-taproot-overlay-chans=true
lnd.protocol.custom-message=17
lnd.accept-keysend=true

Preparation

You will need a recently minted Taproot Asset held by your tapd.

Read more: Minting Taproot Assets on the Bitcoin blockchain

You will need two separate litd nodes. They may share the same Bitcoin Core backend (using RPC polling).

Read more: Get litd

Command Line Interface

With litd integrated mode, all applications are running as part of the litd binary. We will still use the regular CLIs to interact with the applications running as part of litd. For instance, we will use lncli to interact with LND and tapcli to interact with onchain Taproot Assets.

However, when opening, closing, or maintaining Taproot Assets channels or making Taproot Assets payments, we will use litcli.

Unless you are running litd on any other network than mainnet, you will have to specify the network you are running every time you invoke litcli.

For example:

litcli --network=testnet status

In all following example commands, this detail is omitted for simplicity.

Read more: Debugging Tapd

Open channels

To open a channel, we will identify the asset that we would like to deposit into our channel. We can get the asset ids of the Taproot Assets we hold using tapcli assets list. To open the channel, we will need the asset_id and how many of these tokens we want to deposit into our channel.

Specifying a fee rate for the channel opening transaction helps getting the transaction confirmed in time. We will need to find a peer that supports Taproot Assets. Ideally you or this peer is willing to act as an edge node, meaning they are willing to swap the asset in question for satoshis on the Lightning Network.

Learn more: Edge nodes

litcli ln fundchannel --node_key 03e347d089c071c27680e26299223e80a740cf3e3fc4b4237fa219bb67121a670b --sat_per_vbyte 16 --asset_amount 1000 --asset_id 36f682ff98bcf240a1daa5287f9c030bc6808e24ff75e594c0b42ebf82b75d75

As the channel is opening, you will see the channel txid. You should be able to immediately see the channel details with lncli pendingchannels and once confirmed, with lncli listchannels:

   	{
        	"active": true,
        	"remote_pubkey": "03e347d089c071c27680e26299223e80a740cf3e3fc4b4237fa219bb67121a670b",
        	"channel_point": "3596bc22e11333b5c06ea9b4b05ced089acd545df4d1125dca8346b1b5fc64b5:0",
        	"chan_id": "3152442773369192448",
        	"capacity": "100000",
        	"local_balance": "96920",
        	"remote_balance": "0",
        	"commit_fee": "2750",
        	"commit_weight": "614",
        	"fee_per_kw": "2500",
        	"unsettled_balance": "0",
        	"total_satoshis_sent": "0",
        	"total_satoshis_received": "0",
        	"num_updates": "0",
        	"pending_htlcs": [],
        	"csv_delay": 144,
        	"private": true,
        	"initiator": true,
        	"chan_status_flags": "ChanStatusDefault",
        	"local_chan_reserve_sat": "1000",
        	"remote_chan_reserve_sat": "1062",
        	"static_remote_key": false,
        	"commitment_type": "SIMPLE_TAPROOT",
        	"lifetime": "25",
        	"uptime": "25",
        	"close_address": "",
        	"push_amount_sat": "0",
        	"thaw_height": 0,
        	"local_constraints": {
            	"csv_delay": 144,
            	"chan_reserve_sat": "1000",
            	"dust_limit_sat": "354",
            	"max_pending_amt_msat": "99000000",
            	"min_htlc_msat": "1",
            	"max_accepted_htlcs": 483
        	},
        	"remote_constraints": {
            	"csv_delay": 144,
            	"chan_reserve_sat": "1062",
            	"dust_limit_sat": "354",
            	"max_pending_amt_msat": "99000000",
            	"min_htlc_msat": "1",
            	"max_accepted_htlcs": 483
        	},
        	"alias_scids": [
            	"17592186044416000004"
        	],
        	"zero_conf": false,
        	"zero_conf_confirmed_scid": "0",
        	"peer_alias": "VelasCommerce-Testnet",
        	"peer_scid_alias": "17592186044416000150",
        	"memo": "",
        	"custom_channel_data": {
            	"assets": [
                	{
                    	"asset_utxo": {
                        	"version": 1,
                        	"asset_genesis": {
                            	"genesis_point": "7468e34998fe93c909334b307926b2f805d1780cfaabfeb9f92a0f0aabc767bb:1",
                            	"name": "beefbux0708b",
                            	"meta_hash": "1b206639244dae9875be0db3babd9c326e9ffe319f9a913c56b765c8e80b6299",
                            	"asset_id": "1d98fdb40cab6edfd23480403210d8c48a714d9f693893bb09dde025980df830"
                        	},
                        	"amount": 90000,
                        	"script_key": "0250aaeb166f4234650d84a2d8a130987aeaf6950206e0905401ee74ff3f8d18e6"
                    	},
                    	"capacity": 90000,
                    	"local_balance": 90000,
                    	"remote_balance": 0
                	}
            	]
        	}

Generate invoices

To be able to generate invoices, you must have a channel with a remote balance for the asset you are requesting. Your peer also needs to be configured for RFQ (request for quote).

Learn: How to set up RFQ and become an Edge Node

The invoice generation format follows that of LND.

litcli ln addinvoice --memo "my first taproot asset transfer" --asset_id 1d98fdb40cab6edfd23480403210d8c48a714d9f693893bb09dde025980df830 --asset_amount 10

lntb100n1pngas7zpp587tawysmkje0nn3ky924kn6uqrah3kg3r74fy0dxlld9cm3x6wgqdpjd4ujqenfwfehggr5v9c8ymm0wssxzumnv46zqarjv9h8xen9wgcqzzsxqzpurzjqwkt9dep6spnj6j675lwsnkqw29cq4l4apsjgdvaqp3utu6tcq3r6e3ctdznnjyxpsqqqqlgqqqqqqgq2qsp5gfvdzsac6nn869ldzljaruwnzkn4mgjfgef6t7hnka3urvgxjtss9qxpqysgqwsdtk928g7a5dcnw52nd5vp5u062h2puncsepj6w43yh4cxly9sk3fm8vqtykd6sc4hs0452kf6mh5dwe8knryz3sz5e5w7wh2uze2qp69s94y

Make payments

You can make the payment by passing the invoice to litcli on the sender’s node. The invoice needs to be passed together with the asset ID.

litcli ln payinvoice --pay_req lntb100n1pngas7zpp587tawysmkje0nn3ky924kn6uqrah3kg3r74fy0dxlld9cm3x6wgqdpjd4ujqenfwfehggr5v9c8ymm0wssxzumnv46zqarjv9h8xen9wgcqzzsxqzpurzjqwkt9dep6spnj6j675lwsnkqw29cq4l4apsjgdvaqp3utu6tcq3r6e3ctdznnjyxpsqqqqlgqqqqqqgq2qsp5gfvdzsac6nn869ldzljaruwnzkn4mgjfgef6t7hnka3urvgxjtss9qxpqysgqwsdtk928g7a5dcnw52nd5vp5u062h2puncsepj6w43yh4cxly9sk3fm8vqtykd6sc4hs0452kf6mh5dwe8knryz3sz5e5w7wh2uze2qp69s94y --asset_id 1d98fdb40cab6edfd23480403210d8c48a714d9f693893bb09dde025980df830

You will notice that as the payment succeeds, a small amount of satoshis also gets pushed to the remote side. Satoshis are needed to anchor the taproot asset in an HTLC. In a testing environment it may make sense to balance the bitcoin in the channel using keysend in order to be able to send and receive smoothly.

lncli sendpayment --dest 03e347d089c071c27680e26299223e80a740cf3e3fc4b4237fa219bb67121a670b --outgoing_chan_id 3152442773369192448 --amt 50000 --keysend

Taproot Assets routing

In a testing environment, try to create multihop routes that involve Taproot Assets channel.

litd (A) <-> litd (B) <-> any Lightning node implementation (C)

We can simulate an environment in which a user (A) holds Taproot Assets in a Lightning Network channel with an Edge Node (B). User (A) will now be able to pay generic Bolt11 Lightning Network invoices presented by node (C).

User (A) is also able to request assets by generating invoices that are payable by node (C), regardless of whether node (C) has knowledge of Taproot Assets.

Close channels

We can close channels using lncli as if it were a normal channel. It is preferable to close channels cooperatively, but if the peer cannot be reached, it may be necessary to unilaterally close a channel with the --force flag.

lncli closechannel --chan_point 3596bc22e11333b5c06ea9b4b05ced089acd545df4d1125dca8346b1b5fc64b5:0