Lightning Terminal v0.13.6-alpha

This release of Lightning Terminal (LiT) includes a hotfix that updates application version of LiT, which was unchanged in v0.13.5-alpha.

We'll be continuously working to improve the user experience based on feedback from the community.

Installation and configuration instructions can be found in the README.

This release packages LND v0.18.3-beta, Taproot Assets Daemon v0.4.1-alpha, Loop v0.28.8-beta, Pool v0.6.5-beta and Faraday v0.2.13-alpha.

• IMPORTANT NOTE: To avoid loss of funds, it's imperative that you read the Operational Safety Guidelines before before using tapd on mainnet!

• The Taproot Assets daemon is still in alpha state, which means there can still be bugs and not all desired data safety and backup mechanisms have been implemented yet. Releasing on mainnet mainly signals that there will be no breaking changes in the future and that assets minted with v0.3.0+ will be compatible with later versions.

Important note for Umbrel/Lightning Terminal users

DO NOT UNDER ANY CIRCUMSTANCE uninstall (or re-install) the "Lightning Terminal" app without first making a manual backup of all local tapd data, if you are using Taproot Assets as part of the "Lightning Terminal" app with Umbrel -- or any comparable node-in-a-box solution. Uninstalling Umbrel apps deletes application data. This Taproot Assets application data encumbers Taproot Assets AND bitcoin funds. Receiving and sending tapd assets updates the daemon's funds-custody material. Merely having the lnd seed phrase is NOT enough to restore assets minted or received. WITHOUT BACKUP BEFORE DELETION, FUNDS ARE DESTROYED.

lnd in remote mode (lnd-mode=remote)

NOTE that the minimum version of lnd that can be used in --lnd-mode=remote is v0.17.1-beta.

Required changes when running in lnd remote mode

When connecting to an existing lnd node, that node must enable the RPC middleware interceptor feature. You can enable that by specifying the --rpcmiddleware.enable command line flag or by adding rpcmiddleware.enable=true to your lnd.conf file. See the remote configuration docs for more information.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import ViktorTigerstrom's key from the ubuntu key server:

gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 187F6ADD93AE3B0CF335AA6AB984570980684DCC

Once you have his PGP key you can verify the release (assuming manifest-v0.13.6-alpha.sig and manifest-v0.13.6-alpha.txt are in the current directory) with:

gpg --verify manifest-v0.13.6-alpha.sig manifest-v0.13.6-alpha.txt

You should see the following if the verification was successful:

gpg: Signature made Mon Oct 28 12:48:02 2024 CET
gpg:                using EDDSA key 187F6ADD93AE3B0CF335AA6AB984570980684DCC
gpg: Good signature from "Viktor Tigerström <vtigerstrom@gmail.com>

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

cat manifest-v0.13.6-alpha.txt

One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.13.6-alpha

Verifying the Release Timestamp

We have also started to timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-v0.13.6-alpha.sig.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-v0.13.6-alpha.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Release Notes:

https://github.com/lightninglabs/lightning-terminal/blob/master/docs/release-notes/release-notes-0.13.6.md

Lightning Terminal v0.13.5-alpha

This release of Lightning Terminal (LiT) includes updates to the integrated version Loop (v0.28.8-beta). We also introduce changes in this release, which ensures that all future releases will be fully reproducible on all environments.

We'll be continuously working to improve the user experience based on feedback from the community.

Installation and configuration instructions can be found in the README.

This release packages LND v0.18.3-beta, Taproot Assets Daemon v0.4.1-alpha, Loop v0.28.8-beta, Pool v0.6.5-beta and Faraday v0.2.13-alpha.

• IMPORTANT NOTE: To avoid loss of funds, it's imperative that you read the Operational Safety Guidelines before before using tapd on mainnet!

• The Taproot Assets daemon is still in alpha state, which means there can still be bugs and not all desired data safety and backup mechanisms have been implemented yet. Releasing on mainnet mainly signals that there will be no breaking changes in the future and that assets minted with v0.3.0+ will be compatible with later versions.

Important note for Umbrel/Lightning Terminal users

DO NOT UNDER ANY CIRCUMSTANCE uninstall (or re-install) the "Lightning Terminal" app without first making a manual backup of all local tapd data, if you are using Taproot Assets as part of the "Lightning Terminal" app with Umbrel -- or any comparable node-in-a-box solution. Uninstalling Umbrel apps deletes application data. This Taproot Assets application data encumbers Taproot Assets AND bitcoin funds. Receiving and sending tapd assets updates the daemon's funds-custody material. Merely having the lnd seed phrase is NOT enough to restore assets minted or received. WITHOUT BACKUP BEFORE DELETION, FUNDS ARE DESTROYED.

lnd in remote mode (lnd-mode=remote)

NOTE that the minimum version of lnd that can be used in --lnd-mode=remote is v0.17.1-beta.

Required changes when running in lnd remote mode

When connecting to an existing lnd node, that node must enable the RPC middleware interceptor feature. You can enable that by specifying the --rpcmiddleware.enable command line flag or by adding rpcmiddleware.enable=true to your lnd.conf file. See the remote configuration docs for more information.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import ViktorTigerstrom's key from the ubuntu key server:

gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 187F6ADD93AE3B0CF335AA6AB984570980684DCC

Once you have his PGP key you can verify the release (assuming manifest-v0.13.5-alpha.sig and manifest-v0.13.5-alpha.txt are in the current directory) with:

gpg --verify manifest-v0.13.5-alpha.sig manifest-v0.13.5-alpha.txt

You should see the following if the verification was successful:

gpg: Signature made Fri Oct 25 20:50:17 2024 CEST
gpg:                using EDDSA key 187F6ADD93AE3B0CF335AA6AB984570980684DCC
gpg: Good signature from "Viktor Tigerström <vtigerstrom@gmail.com>"

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

cat manifest-v0.13.5-alpha.txt

One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.13.5-alpha

Verifying the Release Timestamp

We have also started to timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-v0.13.5-alpha.sig.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-v0.13.5-alpha.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Release Notes:

https://github.com/lightninglabs/lightning-terminal/blob/master/docs/release-notes/release-notes-0.13.5.md

Lightning Terminal v0.13.995-experimental

litd v0.13.995-experimental includes the latest tapd features an bug fixes as well as litd upgrades.

Release Notes

The Lightning Terminal (LiT) experimental release is the alpha-preview build that brings Taproot Assets to the Lightning Network, with support for Taproot Asset Channels.

Please note that Taproot Asset Channel functionality is only supported when litd runs with both lnd and tapd in integrated mode (--lnd-mode=integrated and --taproot-assets-mode=integrated).

General installation and configuration instructions can be found in the README.

Key Updates

1. Clarify Asset Balance Reporting: ListBalances now supports the include_leased flag, which will include leased asset balances in balance queries.
2. Tap Channel Liquidity Fixes: Fixed issues with tap channel liquidity calculations, including sending very small or very big asset amounts.
3. RFQ Price-acceptance Tolerances: Added AcceptPriceDeviationPpm configuration.
4. RFQ Quote Accept Message Parsing: Improved RFQ quote accept message parsing by looking up the associated quote request message.
5. Aux Signer Signal Handling: Improved aux signer signal handling to prevent quit signals from being missed.
6. Coin Select Type: Added a new CoinSelectType enum to FundVirtualPsbt to specify script key type.
7. Dust Checks for Allocations: Added dust checks for allocations in tap channels.

Performance and Stability Improvements

• Parallel Proof Delivery
• Error Handling in parallel processing
• Server Logging Cleanup: log calls moved from info to trace and merged log messages.

Important Notes

• This release packages a staging/testing branch of LND, Taproot Assets Daemon, Loop, Pool, and Faraday.

• ⚠️**IMPORTANT NOTE: To avoid loss of funds, please read the Operational Safety Guidelines before using tapd on mainnet!⚠️

• The Taproot Assets daemon is still in alpha state, which means there can still be bugs and not all desired data safety and backup mechanisms have been implemented yet. Releasing on mainnet mainly signals that there will be no breaking changes in the future and that assets minted with v0.3.0+ will be compatible with later versions.

What's Changed

• Updated to latest tapd version to v0.13.995.
• Fixed bugs related to TAP channel liquidity..
• Added custom channels liquidity edge cases test.
• [custom channels]: plumb payinvoice CLI arg by @jharveyb in #838

New Contributors

• @jharveyb made their first contribution.

Full Changelog: v0.13.994-experimental...v0.13.995-experimental

Lightning Terminal v0.13.4-alpha

This release of Lightning Terminal (LiT) includes updates to the integrated versions of LND (v0.18.3-beta) and Loop (v0.28.7-beta).

We'll be continuously working to improve the user experience based on feedback from the community.

Installation and configuration instructions can be found in the README.

This release packages LND v0.18.3-beta, Taproot Assets Daemon v0.4.1-alpha, Loop v0.28.7-beta, Pool v0.6.5-beta and Faraday v0.2.13-alpha.

• IMPORTANT NOTE: To avoid loss of funds, it's imperative that you read the Operational Safety Guidelines before before using tapd on mainnet!

• The Taproot Assets daemon is still in alpha state, which means there can still be bugs and not all desired data safety and backup mechanisms have been implemented yet. Releasing on mainnet mainly signals that there will be no breaking changes in the future and that assets minted with v0.3.0+ will be compatible with later versions.

Important note for Umbrel/Lightning Terminal users

DO NOT UNDER ANY CIRCUMSTANCE uninstall (or re-install) the "Lightning Terminal" app without first making a manual backup of all local tapd data, if you are using Taproot Assets as part of the "Lightning Terminal" app with Umbrel -- or any comparable node-in-a-box solution. Uninstalling Umbrel apps deletes application data. This Taproot Assets application data encumbers Taproot Assets AND bitcoin funds. Receiving and sending tapd assets updates the daemon's funds-custody material. Merely having the lnd seed phrase is NOT enough to restore assets minted or received. WITHOUT BACKUP BEFORE DELETION, FUNDS ARE DESTROYED.

lnd in remote mode (lnd-mode=remote)

NOTE that the minimum version of lnd that can be used in --lnd-mode=remote is v0.17.1-beta.

Required changes when running in lnd remote mode

When connecting to an existing lnd node, that node must enable the RPC middleware interceptor feature. You can enable that by specifying the --rpcmiddleware.enable command line flag or by adding rpcmiddleware.enable=true to your lnd.conf file. See the remote configuration docs for more information.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import ViktorTigerstrom's key from the ubuntu key server:

gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 187F6ADD93AE3B0CF335AA6AB984570980684DCC

Once you have his PGP key you can verify the release (assuming manifest-v0.13.4-alpha.sig and manifest-v0.13.4-alpha.txt are in the current directory) with:

gpg --verify manifest-v0.13.4-alpha.sig manifest-v0.13.4-alpha.txt

You should see the following if the verification was successful:

gpg: Signature made Mon Sep 16 16:59:51 2024 +07
gpg:                using EDDSA key 187F6ADD93AE3B0CF335AA6AB984570980684DCC
gpg: Good signature from "Viktor Tigerström <vtigerstrom@gmail.com>"

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

cat manifest-v0.13.4-alpha.txt

One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.13.4-alpha

Verifying the Release Timestamp

We have also started to timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-v0.13.4-alpha.sig.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-v0.13.4-alpha.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Release Notes:

https://github.com/lightninglabs/lightning-terminal/blob/master/docs/release-notes/release-notes-0.13.4.md

Lightning Terminal v0.13.994-experimental

This version includes the latest bugfixes in tapd as well as new convenience RPCs for easier interaction with Taproot Asset Channels. See lightninglabs/taproot-assets#1048 for more information on the new tapchannelrpc.AddInvoice and tapchannelrpc.SendPayment RPCs.

Release Notes

This release of Lightning Terminal (LiT) is the first, experimental alpha preview build that brings Taproot Assets to the Lightning Network, with support for Taproot Asset Channels.

We'll be continuously working to improve the user experience based on feedback from the community.

Please note that Taproot Asset Channel functionality is only supported when litd runs with both lnd and tapd in integrated mode (--lnd-mode=integrated and --taproot-assets-mode=integrated).

General installation and configuration instructions can be found in the README.

Guides for minting assets and setting up Taproot Asset Channels in a test environment can be found here:

• First Steps: Prepare and mint assets
• Taproot Asset Channels
• RFQ

This release packages a staging/testing branch of LND v0.18.0-beta, Taproot Assets Daemon v0.4.1, Loop v0.28.5-beta, Pool v0.6.5-beta and Faraday v0.2.13-alpha.

• IMPORTANT NOTE: To avoid loss of funds, it's imperative that you read the Operational Safety Guidelines before before using tapd on mainnet!

• The Taproot Assets daemon is still in alpha state, which means there can still be bugs and not all desired data safety and backup mechanisms have been implemented yet. Releasing on mainnet mainly signals that there will be no breaking changes in the future and that assets minted with v0.3.0+ will be compatible with later versions.

Breaking changes

The configuration value (taproot-assets.universe.public-access) and command line flag (--taproot-assets.universe.public-access) now needs a value and is no longer a boolean. The value now controls whether the node's universe database can be accessed over RPC and either read (value r) or written to (value w) or both (value rw).
So existing nodes with the configuration file value taproot-assets.universe.public-access=true need to change the value to taproot-assets.universe.public-access=rw. Users specifying the command line flag --taproot-assets.universe.public-access just need to append a value, for example --taproot-assets.universe.public-access=rw.

Important note for Umbrel/Lightning Terminal users

DO NOT UNDER ANY CIRCUMSTANCE uninstall (or re-install) the "Lightning Terminal" app without first making a manual backup of all local tapd data, if you are using Taproot Assets as part of the "Lightning Terminal" app with Umbrel -- or any comparable node-in-a-box solution. Uninstalling Umbrel apps deletes application data. This Taproot Assets application data encumbers Taproot Assets AND bitcoin funds. Receiving and sending tapd assets updates the daemon's funds-custody material. Merely having the lnd seed phrase is NOT enough to restore assets minted or received. WITHOUT BACKUP BEFORE DELETION, FUNDS ARE DESTROYED.

lnd in remote mode (lnd-mode=remote)

NOTE that the minimum version of lnd that can be used in --lnd-mode=remote is v0.17.0-beta.

Required changes when running in lnd remote mode

When connecting to an existing lnd node, that node must enable the RPC middleware interceptor feature. You can enable that by specifying the --rpcmiddleware.enable command line flag or by adding rpcmiddleware.enable=true to your lnd.conf file. See the remote configuration docs for more information.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import guggero's key from the ubuntu key server:

gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys F4FC70F07310028424EFC20A8E4256593F177720

Once you have her PGP key you can verify the release (assuming manifest-v0.13.994-experimental.sig and manifest-v0.13.994-experimental.txt are in the current directory) with:

gpg --verify manifest-v0.13.994-experimental.sig manifest-v0.13.994-experimental.txt

You should see the following if the verification was successful:

gpg: Signature made Thu Jun  6 15:36:23 2024 EDT
gpg:                using RSA key F4FC70F07310028424EFC20A8E4256593F177720
gpg: Good signature from "Oliver Gugger <gugger@gmail.com>" [ultimate]

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

cat manifest-v0.13.994-experimental.txt

One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.13.994-experimental

Verifying the Release Timestamp

We have also started to timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-v0.13.994-experimental.sig.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-v0.13.994-experimental.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Changelog (auto generated)

What's Changed

• itest: spend assets after sweeping from force close by @guggero in #825

Full Changelog: v0.13.993-experimental...v0.13.994-experimental

Lightning Terminal v0.13.993-experimental

This version includes the latest bugfixes in tapd as well as new convenience RPCs for easier interaction with Taproot Asset Channels. See lightninglabs/taproot-assets#1048 for more information on the new tapchannelrpc.AddInvoice and tapchannelrpc.SendPayment RPCs.

Release Notes

This release of Lightning Terminal (LiT) is the first, experimental alpha preview build that brings Taproot Assets to the Lightning Network, with support for Taproot Asset Channels.

We'll be continuously working to improve the user experience based on feedback from the community.

Please note that Taproot Asset Channel functionality is only supported when litd runs with both lnd and tapd in integrated mode (--lnd-mode=integrated and --taproot-assets-mode=integrated).

General installation and configuration instructions can be found in the README.

Guides for minting assets and setting up Taproot Asset Channels in a test environment can be found here:

• First Steps: Prepare and mint assets
• Taproot Asset Channels
• RFQ

This release packages a staging/testing branch of LND v0.18.0-beta, Taproot Assets Daemon v0.4.1, Loop v0.28.5-beta, Pool v0.6.5-beta and Faraday v0.2.13-alpha.

• IMPORTANT NOTE: To avoid loss of funds, it's imperative that you read the Operational Safety Guidelines before before using tapd on mainnet!

• The Taproot Assets daemon is still in alpha state, which means there can still be bugs and not all desired data safety and backup mechanisms have been implemented yet. Releasing on mainnet mainly signals that there will be no breaking changes in the future and that assets minted with v0.3.0+ will be compatible with later versions.

Breaking changes

The configuration value (taproot-assets.universe.public-access) and command line flag (--taproot-assets.universe.public-access) now needs a value and is no longer a boolean. The value now controls whether the node's universe database can be accessed over RPC and either read (value r) or written to (value w) or both (value rw).
So existing nodes with the configuration file value taproot-assets.universe.public-access=true need to change the value to taproot-assets.universe.public-access=rw. Users specifying the command line flag --taproot-assets.universe.public-access just need to append a value, for example --taproot-assets.universe.public-access=rw.

Important note for Umbrel/Lightning Terminal users

DO NOT UNDER ANY CIRCUMSTANCE uninstall (or re-install) the "Lightning Terminal" app without first making a manual backup of all local tapd data, if you are using Taproot Assets as part of the "Lightning Terminal" app with Umbrel -- or any comparable node-in-a-box solution. Uninstalling Umbrel apps deletes application data. This Taproot Assets application data encumbers Taproot Assets AND bitcoin funds. Receiving and sending tapd assets updates the daemon's funds-custody material. Merely having the lnd seed phrase is NOT enough to restore assets minted or received. WITHOUT BACKUP BEFORE DELETION, FUNDS ARE DESTROYED.

lnd in remote mode (lnd-mode=remote)

NOTE that the minimum version of lnd that can be used in --lnd-mode=remote is v0.17.0-beta.

Required changes when running in lnd remote mode

When connecting to an existing lnd node, that node must enable the RPC middleware interceptor feature. You can enable that by specifying the --rpcmiddleware.enable command line flag or by adding rpcmiddleware.enable=true to your lnd.conf file. See the remote configuration docs for more information.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import guggero's key from the ubuntu key server:

gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys F4FC70F07310028424EFC20A8E4256593F177720

Once you have her PGP key you can verify the release (assuming manifest-v0.13.993-experimental.sig and manifest-v0.13.993-experimental.txt are in the current directory) with:

gpg --verify manifest-v0.13.993-experimental.sig manifest-v0.13.993-experimental.txt

You should see the following if the verification was successful:

gpg: Signature made Thu Jun  6 15:36:23 2024 EDT
gpg:                using RSA key F4FC70F07310028424EFC20A8E4256593F177720
gpg: Good signature from "Oliver Gugger <gugger@gmail.com>" [ultimate]

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

cat manifest-v0.13.993-experimental.txt

One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.13.993-experimental

Verifying the Release Timestamp

We have also started to timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-v0.13.993-experimental.sig.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-v0.13.993-experimental.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Changelog (auto generated)

What's Changed

• litclient: add taprpc packages to Registrations by @jamaljsr in #816
• [custom channels]: bump taproot assets dependency, add missing CLI flag by @guggero in #817
• [custom channels]: bump to latest version of tapd, set version to v0.13.993-experimental by @guggero in #819

Full Changelog: v0.13.992-experimental...v0.13.993-experimental

Lightning Terminal v0.13.992-experimental

This version includes the latest bugfixes in tapd as well as new convenience RPCs for easier interaction with Taproot Asset Channels. See lightninglabs/taproot-assets#1048 for more information on the new tapchannelrpc.AddInvoice and tapchannelrpc.SendPayment RPCs .

Release Notes

This release of Lightning Terminal (LiT) is the first, experimental alpha preview build that brings Taproot Assets to the Lightning Network, with support for Taproot Asset Channels.

We'll be continuously working to improve the user experience based on feedback from the community.

Please note that Taproot Asset Channel functionality is only supported when litd runs with both lnd and tapd in integrated mode (--lnd-mode=integrated and --taproot-assets-mode=integrated).

General installation and configuration instructions can be found in the README.

Guides for minting assets and setting up Taproot Asset Channels in a test environment can be found here:

• First Steps: Prepare and mint assets
• Taproot Asset Channels
• RFQ

This release packages a staging/testing branch of LND v0.18.0-beta, Taproot Assets Daemon v0.4.1, Loop v0.28.5-beta, Pool v0.6.5-beta and Faraday v0.2.13-alpha.

• IMPORTANT NOTE: To avoid loss of funds, it's imperative that you read the Operational Safety Guidelines before before using tapd on mainnet!

• The Taproot Assets daemon is still in alpha state, which means there can still be bugs and not all desired data safety and backup mechanisms have been implemented yet. Releasing on mainnet mainly signals that there will be no breaking changes in the future and that assets minted with v0.3.0+ will be compatible with later versions.

Breaking changes

The configuration value (taproot-assets.universe.public-access) and command line flag (--taproot-assets.universe.public-access) now needs a value and is no longer a boolean. The value now controls whether the node's universe database can be accessed over RPC and either read (value r) or written to (value w) or both (value rw).
So existing nodes with the configuration file value taproot-assets.universe.public-access=true need to change the value to taproot-assets.universe.public-access=rw. Users specifying the command line flag --taproot-assets.universe.public-access just need to append a value, for example --taproot-assets.universe.public-access=rw.

Important note for Umbrel/Lightning Terminal users

DO NOT UNDER ANY CIRCUMSTANCE uninstall (or re-install) the "Lightning Terminal" app without first making a manual backup of all local tapd data, if you are using Taproot Assets as part of the "Lightning Terminal" app with Umbrel -- or any comparable node-in-a-box solution. Uninstalling Umbrel apps deletes application data. This Taproot Assets application data encumbers Taproot Assets AND bitcoin funds. Receiving and sending tapd assets updates the daemon's funds-custody material. Merely having the lnd seed phrase is NOT enough to restore assets minted or received. WITHOUT BACKUP BEFORE DELETION, FUNDS ARE DESTROYED.

lnd in remote mode (lnd-mode=remote)

NOTE that the minimum version of lnd that can be used in --lnd-mode=remote is v0.17.0-beta.

Required changes when running in lnd remote mode

When connecting to an existing lnd node, that node must enable the RPC middleware interceptor feature. You can enable that by specifying the --rpcmiddleware.enable command line flag or by adding rpcmiddleware.enable=true to your lnd.conf file. See the remote configuration docs for more information.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import guggero's key from the ubuntu key server:

gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys F4FC70F07310028424EFC20A8E4256593F177720

Once you have her PGP key you can verify the release (assuming manifest-v0.13.992-experimental.sig and manifest-v0.13.992-experimental.txt are in the current directory) with:

gpg --verify manifest-v0.13.992-experimental.sig manifest-v0.13.992-experimental.txt

You should see the following if the verification was successful:

gpg: Signature made Thu Jun  6 15:36:23 2024 EDT
gpg:                using RSA key F4FC70F07310028424EFC20A8E4256593F177720
gpg: Good signature from "Oliver Gugger <gugger@gmail.com>" [ultimate]

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

cat manifest-v0.13.992-experimental.txt

One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.13.992-experimental

Verifying the Release Timestamp

We have also started to timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-v0.13.992-experimental.sig.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-v0.13.992-experimental.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Changelog (auto generated)

What's Changed

• [custom channels]: Use new tapchannelrpc RPC methods by @guggero in #807
• [custom channels]: bump experimental branch to latest taproot-assets version, increase version to v0.13.992-experimental by @guggero in #815

Full Changelog: v0.13.991-experimental...v0.13.992-experimental

Lightning Terminal v0.13.3-alpha

This release of Lightning Terminal (LiT) includes updates the integrated Taproot-assets (v0.4.1-alpha) and Loop (v0.28.6-beta) versions.
The minimum compatible version of lnd in remote mode has now been bumped to v0.17.1-beta.

We'll be continuously working to improve the user experience based on feedback from the community.

Installation and configuration instructions can be found in the README.

This release packages LND v0.18.2-beta, Taproot Assets Daemon v0.4.1-alpha, Loop v0.28.6-beta, Pool v0.6.5-beta and Faraday v0.2.13-alpha.

• IMPORTANT NOTE: To avoid loss of funds, it's imperative that you read the Operational Safety Guidelines before before using tapd on mainnet!

• The Taproot Assets daemon is still in alpha state, which means there can still be bugs and not all desired data safety and backup mechanisms have been implemented yet. Releasing on mainnet mainly signals that there will be no breaking changes in the future and that assets minted with v0.3.0+ will be compatible with later versions.

Breaking changes

The configuration value (taproot-assets.universe.public-access) and command line flag (--taproot-assets.universe.public-access) now needs a value and is no longer a boolean. The value now controls whether the node's universe database can be accessed over RPC and either read (value r) or written to (value w) or both (value rw).
So existing nodes with the configuration file value taproot-assets.universe.public-access=true need to change the value to taproot-assets.universe.public-access=rw. Users specifying the command line flag --taproot-assets.universe.public-access just need to append a value, for example --taproot-assets.universe.public-access=rw.

Important note for Umbrel/Lightning Terminal users

DO NOT UNDER ANY CIRCUMSTANCE uninstall (or re-install) the "Lightning Terminal" app without first making a manual backup of all local tapd data, if you are using Taproot Assets as part of the "Lightning Terminal" app with Umbrel -- or any comparable node-in-a-box solution. Uninstalling Umbrel apps deletes application data. This Taproot Assets application data encumbers Taproot Assets AND bitcoin funds. Receiving and sending tapd assets updates the daemon's funds-custody material. Merely having the lnd seed phrase is NOT enough to restore assets minted or received. WITHOUT BACKUP BEFORE DELETION, FUNDS ARE DESTROYED.

lnd in remote mode (lnd-mode=remote)

NOTE that the minimum version of lnd that can be used in --lnd-mode=remote is v0.17.1-beta.

Required changes when running in lnd remote mode

When connecting to an existing lnd node, that node must enable the RPC middleware interceptor feature. You can enable that by specifying the --rpcmiddleware.enable command line flag or by adding rpcmiddleware.enable=true to your lnd.conf file. See the remote configuration docs for more information.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import ellemouton's key from the ubuntu key server:

gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 26984CB69EB8C4A26196F7A4D7D916376026F177

Once you have her PGP key you can verify the release (assuming manifest-v0.13.3-alpha.sig and manifest-v0.13.3-alpha.txt are in the current directory) with:

gpg --verify manifest-v0.13.3-alpha.sig manifest-v0.13.3-alpha.txt

You should see the following if the verification was successful:

gpg: Signature made Fri Jul 26 11:24:28 2024 SAST
gpg:                using RSA key 26984CB69EB8C4A26196F7A4D7D916376026F177
gpg: Good signature from "Elle Mouton <elle.mouton@gmail.com>" [ultimate]

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

cat manifest-v0.13.3-alpha.txt

One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.13.3-alpha

Verifying the Release Timestamp

We have also started to timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-v0.13.3-alpha.sig.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-v0.13.3-alpha.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Release Notes:

https://github.com/lightninglabs/lightning-terminal/blob/master/docs/release-notes/release-notes-0.13.3.md

Lightning Terminal v0.13.991-experimental

This version is a hot fix in the integrated tapd that fixes an issue with an incorrectly created proof.

Release Notes

This release of Lightning Terminal (LiT) is the first, experimental alpha preview build that brings Taproot Assets to the Lightning Network, with support for Taproot Asset Channels.

We'll be continuously working to improve the user experience based on feedback from the community.

Please note that Taproot Asset Channel functionality is only supported when litd runs with both lnd and tapd in integrated mode (--lnd-mode=integrated and --taproot-assets-mode=integrated).

General installation and configuration instructions can be found in the README.

Guides for minting assets and setting up Taproot Asset Channels in a test environment can be found here:

• First Steps: Prepare and mint assets
• Taproot Asset Channels
• RFQ

This release packages a staging/testing branch of LND v0.18.0-beta, Taproot Assets Daemon v0.4.1, Loop v0.28.5-beta, Pool v0.6.5-beta and Faraday v0.2.13-alpha.

• IMPORTANT NOTE: To avoid loss of funds, it's imperative that you read the Operational Safety Guidelines before before using tapd on mainnet!

• The Taproot Assets daemon is still in alpha state, which means there can still be bugs and not all desired data safety and backup mechanisms have been implemented yet. Releasing on mainnet mainly signals that there will be no breaking changes in the future and that assets minted with v0.3.0+ will be compatible with later versions.

Breaking changes

The configuration value (taproot-assets.universe.public-access) and command line flag (--taproot-assets.universe.public-access) now needs a value and is no longer a boolean. The value now controls whether the node's universe database can be accessed over RPC and either read (value r) or written to (value w) or both (value rw).
So existing nodes with the configuration file value taproot-assets.universe.public-access=true need to change the value to taproot-assets.universe.public-access=rw. Users specifying the command line flag --taproot-assets.universe.public-access just need to append a value, for example --taproot-assets.universe.public-access=rw.

Important note for Umbrel/Lightning Terminal users

DO NOT UNDER ANY CIRCUMSTANCE uninstall (or re-install) the "Lightning Terminal" app without first making a manual backup of all local tapd data, if you are using Taproot Assets as part of the "Lightning Terminal" app with Umbrel -- or any comparable node-in-a-box solution. Uninstalling Umbrel apps deletes application data. This Taproot Assets application data encumbers Taproot Assets AND bitcoin funds. Receiving and sending tapd assets updates the daemon's funds-custody material. Merely having the lnd seed phrase is NOT enough to restore assets minted or received. WITHOUT BACKUP BEFORE DELETION, FUNDS ARE DESTROYED.

lnd in remote mode (lnd-mode=remote)

NOTE that the minimum version of lnd that can be used in --lnd-mode=remote is v0.17.0-beta.

Required changes when running in lnd remote mode

When connecting to an existing lnd node, that node must enable the RPC middleware interceptor feature. You can enable that by specifying the --rpcmiddleware.enable command line flag or by adding rpcmiddleware.enable=true to your lnd.conf file. See the remote configuration docs for more information.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import guggero's key from the ubuntu key server:

gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys F4FC70F07310028424EFC20A8E4256593F177720

Once you have her PGP key you can verify the release (assuming manifest-v0.13.991-experimental.sig and manifest-v0.13.991-experimental.txt are in the current directory) with:

gpg --verify manifest-v0.13.991-experimental.sig manifest-v0.13.991-experimental.txt

You should see the following if the verification was successful:

gpg: Signature made Thu Jun  6 15:36:23 2024 EDT
gpg:                using RSA key F4FC70F07310028424EFC20A8E4256593F177720
gpg: Good signature from "Oliver Gugger <gugger@gmail.com>" [ultimate]

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

cat manifest-v0.13.991-experimental.txt

One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.13.991-experimental

Verifying the Release Timestamp

We have also started to timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-v0.13.991-experimental.sig.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-v0.13.991-experimental.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Changelog (auto generated)

What's Changed

• mod+version: update tapd to v0.4.1, bump version v0.13.991-experimental by @guggero in #803

Full Changelog: v0.13.99-experimental...v0.13.991-experimental

Lightning Terminal v0.13.99-experimental

Release Notes

This release of Lightning Terminal (LiT) is the first, experimental alpha preview build that brings Taproot Assets to the Lightning Network, with support for Taproot Asset Channels.

We'll be continuously working to improve the user experience based on feedback from the community.

Please note that Taproot Asset Channel functionality is only supported when litd runs with both lnd and tapd in integrated mode (--lnd-mode=integrated and --taproot-assets-mode=integrated).

General installation and configuration instructions can be found in the README.

Guides for minting assets and setting up Taproot Asset Channels in a test environment can be found here:

• First Steps: Prepare and mint assets
• Taproot Asset Channels
• RFQ

This release packages a staging/testing branch of LND v0.18.0-beta, Taproot Assets Daemon v0.4.0, Loop v0.28.5-beta, Pool v0.6.5-beta and Faraday v0.2.13-alpha.

• IMPORTANT NOTE: To avoid loss of funds, it's imperative that you read the Operational Safety Guidelines before before using tapd on mainnet!

• The Taproot Assets daemon is still in alpha state, which means there can still be bugs and not all desired data safety and backup mechanisms have been implemented yet. Releasing on mainnet mainly signals that there will be no breaking changes in the future and that assets minted with v0.3.0+ will be compatible with later versions.

Breaking changes

The configuration value (taproot-assets.universe.public-access) and command line flag (--taproot-assets.universe.public-access) now needs a value and is no longer a boolean. The value now controls whether the node's universe database can be accessed over RPC and either read (value r) or written to (value w) or both (value rw).
So existing nodes with the configuration file value taproot-assets.universe.public-access=true need to change the value to taproot-assets.universe.public-access=rw. Users specifying the command line flag --taproot-assets.universe.public-access just need to append a value, for example --taproot-assets.universe.public-access=rw.

Important note for Umbrel/Lightning Terminal users

DO NOT UNDER ANY CIRCUMSTANCE uninstall (or re-install) the "Lightning Terminal" app without first making a manual backup of all local tapd data, if you are using Taproot Assets as part of the "Lightning Terminal" app with Umbrel -- or any comparable node-in-a-box solution. Uninstalling Umbrel apps deletes application data. This Taproot Assets application data encumbers Taproot Assets AND bitcoin funds. Receiving and sending tapd assets updates the daemon's funds-custody material. Merely having the lnd seed phrase is NOT enough to restore assets minted or received. WITHOUT BACKUP BEFORE DELETION, FUNDS ARE DESTROYED.

lnd in remote mode (lnd-mode=remote)

NOTE that the minimum version of lnd that can be used in --lnd-mode=remote is v0.17.0-beta.

Required changes when running in lnd remote mode

When connecting to an existing lnd node, that node must enable the RPC middleware interceptor feature. You can enable that by specifying the --rpcmiddleware.enable command line flag or by adding rpcmiddleware.enable=true to your lnd.conf file. See the remote configuration docs for more information.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import guggero's key from the ubuntu key server:

gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys F4FC70F07310028424EFC20A8E4256593F177720

Once you have her PGP key you can verify the release (assuming manifest-v0.13.99-experimental.sig and manifest-v0.13.99-experimental.txt are in the current directory) with:

gpg --verify manifest-v0.13.99-experimental.sig manifest-v0.13.99-experimental.txt

You should see the following if the verification was successful:

gpg: Signature made Thu Jun  6 15:36:23 2024 EDT
gpg:                using RSA key F4FC70F07310028424EFC20A8E4256593F177720
gpg: Good signature from "Oliver Gugger <gugger@gmail.com>" [ultimate]

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

cat manifest-v0.13.99-experimental.txt

One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.13.99-experimental

Verifying the Release Timestamp

We have also started to timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-v0.13.99-experimental.sig.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-v0.13.99-experimental.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Changelog (auto generated)

What's Changed

• custom channels: use tapd as the aux component implementation for lnd in integrated mode by @guggero in #761
• itest: add BTC-only keysend and invoice payments by @guggero in #775
• itests: add asset force close itest by @Roasbeef in #770
• itest: add breach itest for custom channels by @Roasbeef in #779
• itest: Add custom channels with grouped asset test by @GeorgeTsagk in #781
• litd: update to latest lnd+tapd versions, bump version to rc1 for asset chans release by @Roasbeef in #782
• itest: refactor, add more assertions by @guggero in #784
• build: bump version to v0.14.0-alpha.rc2 by @Roasbeef in #785
• itest: remove TODO after fix by @guggero in #786
• version: bump to v0.13.99-alpha.rc2 by @guggero in #787
• rules+firewall: rules and privacy mappings for channel creation by @bitromortac in #752
• build: update to latest lnd+tapd - bump version to v0.13.99-alpha.rc3 by @Roasbeef in #789
• mod+itest: reproduce and fix reverse direction invoice payment, bump to rc4 by @guggero in #790
• mod+itest: add test case for initiator having zero balance by @guggero in #796
• custom channels: add more itest coverage, fix pending channel bug by @guggero in #797
• build: bump version to v0.13.99 by @Roasbeef in #801
• version: change "alpha" to "experimental" for Taproot Asset Channel release by @guggero in #802

Full Changelog: v0.13.1-alpha...v0.13.99-experimental