Published: 2022-04-15 21:41:28 UTC
Also available on PyPi and can be installed with pip install -U hwi
tr()
descriptors and tap
address typesigntx
will return a status indicating whether the PSBT was signedenumerate
Published: 2022-04-12 15:11:43 UTC
Minor compatibility fixes
Published: 2022-04-07 04:40:20 UTC
Minor bugfixes and performance improvements.
Go to Repo Go to ReleasePublished: 2022-04-05 12:02:34 UTC
This update brings two brand new apps to the Umbrel App Store — Agora and sparkkiosk, along with updated apps and bugfixes.
Go to Repo Go to ReleasePublished: 2022-04-04 17:25:39 UTC
There are two types of binaries:
It's a windowed GUI application with Specter server included. Supported platforms: Windows, MacOS, Linux (x86_64)
Note on Linux: you need to set up udev rules (included in the archive). Check out readme.
Note on macOS: The current build supports only macOS Catalina (10.15) or higher. If you'd like to run Specter on an older macOS version, you can install Specter from Pip.
It's a command-line program that only runs Specter server. Supported platforms: Windows, MacOS, Linux (x86_64)
SHA256SUMS file contains sha256 hashes of all binary files and signed with "Specter Signer's" GPG key.
You can get the public key from here.
Fingerprint of the key is 785A 2269 EE3A 9736 AC1A 4F4C 864B 7CF9 A811 FEF7
This key has been signed by @k9ert's key which you might have used for validating th 1.7.0 release.
Published: 2022-04-03 16:35:30 UTC
option_scid_alias
is now supported and may be negotiated
when opening a channel with a peer. It can be configured via
ChannelHandshakeConfig::negotiate_scid_privacy
and is off by default but
will be on by default in the future (#1351).OpenChannelRequest
now has a channel_type
field indicating the features
the channel will operate with and should be used to filter channels with
undesirable features (#1351). See the Serialization Compatibility section.ChannelManager
supports sending and receiving short channel id aliases in
the funding_locked
message. These are used when forwarding payments and
constructing invoice route hints for improved privacy. ChannelDetails
has a
inbound_scid_alias
field and a get_inbound_payment_scid
method to support
the latter (#1311).DefaultRouter
and find_route
take an additional random seed to improve
privacy by adding a random CLTV expiry offset to each path's final hop. This
helps obscure the intended recipient from adversarial intermediate hops
(#1286). The seed is also used to randomize candidate paths during route
selection (#1359).lightning-block-sync
crate's init::synchronize_listeners
method
interface has been relaxed to support multithreaded environments (#1349).ChannelManager::create_inbound_payment_for_hash
's documentation has been
corrected to remove the one-year restriction on invoice_expiry_delta_secs
,
which is only applicable to the deprecated create_inbound_payment_legacy
and create_inbound_payment_for_hash_legacy
methods (#1341).Features
mutator methods now take self
by reference instead of by value
(#1331).RouteParameters::max_total_cltv_expiry_delta
(#1358).lightning-invoice
crate's utils
module
include versions that accept a description hash instead of only a description
(#1361).RoutingMessageHandler::sync_routing_table
has been renamed peer_connected
(#1368).MessageSendEvent::SendGossipTimestampFilter
has been added to indicate that
a gossip_timestamp_filter
should be sent (#1368).PeerManager
takes an optional NetAddress
in new_outbound_connection
and
new_inbound_connection
, which is used to report back the remote address to
the connecting peer in the init
message (#1326).ChannelManager::accept_inbound_channel
now takes a user_channel_id
, which
is used in a similar manner as in outbound channels. (#1381).BackgroundProcessor
now persists NetworkGraph
on a timer and upon
shutdown as part of a new Persister
trait, which also includes
ChannelManager
persistence (#1376).ProbabilisticScoringParameters
now has a base_penalty_msat
option, which
default to 500 msats. It is applied at each hop to help avoid longer paths
(#1375).ProbabilisticScoringParameters::liquidity_penalty_multiplier_msat
's default
value is now 40,000 msats instead of 10,000 msats (#1375).lightning
crate has a grind_signatures
feature used to produce
signatures with low r-values for more predictable transaction weight. This
feature is on by default (#1388).ProbabilisticScoringParameters
now has a amount_penalty_multiplier_msat
option, which is used to further penalize large amounts (#1399).PhantomRouteHints
, FixedPenaltyScorer
, and ScoringParameters
now
implement Clone
(#1346).ProbabilisticScorer
under --feature=no-std
(#1347).lightning-invoice
crate's utils
module
filter invoice hints in order to limit the invoice size (#1325).funding_locked
message was delayed by a block if the
funding transaction was confirmed while offline, depending on the ordering
of Confirm::transactions_confirmed
calls when brought back online (#1363).NetGraphMsgHandler
where it didn't continue to receive
gossip messages from peers after initial connection (#1368, #1382).ChannelManager::timer_tick_occurred
will now timeout a received multi-path
payment (MPP) after three ticks if not received in full instead of waiting
until near the HTLC timeout block(#1353).find_route
causing it to be overly aggressive in using
MPP over channels to the same first hop (#1370).channel_update
messages by checking
signatures after checking if no newer messages have already been processed
(#1380).find_route
which caused preferring paths with a
higher cost (#1398).ProbabilisticScorer
where a channel with not enough
liquidity could still be used when retrying a failed payment if it was on a
path with an overall lower cost (#1399).option_scid_alias
negotiated will be incompatible with
prior releases (#1351). This may occur in the following cases:
ChannelHandshakeConfig::negotiate_scid_privacy
is
enabled.OpenChannel
message
with a channel_type
that has ChannelTypeFeatures::supports_scid_privacy
return true. See UserConfig::accept_inbound_channels
.OpenChannelRequest
with a
channel_type
that has ChannelTypeFeatures::supports_scid_privacy
return
true. See UserConfig::manually_accept_inbound_channels
.In total, this release features 43 files changed, 4052 insertions, 1274 deletions in 75 commits from 11 authors, in alphabetical order: * Devrandom * Duncan Dean * Elias Rohrer * Jeffrey Czyz * Jurvis Tan * Luiz Parreira * Matt Corallo * Omar Shamardy * Viktor Tigerström * dependabot[bot] * psycho-pirate
Go to Repo Go to ReleasePublished: 2022-04-02 19:53:51 UTC
There are two types of binaries:
It's a windowed GUI application with Specter server included. Supported platforms: Windows, MacOS, Linux (x86_64)
Note on Linux: you need to set up udev rules (included in the archive). Check out readme.
Note on macOS: The current build supports only macOS Catalina (10.15) or higher. If you'd like to run Specter on an older macOS version, you can install Specter from Pip.
It's a command-line program that only runs Specter server. Supported platforms: Windows, MacOS, Linux (x86_64)
SHA256SUMS file contains sha256 hashes of all binary files and signed with "Specter Signer's" GPG key.
You can get the public key from here.
Fingerprint of the key is 785A 2269 EE3A 9736 AC1A 4F4C 864B 7CF9 A811 FEF7
This key has been signed by @k9ert's key which you might have used for validating th 1.7.0 release.
Published: 2022-04-02 00:29:36 UTC
General fixes/improvements, mainly restoring the fee reserve improvements made to the Quart branch.
Go to Repo Go to ReleasePublished: 2022-04-01 11:23:57 UTC
Published: 2022-03-31 13:44:20 UTC
Published: 2022-03-31 11:41:00 UTC
Published: 2022-03-30 10:17:28 UTC
There are two types of binaries:
It's a windowed GUI application with Specter server included. Supported platforms: Windows, MacOS, Linux (x86_64)
Note on Linux: you need to set up udev rules (included in the archive). Check out readme.
Note on macOS: The current build supports only macOS Catalina (10.15) or higher. If you'd like to run Specter on an older macOS version, you can install Specter from Pip.
It's a command-line program that only runs Specter server. Supported platforms: Windows, MacOS, Linux (x86_64)
SHA256SUMS file contains sha256 hashes of all binary files and signed with "Specter Signer's" GPG key.
You can get the public key from here.
Fingerprint of the key is 785A 2269 EE3A 9736 AC1A 4F4C 864B 7CF9 A811 FEF7
This key has been signed by @k9ert's key which you might have used for validating th 1.7.0 release.
Published: 2022-03-25 10:10:39 UTC
This version fixes an issue on some devices where creating an entry in the keystore would fail, preventing new wallets from being created.
List of commits (filter on phoenix-legacy)
You will need gpg
and our release signing key E434ED292E85643A. Note that you can get it:
- from our website: https://acinq.co/pgp/padioupm.asc
- from github user @pm47, a committer on eclair: https://api.github.com/users/pm47/gpg_keys
To import our signing key:
$ gpg --import padioupm.asc
To verify the release file checksums and signatures:
$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped
Published: 2022-03-23 18:31:51 UTC
This release contains several enhancements in JSON-RPC interface, Ethereum compatibility fixes and node robustness enhancements. This is a non-comprehensive list of the changes included in this version:
web3_sha3
method for non-hex encoded strings in https://github.com/rsksmart/rskj/pull/1637eth_getLogs
method performance improvements in https://github.com/rsksmart/rskj/pull/1650debug_traceTransaction
method in https://github.com/rsksmart/rskj/pull/1644You can find a complete list of the changes introduced in Iris 3.3.0 milestone.
SHA256 (see Reproducible Build guide for further details): cce6c949251d1ee6d9ab8bf1d29e026778a846f048a854ca5ef114000b05f079 rskj-core-3.3.0-IRIS-all.jar
Go to Repo Go to ReleasePublished: 2022-03-22 09:21:48 UTC
This release upgrades the built-in Tor client from v.0.4.5.10 to v0.4.6.9. There are many significant changes, that greatly increase the network stability and performance. The release also contains some rare but annoying crash fix. Make sure your Tor client is not running in the background so Wasabi can update it - the easiest way is to restart your machine and start the new version of Wasabi.
While setting up Wasabi is straightforward, even a Linux wizard with the longest beard can get stuck on the most basic tasks. Consider taking a look at the Installation Instructions guide.
If you want to build Wasabi from source code or update the source code check out these instructions.
From version 1.1.3 Wasabi also introduces reproducible builds: Deterministic Build Guide
Build with .NET Core 3.1.407-win-x64.
Published: 2022-03-18 14:00:59 UTC
When sending a payment, the "send all" checkbox lets users use all their balance for that payment and forces the app to use the highest possible trampoline fee, which can lead to unintended high fees (especially if the default trampoline fees have been altered by the user). This checkbox has thus been removed until we find a better solution.
You will need gpg
and our release signing key E434ED292E85643A. Note that you can get it:
- from our website: https://acinq.co/pgp/padioupm.asc
- from github user @pm47, a committer on eclair: https://api.github.com/users/pm47/gpg_keys
To import our signing key:
$ gpg --import padioupm.asc
To verify the release file checksums and signatures:
$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped
Published: 2022-03-17 13:57:16 UTC
Published: 2022-03-15 12:36:38 UTC
This update brings the latest versions of Jam, Krystal Bull, Suredbits Wallet, Bitfeed, LNDg, and Urbit to the Umbrel App Store.
Go to Repo Go to ReleasePublished: 2022-03-08 10:37:06 UTC
This is a follow-up release that fixes the news badge on Settings
for existing Bisq users and handles an additional case where the DAO needs resync.
See https://github.com/bisq-network/bisq/milestone/69?closed=1 for more details.
Here are the release notes from v1.8.3:
This release improves privacy by automatically deleting past trade data, improves the UI in many places, and fixes bugs across the board (as always).
gettrades
methodNo new assets were added.
For a detailed description on how to verify your Bisq installer please have a look at our wiki: https://bisq.wiki/Downloading_and_installing#Verify_installer_file
Url of the signing key (Christoph Atteneder): https://bisq.network/pubkey/29CDFD3B.asc
Full fingerprint: CB36 D7D2 EBB2 E35D 9B75 500B CD5D C1C5 29CD FD3B
Import the key:
curl https://bisq.network/pubkey/29CDFD3B.asc | gpg --import
GPG prints a confusion warning: "This key is not certified with a trusted signature!" - See https://serverfault.com/questions/569911/how-to-verify-an-imported-gpg-key for background information what it means.
How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-1.8.4.dmg)
Verify jar file inside binary: You can verify on OSX the jar file with: shasum -a256 [PATH TO BISQ APP]/Bisq.app/Contents/app/desktop-1.8.4-all.jar The output need to match the value from the Bisq-1.8.4.jar.txt file.
There are three hashes within the Bisq-1.8.4.jar.txt file (macOS, Windows, Linux). If you want to reproduce and verify the hash of the jar file locally, you need to do so on Windows or Linux using Java 15.0.5 and the v1.8.4 release tag. Because of the signing and notarization process that requires the developer certificate used for the build on macOS it is not possible to create the same jar on macOS.
There is a known issue with Anti Virus software. We got several reports from users running into different problems. Either the AV software blocks Bisq or Tor, delete files in the data directory [2] or app directory [1]) or cause such a long delay at startup that Tor gets terminated and a file remains locked which can cause that Bisq cannot be started afterwards. To resolve that you need to restart Windows then the lock get released. We are working on solutions to fix those issues.
If you use Crypto currencies on your Windows system be aware that Windows is much more vulnerable to malware than Linux or OSX. Consider to use a dedicated non-Windows system when dealing with cryptocurrencies.
[1] Application directory (contains application installation files): C:\Users<username>\AppData\Local\Bisq
[2] Data directory (contains all Bisq data including wallet): C:\Users<username>\AppData\Roaming\Bisq\btc_mainnet\tor (you can delete everything except the hiddenservice directory)
Hint for Debian users:
If you have problems starting Bisq on Debian use: /opt/bisq/bin/Bisq
If your Linux distro does not support .deb files please follow this instruction:
cd ~/Downloads
mkdir tmp
cd tmp
ar x ../Bisq-64bit-1.8.4.deb
sudo tar Jxvf data.tar.xz
sudo cp -rp opt/Bisq /opt/
That instruction is not tested on many different distros. If you encounter problems please report it in a Github issue so we can improve it.
Thanks to everyone who directly contributed to this release:
A special thanks to our first time contributors: - @MarnixCroes: Update Apple plist copyright notice
As well as to everyone that helped with translations on Transifex.
Go to Repo Go to ReleasePublished: 2022-03-04 13:22:07 UTC
Published: 2022-03-04 07:56:34 UTC
https://github.com/romanz/electrs/blob/master/RELEASE-NOTES.md#096-mar-4-2022
Go to Repo Go to ReleasePublished: 2022-03-03 14:05:07 UTC
Changelog:
Published: 2022-03-03 13:17:27 UTC
Published: 2022-03-02 12:03:44 UTC
Published: 2022-03-01 14:07:30 UTC
This update brings three brand new apps to the Umbrel App Store — Jam (JoinMarket UI), Snowflake Tor Proxy, and Bleskomat Server, along with updated apps and bugfixes.
Go to Repo Go to ReleasePublished: 2022-03-01 05:45:37 UTC
Published: 2022-03-01 04:15:52 UTC
Phantom node
payments are now supported, allowing receipt of a payment on
any one of multiple nodes without any coordination across the nodes being
required. See the new PhantomKeysManager
's docs for more, as well as
requirements on KeysInterface::get_inbound_payment_key_material
and
lightning_invoice::utils::create_phantom_invoice
(#1199).KeysInterface
methods
now accept a Recipient
parameter to select between the local node_id
and
a phantom-specific one.ProbabilisticScorer
, a Score
based on learning the current balances of
channels in the network, was added. It attempts to better capture payment
success probability than the existing Scorer
, though may underperform on
nodes with low payment volume. We welcome feedback on performance (#1227).Score::channel_penalty_msat
now always takes the channel value, instead of
an Option
(#1227).UserConfig::manually_accept_inbound_channels
was added which, when set,
generates a new Event::OpenChannelRequest
, which allows manual acceptance
or rejection of incoming channels on a per-channel basis (#1281).Payee
has been renamed to PaymentParameters
(#1271).PaymentParameters
now has a max_total_cltv_expiry_delta
field. This
defaults to 1008 and limits the maximum amount of time an HTLC can be pending
before it will either fail or be claimed (#1234).lightning-invoice
crate now supports no-std environments. This required
numerous API changes around timestamp handling and std+no-std versions of
several methods that previously assumed knowledge of the time (#1223, #1230).lightning-invoice
now supports parsing invoices with expiry times of more
than one year. This required changing the semantics of ExpiryTime
(#1273).CounterpartyCommitmentSecrets
is now public, allowing external uses of
the BOLT 3
secret storage scheme (#1299).Sign
methods now receive HTLC preimages as proof of state
transition, see new documentation for more (#1251).KeysInterface::sign_invoice
now provides the HRP and other invoice data
separately to make it simpler for external signers to parse (#1272).Sign::sign_channel_announcement
now returns both the node's signature and
the per-channel signature. InMemorySigner
now requires the node's secret
key in order to implement this (#1179).ChannelManager
deserialization will now fail if the KeysInterface
used
has a different node_id
than the ChannelManager
expects (#1250).ErrorAction
variant was added to send warning
messages (#1013).chain::Listen
objects in lightning-block-sync
no
longer require a mutable reference (#1304).ChannelManager
's internal
locks could have an order violation leading to a deadlock (#1238).BackgroundProcessor
(#1269).ChannelManager
prior to BackgroundProcessor
stopping,
preventing race conditions where channels are closed on startup even with a
clean shutdown. This requires that users stop network processing and
disconnect peers prior to BackgroundProcessor
shutdown (#1253).ChannelHandshakeLimits
provided via the override_config
to
create_channel
are now applied instead of the default config (#1292).channel_type
field to accept_channel
messages we send, which
may avoid some future compatibility issues with other nodes (#1314).lightning-persister
crashed
while persisting updated data, we may have failed to initialize (#1332).ChannelDetails::balance_msat
to
underflow and be reported as large, or cause panics in debug mode (#1268).Trace
level to the
Gossip
level (#1220).announcement_signatures
until the channel has six confirmations,
slightly improving propagation of channel announcements (#1179).ChannelManager
data written by versions prior to 0.0.105 will result
in preimages for HTLCs that were pending at startup to be missing in calls
to KeysInterface
methods (#1251).0.0.105 fixes two denial-of-service vulnerabilities which may be reachable from untrusted input in certain application designs.
ChannelMonitor::get_claimable_balances
spuriously panics in some scenarios
when the LDK application's local commitment transaction is confirmed while
HTLCs are still pending resolution.In total, this release features 109 files changed, 7270 insertions, 2131 deletions in 108 commits from 15 authors, in alphabetical order: * Conor Okus * Devrandom * Elias Rohrer * Jeffrey Czyz * Jurvis Tan * Ken Sedgwick * Matt Corallo * Naveen * Tibo-lg * Valentine Wallace * Viktor Tigerström * dependabot[bot] * hackerrdave * naveen * vss96
Go to Repo Go to ReleasePublished: 2022-02-21 08:26:22 UTC
Published: 2022-02-20 23:28:13 UTC
Cache & Backgroundscan refactor & new apps: LNbits c-lightning, Tallycoin Connect, Helipad, ...
Go to Repo Go to ReleasePublished: 2022-02-18 23:29:20 UTC
Published: 2022-02-15 16:59:28 UTC
This release is backwards incompatible with previous releases of bitcoin-s.
You will not be able to build a DLC with prior releases of bitcoin-s. This was due to a bug
in how we computed contractId
in a DLC. See #4012 for more information.
We now have official typescript bindings for our oracleServer
and appServer
See the individual module sections for more information on lower level updates to the codebase.
If you want to run the standalone server binary, after verifying gpg signatures, you
can unzip bitcoin-s-server-1.9.0.zip
and then run it with ./bin/bitcoin-s-server
to start the node. You will need to
configure the node properly first, you can find example
configurations here.
You can then unzip the bitcoin-s-cli-1.9.0.zip
folder and start using the bitcoin-s-cli
like this:
```bashrc
./bin/bitcoin-s-cli --help
Usage: bitcoin-s-cli [options] [
-n, --network
For more information on what commands bitcoin-s-cli
supports check the documentation, here is where to
start: https://bitcoin-s.org/docs/next/applications/server#server-endpoints
This release is signed with Chris's signing key with
fingerprint 339A49229576050819083EB3F99724872F822910
To do the verification, first hash the executable using sha256sum
. You should check that the result is listed in
the SHA256SUMS.asc
file next to its file name. After doing that you can use gpg --verify
to authenticate the
signature.
Example:
``` sha256sum bitcoin-s-server-1.9.0.zip ec2bccd61bdabc1f0453d1f8b7608b628da28fe45d55754a269e30391106c18d bitcoin-s-server-1.9.0.zip
gpg --verify SHA256SUMS.asc gpg: Signature made Tue 15 Feb 2022 12:58:48 PM CST gpg: using RSA key 339A49229576050819083EB3F99724872F822910 gpg: Good signature from "Chris Stewart stewart.chris1234@gmail.com" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 339A 4922 9576 0508 1908 3EB3 F997 2487 2F82 2910 ```
89 Chris Stewart
36 Scala Steward
35 benthecarman
31 rorp
3 Nadav Kohen
2 user411
1 Shreyansh
1 dependabot[bot]
https://repo1.maven.org/maven2/org/bitcoin-s/
https://oss.sonatype.org/content/repositories/snapshots/org/bitcoin-s/
https://hub.docker.com/orgs/bitcoinscala/repositories
Bug fixes and improve the API for AppConfig
4e6c68155e Sort outcomes in decodeoffer
response (#4094)
142612f034 Make newConfigOfType use VectorConfig
2066447cdc Add isEndpoint to numeric contract descriptor serialization (#4033)
e802254a20 2022 01 24 rm appconfig varargs (#4011)
3162c1b2d0 Ignore .DS_Store files when making backups (#4000)
a7af8cac4c Patch bug where zipdatadir
doesn't work if the directory was not created (#3959)
The major features shipped this release is support for websockets. You can now be notified of websocket events from the wallet, dlc wallet, and chain. These are used on the wallet-server-ui to notify when events happen
This module will be renamed to Wallet Server
in future releases as that
is a more accurate name for this module.
There are various PRs that broke API compatability from 1.8
-> 1.9
. See the list
08941206fc Bump timeout to 60 seconds (#4021)
d2f53db82e Change BTC RPC log level (#4010)
f438ce2897 Refactor zipDatadir (#3999)
d88e2494e0 Make RPC authentication optional for localhost (#3980)
ee3ee53191 RPC password authentication (#3961)
9dd126bb9f Modify estimatefee endpoint to return a number rather than a string (#3973)
66e23b61a8 2021 01 11 issue 3938 (#3971)
eeeecb00c5 Reduce polling log to trace when we try to poll bitcoind (#3964)
5de325e7de Exclude seeds from backup (#3950)
f8f8f50aae Implement ping every 5 seconds to keep websocket connection alive (#3947)
7527388be5 2021 12 20 ws dlc callbacks (#3926)
50bec2abc6 2021 12 14 websockets (#3906)
4b07629d56 Add getmediantimepast
RPC call (#3921)
4646ef6e19 Remove BitcoinSServerMain.startedFP (#3928)
3cd57d37f5 Remove backupwallet / backup oracle (#3920)
f8f5a8e8dc Update docker-application.conf (#3905)
7e214da601 Improve BitcoinSAppConfig.zipDatadir
(#3903)
6c67e83d3f 2021 12 10 issue 3891 (#3894)
41585a18ca Make Bitcoin Core RPC backend to retry on Error -28: Verifying blocks (#3896)
a38309bed1 Add range of block heights to the error message (#3886)
d393848cc2 2021 11 30 issue 3847 (#3862)
0b9500f4f2 Add hex
fields to decodecontractinfo
JSON response (#3830)
1d7529236f 2021 11 13 scan bitcoind witspkv1 mempool (#3825)
5189b6ad5c revert logging directives on request/response back to DEBUG (#3819)
a40ef1ab21 Break existing api to get new address to remove the requirement for null label (#3818)
21fab4ee70 Improve app server validation error handling (#3796)
403c78fd8f Server Docker config (#3775)
Implements rudimentary support for bitcoin core v22. This release does not implement all RPCs on v22.
5366428fb2 Implement BitcoindRpcClient.epochSecondToBlockHeight
(#4068)
c0c54acc24 Make non-final bitcoind RPC error message more descriptive (#3915)
a6898defe2 Support for Bitcoin Core v22 (#3834)
Ergonomic improvements for runnign test suites, make the installer names more readable for non technical users.
52dcf51e82 Automatically download binaries if they are used in test suite (#4005) e24efd65ae 2022 01 12 docker ws (#3976) 6e7af37ca0 2021 12 03 installer rename (#3876) cd3006c020 Verify binary download hashes (#3849)
Adds a callback so that we can be notified when a header is processed by the chain module.
7ee1f0f406 Implement batching of database calls for our chain callback (#4003) d06b064b6b 2021 12 28 blockprocessed callback (#3946)
This is a new module in the 1.9 release. It adds support for a clightning RPC.
cb704da927 Add clightning sendcustommsg (#3883) 7933c90741 Update c-lightning to v0.10.2 (#3857) cd5451adaa Add clightning listtransactions func (#3797) 01a7c7c838 Make clightning tests execute async (#3768) 6d43d443ba Initial c-lightning rpc support (#3755)
This release merges support for general payout curves in the core
module for the DLC specification.
See #3854 for more information
This release also merges support for disjoint union contracts in the DLC specification.
This release fixes a bug in our contractId
computation.
This breaks backward compatibility in older releases of bitcoin-s.
13c46e0af8 Move expensive script checks to last inside of P2PKWithTimeoutScriptPubKey (#4087)
e2b9c458e4 Change DLCUtil.buildOracleSignatures
(#4061)
7a6f0430d6 2022 02 03 issue 4032 (#4042)
71711ca582 Add invariant to make sure spendingTxId is different than the txid (#4019)
b918cf78b7 Fix bugs where we were building internally inconsistent SpendingInfoDb (#4016)
d983ad14f3 Fix contractid computation (#4012)
21de609ed8 2022 01 22 cetsignatures refactor (#4004)
214213b59d 2022 01 16 issue 3983 (#3987)
93c5121632 2021 01 06 tlv invariants (#3965)
8857af2b66 Address ben's code review on #3854 (#3962)
b342f373ae Make ContractDescriptorTemplate an unsealed trait (#3963)
8c5288d758 Implemented general payout curves (#3854)
6652448f99 Added constructor for p2pkh for decompressed public keys (#3944)
d66afe9e43 Add satoshisRounded to Bitcoins (#3904)
0d37c4b54f 2021 12 08 block parsing bug caused by 65 byte taproot signatures (#3887)
8765c2f845 Disjoint union dlc (#3839)
422aea2242 Fix TypeIdentifier fromBytes (#3832)
0b3654f020 Remove scientific notation from Bitcoins.toString() (#3811)
09c2562675 Added WitnessScriptPubKeyV1 for sending to Taproot addresses (#3737)
aa748c012f 2021 11 03 protocol version (#3793)
18726c10bb Move ValueIterator out of TLVFactory trait (#3794)
92cf042ccb Expose MnemonicCode.toEntropy() and MnemonicCode.toEntropyWithChecksum() methods (#3786)
92ab9faa45 Decide which coin selection solution to use based on waste metric (#3646)
f4a2ec8554 Make AesEncryptedData a network element / factory (#3952)
A major theme this release is enabling our APIs to use database actions in Slick. This allows us to build database transactions to avoid corrupting data.
We also fixed some bugs in our database implementations around storing very large scriptpubkeys.
4d85b7a3d7 Support for big SPKs (#4084)
3d674c37f3 Create upsertAllAction (#4073)
2166faf61d Make findByPrimaryKeysAction public (#4079)
3991789129 Don't call findByPrimaryKeys if ids is empty (#4074)
48189d5c1d Make CRUD.run
and CRUD.runVec
transactional (#4059)
0079489a15 Create DbMapper for DoubleSha256Digest (#3995)
6c2bb0d111 Rename database username and password variables (#3930)
afb51228b4 Add NodeId to DbCommonsColumnMappers (#3880)
085b8b1910 Implement CRUDAction.deleteAction() (#3877)
2d5732375f Add CRUDAction.{updateAllAction, updateAction} (#3872)
f71d3567ed 2021 11 23 crud action (#3851)
The major change this release is implementing a connection timeout for dlc node. If we cannot connect to a peer within 45 seconds, we throw a timeout exception.
55ecc1ae8f Implement connection timeout (#4081) 019c9b2644 Fix log message failure in DLCDataHandler (#3845) 41cb26a3bb Make DLC node's external IP configurable (#3838)
Improvements to the database handling code so that announcement/attestation creation is transactional.
49d4d7f179 2022 02 06 issue 4049 (#4056) 7f344ad3ff 2022 02 06 announcement creation logging (#4055) 524c5212e0 Add MasterXPubTable to list of DLCOracle tables (#3955) c3d1b2ee12 Give DLCOracle to filter events by pending/completed (#3953)
This release of dlc wallet fixes bugs for accepting offers multiple times.
We also add a new column in global_dlc_data
for serialization_version
for when we
break binary level serialization in the DLC protocol spec. This will be done in the 2.0
release of bitcoin-s.
Finally there is a ton of improvements to database handling code.
6cfbf67812 Prevent DB state corruption while accepting the same offer multiple times (#4067)
bce58ba33d Validate announcement signatures on create/accept offer (#4071)
9de4b0272a 2022 01 31 issue 4030 (#4066)
f253b5055e 2022 02 08 dlc accept refactor (#4064)
5aeecdb893 Reworking/refactoring acceptDLCOffer (#4048)
590cd9c72e 2022 02 06 remoteclaimed refactor (#4054)
d213e9935d Add better exception messages (#4053)
bd5bcfef3a 2022 01 18 issue 3969 Add serialization_version
to global_dlc_data
(#3992)
8a881b37f4 Add DLC callback for refunded DLC (#3989)
ee0d62c5b8 2022 01 14 DLCDataManagement
refactor (#3982)
4ca586ca46 2021 12 19 dlc callbacks (#3923)
d71208cf0f Support Eclair v0.6.2 (#3765)
This release adds a new module so you can use esplora on as a chain data source.
03abb7537b Add basic esplora client (#4018)
5f4053b2e4 Create FallbackFeeRateApi (#3974) bf8b165fe9 Implement recovery for when we cannot receive a fee rate from a FeeRateApi (#3975)
Small bug fixes. We are moving to having a web interface for bitcoin-s.
This can be found here:
https://github.com/bitcoin-s/bitcoin-s-ts/tree/master/wallet-server-ui
546e030dde [GUI] Fix 'First and last points must be endpoints' exception (#4029) 2aa6f168eb Implement rpc password in GUI (#3986) 7f9fb87a55 Call trim on peer address in Accept dialog (#3942) 856e455be3 Remove 'not set' rate of return % sign on wallet (#3828)
Upgrades lnd to 0.14.2, implements more lnd rpc functionality.
44373f8449 Add functions for LND subscription (#4062) afc6a32c62 Update lnd to v0.14.2 (#4040) 3ba8fb6dd4 Allow creating invoices with description hash (#3966) f54ed98c74 Add subscribe invoices function to lnd (#3860) 09f0ac4657 Update lnd to v0.14.1 (#3848) 155301fc1d Allow lnd remote to work with certificate string (#3840) 079fa62073 Lnd v0.14.0 (#3835)
Fixes various bugs around broadcasting witness transactions. Also fixes bugs to make sure we fetch the entire witness transaction (witnesses included). Previously we wouldn't get the witness which leads to problems when calculating DLC outcome state.
This release also adds the ability to store peers we see on the p2p network in teh database. Eventually
we will be able to connect to random peers we see on the p2p network rather than just connecting
to the node configured in bitcoin-s.node.peers
98c5d816ac 2022 01 25 issue 4014 (#4015) dbfd58da86 Add log txids inside of inventories in big endian rather than little endian (#4013) a58ef1cd02 Storing peers in database (#3773) 90e01d7fc6 Fix broadcasting witness vs legacy txs (#3841) 9701769125 Handle TypeIdentifier.MsgWitnessTx messages (#3836) fc09f41db2 Request witness versions of transactions from nodes (#3829)
Updates to the underlying libsecp256k1 to give better performance.
9c9a0a618f Update secp256k1-zkp (#3856)
Improves database handling code in the wallet so we use database transactions more often.
This release included various bug fixes and performance.
dc47c070a2 Fix SpendingInfoDAO.findOutputsReceived() bug (#4090)
eeabe5cd77 2022 02 11 clearutxoandaddresses for account transactional (#4077)
883b01006d Fetch blockHeight earlier in TransactionProcessing.processBlock() (#4025)
8d04ca1cd3 2022 01 30 optimize processblock (#4024)
cf16d93648 Fix bug where we didn't set spendingTxId when transitioning from Reserved
-> PendingConfirmationsSpent
(#3909)
42d6955f79 Filter dust from coin selection (#3866)
21c97bba12 Filter transactions for onTransactionProcessed (#3990)
41b96c4c7e Add rescan
field to walletinfo
response (#3933)
665f931721 Work around for WalletAppConfig.scheduler being blocked by AddressQueueRunnable (#3917)
2d9d12816b Add WalletCallbacks.onBlockProcessed() (#3912)
1969056372 Add better logs for fundTransactionInternal (#3911)
8307fdc0d1 2021 12 12 wallet doublespend tests (#3898)
174c511cd3 2021 12 12 wallet optimization (#3897)
d060c1c5fa Use bigendian txids in wallet log messages (#3893)
174c511cd3 2021 12 12 wallet optimization (#3897)
d060c1c5fa Use bigendian txids in wallet log messages (#3893)
ba88fb1a03 2021 11 12 fix multiple tag issue (#3822)
b3d61bc793 Add deleting address tags to to clearAllUtxosAndAddresses() (#3817)
31e8324522 Make sure exception is caught by Future inside of UtxoHandling.unmarkUTXOsAsReserved() (#3816)
Upgrades tor to 0.4.6.9
1708add6ec Make Tor connect error message more human readable (#4078) 2dcbe73504 Update Tor version to 0.4.6.9 (#3993) 169222a306 Add default proxy params (#3863) e02c9bba12 Overridable Tor config (#3780)
95d9bf44a5 Add 1.9.0 of the website (#4096) e8ee5d7339 Bump website dependencies (#4095) 3931897e7f 2022 02 13 issue 3405 (#4089) 07fcfd0568 2022 02 12 update mdoc fix downloadlink (#4086) e5707d5002 Fix broken website examples (#4085) 526ed37a28 Cleanup docs that use $ (#4083) 4ea87c741f 2022 02 12 cleanup example config (#4082) 35dccd88d6 Add new section to README for running bitcoin-s, add link to the web frontend (#4069) 99418c798a 2022 02 07 release note draft (#4060)
Go to Repo Go to ReleasePublished: 2022-02-15 06:07:59 UTC
Published: 2022-02-09 15:35:35 UTC
This update brings four brand new apps to the Umbrel App Store — Urbit, Urbit Bitcoin Connector, Tailscale, and usocial, along with LND 0.14.2, updated apps, and Nunchuk wallet connection support.
Go to Repo Go to ReleasePublished: 2022-02-08 04:51:41 UTC
Published: 2022-02-07 13:41:11 UTC
Updated LNURLPoS to LNURLDevices, to give the extension greater scope Added admin users to allow easy debiting of admin accounts, and admin only extensions Added FakeWallet, so LNbits can be used completely detached from bitcoin as a centralised payment server (for use as voucher system in schools, universities, businesses, events, etc)
Go to Repo Go to ReleasePublished: 2022-02-04 15:45:49 UTC
https://github.com/romanz/electrs/blob/master/RELEASE-NOTES.md#095-feb-4-2022
Go to Repo Go to ReleasePublished: 2022-02-03 22:33:20 UTC
This is the second minor release of the 0.14x cycle! This release contains no new larger/major features, and instead packages up a series of bug fixes (several obscure crash fixes), and enhancements (like begin able to convert a node to a watch-only mode for use with the remote signer feature).
We strongly recommend that all users update!
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 the keys that have signed this release if you haven't done so already:
curl https://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import
Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.14.2-beta.sig
and manifest-v0.14.2-beta.txt
are in the current directory) with:
gpg --verify manifest-roasbeef-v0.14.2-beta.sig manifest-v0.14.2-beta.txt
You should see the following if the verification was successful:
gpg: Signature made Thu Feb 3 13:55:45 2022 PST
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]
That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256
hash of the archive with shasum -a 256 <filename>
, compare it with the corresponding one in the manifest file, and ensure they match exactly.
From this new version onwards, in addition time-stamping the git tag with OpenTimeStamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.14.2-beta.txt.asc.ots
.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.14.2-beta.sig.ots -f manifest-roasbeef-v0.14.2-beta.sig
Alternatively, the open timestamps website can be used to verify timestamps if one doesn't have a bitcoind
instance accessible locally.
These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.
Our release binaries are fully reproducible. Third parties are able to verify that the release binaries were produced properly without having to trust the release manager(s). See our reproducible builds guide for how this can be achieved.
The release binaries are compiled with go1.17.3
, which is required by verifiers to arrive at the same ones.
They include the following build tags: autopilotrpc
, signrpc
, walletrpc
, chainrpc
, invoicesrpc
, routerrpc
, watchtowerrpc
and monitoring
. Note that these are already included in the release script, so they do not need to be provided.
The make release
command can be used to ensure one rebuilds with all the same flags used for the release. If one wishes to build for only a single platform, then make release sys=<OS-ARCH> tag=<tag>
can be used.
Finally, you can also verify the tag itself with the following command:
$ git verify-tag v0.14.2-beta
gpg: Signature made Thu 03 Feb 2022 08:21:05 PM UTC using RSA key ID 9B280306
gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>"
To verify the lnd
and lncli
binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):
shell
$ docker run --rm --entrypoint="" lightninglabs/lnd:v0.14.2-beta /verify-install.sh v0.14.2-beta
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/lnd [command-line options]
Users are able to rebuild the target release themselves without having to fetch any of the dependencies. In order to do so, assuming
that vendor.tar.gz
and lnd-source-v0.14.2-beta.tar.gz
are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf lnd-source-v0.14.2-beta.tar.gz
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.14.2-beta" ./cmd/lnd
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.14.2-beta" ./cmd/lncli
The -mod=vendor
flag tells the go build
command that it doesn't need to fetch the dependencies, and instead, they're all enclosed in the local vendor directory.
Additionally, it's now possible to use the enclosed release.sh
script to bundle a release for a specific system like so:
make release sys="linux-arm64 darwin-amd64"
⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️
The release notes can be found here: https://github.com/lightningnetwork/lnd/blob/master/docs/release-notes/release-notes-0.14.2.md
Go to Repo Go to ReleasePublished: 2022-02-03 12:04:52 UTC
Published: 2022-02-02 20:13:32 UTC
Published: 2022-02-02 15:30:28 UTC
This update includes the latest Kollider app which contains a bugfix.
Umbrel 0.4.12 brings four brand new apps in the Umbrel App Store — Kollider, Bitfeed, Suredbits Wallet, and LNDg, updated apps, a security patch, bug fixes, and more.
If you face any difficulties while updating, please message us on Telegram: https://t.me/getumbrel
Go to Repo Go to ReleasePublished: 2022-02-02 13:53:43 UTC
Umbrel 0.4.12 brings four brand new apps in the Umbrel App Store — Kollider, Bitfeed, Suredbits Wallet, and LNDg, updated apps, a security patch, bug fixes, and more.
Go to Repo Go to ReleasePublished: 2022-02-02 11:46:28 UTC
Published: 2022-02-01 15:37:31 UTC
There are two types of binaries:
It's a windowed GUI application with Specter server included. Supported platforms: Windows, MacOS, Linux (x86_64)
Note on Linux: you need to set up udev rules (included in the archive). Check out readme.
Note on macOS: The current build supports only macOS Catalina (10.15) or higher. If you'd like to run Specter on an older macOS version, you can install Specter from Pip.
It's a command-line program that only runs Specter server. Supported platforms: Windows, MacOS, Linux (x86_64)
SHA256SUMS file contains sha256 hashes of all binary files and signed with "Specter Signer's" GPG key.
You can get the public key from here.
Fingerprint of the key is 785A 2269 EE3A 9736 AC1A 4F4C 864B 7CF9 A811 FEF7
This key has been signed by @k9ert's key which you might have used for validating th 1.7.0 release.
Published: 2022-02-01 09:15:56 UTC
This release adds official support for two long-awaited lightning features: anchor outputs and onion messages. Support for the PostreSQL database backend is also now production ready! This release also includes a few bug fixes and many new (smaller) features. It is fully compatible with 0.6.2 (and all previous versions of eclair).
Because this release changes the default type of channels that your node will use, make sure you read the release notes carefully! The release notes can be found here.
You will need gpg
and our release signing key 7A73FE77DE2C4027. Note that you can get it:
To import our signing key:
sh
$ gpg --import drouinf.asc
To verify the release file checksums and signatures:
sh
$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped
Eclair builds are deterministic. To reproduce our builds, please use the following environment (*):
Use the following command to generate the eclair-node package:
sh
mvn clean install -DskipTests
That should generate eclair-node/target/eclair-node-0.7.0-a804905-bin.zip
with sha256 checksums that match the one we provide and sign in SHA256SUMS.asc
(*) You may be able to build the exact same artefacts with other operating systems or versions of JDK 11, we have not tried everything.
This release is fully compatible with previous eclair versions. You don't need to close your channels, just stop eclair, upgrade and restart.
Go to Repo Go to ReleasePublished: 2022-01-31 20:46:04 UTC
Published: 2022-01-29 12:15:02 UTC
There are two types of binaries:
It's a windowed GUI application with Specter server included. Supported platforms: Windows, MacOS, Linux (x86_64)
Note on Linux: you need to set up udev rules (included in the archive). Check out readme.
Note on macOS: The current build supports only macOS Catalina (10.15) or higher. If you'd like to run Specter on an older macOS version, you can install Specter from Pip.
It's a command-line program that only runs Specter server. Supported platforms: Windows, MacOS, Linux (x86_64)
SHA256SUMS file contains sha256 hashes of all binary files and signed with "Specter Signer's" GPG key.
You can get the public key from here.
Fingerprint of the key is 785A 2269 EE3A 9736 AC1A 4F4C 864B 7CF9 A811 FEF7
This key has been signed by @k9ert's key which you might have used for validating th 1.7.0 release.
Published: 2022-01-28 13:58:43 UTC
Published: 2022-01-28 04:48:57 UTC
This is a minor bug fix release for an issue that may cause historical mempool graphs to appear incorrectly after upgrading from v2.2 - we recommend upgrading directly to v2.3.1 instead of v2.3.0 if you are currently using v2.2
autocommit=0
flag when migrating SQL database Full Changelog: https://github.com/mempool/mempool/compare/v2.3.0...v2.3.1
Go to Repo Go to ReleasePublished: 2022-01-28 01:48:32 UTC
Bug fixes:
Fix: Existing Lightning addresses were not loaded (#3367 #3368) @Kukks
Go to Repo Go to ReleasePublished: 2022-01-27 13:26:33 UTC
BTCPay Server started in August 2017 and meanwhile has been evolving incrementally thanks to the feedback of the community.
It was finally time to cleanup the UI/UX and technical debt we accumulated over the years.
We enumerate here a lot of new features and bug fixes, but we do not enumerate the UI/UX changes, we dedicated a separate blog post for this topic.
The heavy lifting of this work has been mainly brought to you thanks to the collaboration of @dstrukt and @dennisreimann. We thank also all the testers we brought us feedback, and all of you who participated in the weekly design meetings.
The work on the UI/UX is however never over and we will keep on improving it based on your feedback.
Note: If you are using our docker deployment on a raspberry pi 4, there is a small chance your docker version does not support the new docker image. If you have any issue with raspberry pi 4, you need to update your docker version following steps on this blog post. Note that you do not need to update libseccomp2, our update process does this for you automatically.
missingPermission
field to 403 errors (#3195) @NicolasDorier @woutersamaeycreated
field of payment request should be a unix timestamp @woutersamaey (#3221)created
field of payment request should be a unix timestamp @woutersamaey (#3221)Published: 2022-01-26 02:06:18 UTC
IMPORTANT: RSK Testnet consensus rules have changed in this version, and it is not compatible with previous versions (only for Testnet, this doesn't apply to Mainnet). If you've been running previous versions of the RSK client node in Testnet, we encourage you to update to this new version. The Testnet network upgrade will happen at block number 2,581,800. This is a non-mandatory upgrade for RSK Mainnet nodes.
This release contains enhancements to the node's JSON-RPC interface, as well as Ethereum compatibility fixes. It also introduces a consensus change for Testnet that increases the minimum block difficulty and avoids scenarios where a huge number of blocks would be mined in a short period of time if the difficulty dropped to the minimum levels (doesn't apply to Mainnet).
This is a summary of the changes included in this version:
pending
parameter in eth_getBlockByNumber
JSON-RPC method (#1627)eth_isSyncing
method which was not working as expected (#1618)eth_estimateGas
method (#1548)You can find a complete list of the changes introduced in Iris 3.2.0 milestone.
SHA256 (see Reproducible Build guide for further details): fe8432293600ba403e48e50253c5cdf322d8ec578b1984d17a26bf508a061c8a rskj-core-3.2.0-IRIS-all.jar
Go to Repo Go to ReleasePublished: 2022-01-24 10:03:34 UTC
A newer version is already available! Please don’t use this version anymore.
This is a follow-up release that temporarily deactivates the DAO needs to resync
popup to prevent presenting too many false positives to the user. It will be re-enabled again in the release after.
See https://github.com/bisq-network/bisq/commit/013dc982366ba348bcc8c179caad7dc498bc8535.
Here are the release notes from v1.8.1:
This release improves mediation, extends API capabilities (still in beta), and fixes lots of smaller issues across the board.
Edit offer
button in offer book for own offersfailtrade
, unfailtrade
keepfunds
to closetrade
getmyoffer
--payment-account-id
option name, document createcryptopaymentacct
getoffer
& gettrade
support for BSQ swapsNo new assets were added.
For a detailed description on how to verify your Bisq installer please have a look at our wiki: https://bisq.wiki/Downloading_and_installing#Verify_installer_file
Url of the signing key (Christoph Atteneder): https://bisq.network/pubkey/29CDFD3B.asc
Full fingerprint: CB36 D7D2 EBB2 E35D 9B75 500B CD5D C1C5 29CD FD3B
Import the key:
curl https://bisq.network/pubkey/29CDFD3B.asc | gpg --import
GPG prints a confusion warning: "This key is not certified with a trusted signature!" - See https://serverfault.com/questions/569911/how-to-verify-an-imported-gpg-key for background information what it means.
How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-1.8.2.dmg)
Verify jar file inside binary: You can verify on OSX the jar file with: shasum -a256 [PATH TO BISQ APP]/Bisq.app/Contents/app/desktop-1.8.2-all.jar The output need to match the value from the Bisq-1.8.2.jar.txt file.
There are three hashes within the Bisq-1.8.2.jar.txt file (macOS, Windows, Linux). If you want to reproduce and verify the hash of the jar file locally, you need to do so on Windows or Linux using Java 15.0.5 and the v1.8.2 release tag. Because of the signing and notarization process that requires the developer certificate used for the build on macOS it is not possible to create the same jar on macOS.
There is a known issue with Anti Virus software. We got several reports from users running into different problems. Either the AV software blocks Bisq or Tor, delete files in the data directory [2] or app directory [1]) or cause such a long delay at startup that Tor gets terminated and a file remains locked which can cause that Bisq cannot be started afterwards. To resolve that you need to restart Windows then the lock get released. We are working on solutions to fix those issues.
If you use Crypto currencies on your Windows system be aware that Windows is much more vulnerable to malware than Linux or OSX. Consider to use a dedicated non-Windows system when dealing with cryptocurrencies.
[1] Application directory (contains application installation files): C:\Users<username>\AppData\Local\Bisq
[2] Data directory (contains all Bisq data including wallet): C:\Users<username>\AppData\Roaming\Bisq\btc_mainnet\tor (you can delete everything except the hiddenservice directory)
Hint for Debian users:
If you have problems starting Bisq on Debian use: /opt/bisq/bin/Bisq
If your Linux distro does not support .deb files please follow this instruction:
cd ~/Downloads
mkdir tmp
cd tmp
ar x ../Bisq-64bit-1.8.2.deb
sudo tar Jxvf data.tar.xz
sudo cp -rp opt/Bisq /opt/
That instruction is not tested on many different distros. If you encounter problems please report it in a Github issue so we can improve it.
Thanks to everyone who directly contributed to this release:
- @alvasw
- @cbeams
- @cd2357
- @chimp1984
- @dbast
- @Emzy
- @ghubstan
- @jmacxx
- @KanoczTomas
- @MwithM
- @nutel65
- @ripcurlx
- @sqrrm
- @stejbac
- @xyzmaker123
A special thanks to our first time contributors: - @dbast - CI Security: Use Github actions via sha1 (not tags) and keep them updated via dependabot - Update Gradle wrapper to 7.3.3 - @nutel65 - Fixed annoying semicolon colors
As well as to everyone that helped with translations on Transifex.
Go to Repo Go to ReleasePublished: 2022-01-23 14:01:34 UTC
The full list of changes since 0.7.5-beta can be found here:
https://github.com/LN-Zap/zap-desktop/compare/v0.7.5-beta...v0.7.6-beta
Please refer to our documentation for instructions on how to verify the release.
Go to Repo Go to ReleasePublished: 2022-01-20 19:19:18 UTC
Invoice default expiry is still 1 week, but can now be modified in the payment options screen.
This is to prevent a frustrating scenario for the user where the app will let you overpay more than twice an invoice, even though we know the receiving node will most certainly reject the payment in accordance to BOLT11. (See #232)
You will need gpg
and our release signing key 7A73FE77DE2C4027. Note that you can get it:
- from our website: https://acinq.co/pgp/drouinf.asc
- from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys
To import our signing key:
$ gpg --import drouinf.asc
To verify the release file checksums and signatures:
$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped
Published: 2022-01-17 13:12:32 UTC
Umbrel 0.4.11 brings 4 brand new apps in the Umbrel App Store — ItchySats, Lightning Shell, Helipad, and SatSale, updated apps, latest Electrum server, performance improvements, bug fixes, and more.
Thanks to @prusnak and @tlindi for helping with the electrs update and @nevets963 for reporting missing JWT auth on some API endpoints 👏💜
Go to Repo Go to ReleasePublished: 2022-01-16 08:13:39 UTC
This release introduces a new design for our historical mempool chart legend and API documentation, and improves support for Bitcoin Core v22 and Taproot transactions, among many other enhancements and fixes. All users are encouraged to upgrade.
npm install --prod
by @wiz in https://github.com/mempool/mempool/pull/981ORDER BY id
=> ORDER BY added
by @nymkappa in https://github.com/mempool/mempool/pull/1119statistics.added
field for better query performances by @nymkappa in https://github.com/mempool/mempool/pull/1139Full Changelog: https://github.com/mempool/mempool/compare/v2.2.2...v2.3.0
Go to Repo Go to ReleasePublished: 2022-01-03 22:59:22 UTC
Published: 2022-01-03 16:40:56 UTC
https://github.com/romanz/electrs/blob/master/RELEASE-NOTES.md#094-dec-30-2021
Go to Repo Go to ReleasePublished: 2021-12-17 23:36:26 UTC
PaymentFailed
event is now provided to indicate a payment has failed
fully. This event is generated either after
ChannelManager::abandon_payment
is called for a given payment, or the
payment times out, and there are no further pending HTLCs for the payment.
This event should be used to detect payment failure instead of
PaymentPathFailed::all_paths_failed
, unless no payment retries occur via
ChannelManager::retry_payment
(#1202).KeysInterface::get_inbound_payment_key_material
(#1177).PaymentPathSuccessful
event has been added to ease passing success info
to a scorer, along with a Score::payment_path_successful
method to accept
such info (#1178, #1197).Score::channel_penalty_msat
has additional arguments describing the
channel's capacity and the HTLC amount being sent over the channel (#1166).Gossip
has been added, which is used for verbose
information generated during network graph sync. Enabling the
max_level_trace
feature or ignoring Gossip
log entries reduces log
growth during initial start up from many GiB to several MiB (#1145).allow_wallclock_use
feature has been removed in favor of only using
the std
and no-std
features (#1212).NetworkGraph
can now remove channels that we haven't heard updates for in
two weeks with NetworkGraph::remove_stale_channels{,with_time}
. The first
is called automatically if a NetGraphMsgHandler
is passed to
BackgroundProcessor::start
(#1212).InvoicePayer::pay_pubkey
was added to enable sending "keysend" payments to
supported recipients, using the InvoicePayer
to handle retires (#1160).user_payment_id
has been removed from PaymentPurpose
, and
ChannelManager::create_inbound_payment{,_for_hash}
(#1180).ChannelManager
functions to remove stale
references to panics which no longer occur (#1201).Score
and LockableScore
objects have moved into the
routing::scoring
module instead of being in the routing
module (#1166).Time
parameter to ScorerWithTime
is no longer longer exposed,
instead being fixed based on the std
/no-std
feature (#1184).ChannelDetails::balance_msat
was added to fetch a channel's balance
without subtracting the reserve values, lining up with on-chain claim amounts
less on-chain fees (#1203).UserConfig::accept_inbound_channels
flag is now provided,
removing the need to set min_funding_satoshis
to > 21 million BTC (#1173).ClosureReason::FundingTimedOut
(#1083).NetAddress::OnionV2
parsing was removed as version 2 onion services are no
longer supported in modern Tor (#1204).KeysInterface
, though no support for them exists in the channel itself (#1176)InvoicePayer
where paths may be retried after
the retry count has been exceeded. In this case the
Event::PaymentPathFailed::all_paths_failed
field is not a reliable payment
failure indicator. There was no acceptable alternative indicator,
Event::PaymentFailed
as been added to provide one (#1202).KeysManager::spend_spendable_outputs
no longer adds a change output that
is below the dust threshold for non-standard change scripts (#1131).ChannelMonitor
(#1143).FeeEstimator
that returns values rounded to the next
sat/vbyte may result in force-closures (#1208).ChannelManager::create_inbound_payment{,_for_hash}
will not be
receivable using versions prior to 0.0.104.
ChannelManager::create_inbound_payment{,_for_hash}_legacy
are provided for
backwards compatibility (#1177).PaymentPurpose::InvoicePayment::user_payment_id
will be 0 when reading
objects written with 0.0.104 when read by 0.0.103 and previous (#1180).In total, this release features 51 files changed, 5356 insertions, 2238 deletions in 107 commits from 9 authors, in alphabetical order: * Antoine Riard * Conor Okus * Devrandom * Duncan Dean * Elias Rohrer * Jeffrey Czyz * Ken Sedgwick * Matt Corallo * Valentine Wallace
Go to Repo Go to ReleasePublished: 2021-12-16 11:48:13 UTC
Published: 2021-12-15 06:49:39 UTC
Published: 2021-12-14 03:21:10 UTC
available
property of nodes returned by /api/v1/server/info wasn't actually set (ee1a034c0ab7744a2988e5da874084bc7dfa8b73) @NicolasDorierPublished: 2021-12-13 16:27:17 UTC
Published: 2021-12-13 11:59:12 UTC
Umbrel 0.4.10 brings a brand new app to the Umbrel App Store — Uptime Kuma, support for Boltz swaps in Ride The Lightning app, updated apps including the latest Lightning Terminal app which contains an important security fix, bug fixes, and more.
Thanks to @phaus for packaging Uptime Kuma and @aphex3k for bringing Boltz swaps to Ride The Lightning on Umbrel 👏💜
Go to Repo Go to ReleasePublished: 2021-12-12 21:14:45 UTC
The full list of changes since 0.7.4-beta can be found here:
https://github.com/LN-Zap/zap-desktop/compare/v0.7.4-beta...v0.7.5-beta
Please refer to our documentation for instructions on how to verify the release.
Go to Repo Go to ReleasePublished: 2021-12-10 18:25:56 UTC
A newer version is already available! Please don’t use this version anymore.
This release introduces BSQ swaps: an instant, trustless, and cheaper way to exchange BTC with BSQ. It also ships four new payment methods: ACH Transfer, Domestic Wire Transfer, Tikkie and TransferWise-USD. In addition, this release significantly reduces resources necessary for parsing DAO blocks. You'll find further improvements and bug fixes across the board!
For a detailed description on how to verify your Bisq installer please have a look at our wiki: https://bisq.wiki/Downloading_and_installing#Verify_installer_file
Url of the signing key (Christoph Atteneder): https://bisq.network/pubkey/29CDFD3B.asc
Full fingerprint: CB36 D7D2 EBB2 E35D 9B75 500B CD5D C1C5 29CD FD3B
Import the key:
curl https://bisq.network/pubkey/29CDFD3B.asc | gpg --import
GPG prints a confusion warning: "This key is not certified with a trusted signature!" - See https://serverfault.com/questions/569911/how-to-verify-an-imported-gpg-key for background information what it means.
How to verify signatures?
gpg --digest-algo SHA256 --verify BINARY{.asc*,}
Replace BINARY with the file you downloaded (e.g. Bisq-1.8.0.dmg)
Verify jar file inside binary: You can verify on OSX the jar file with: shasum -a256 [PATH TO BISQ APP]/Bisq.app/Contents/app/desktop-1.8.0-all.jar The output need to match the value from the Bisq-1.8.0.jar.txt file.
There are three hashes within the Bisq-1.8.0.jar.txt file (macOS, Windows, Linux). If you want to reproduce and verify the hash of the jar file locally, you need to do so on Windows or Linux using Java 15.0.5 and the v1.8.0 release tag. Because of the signing and notarization process that requires the developer certificate used for the build on macOS it is not possible to create the same jar on macOS.
There is a known issue with Anti Virus software. We got several reports from users running into different problems. Either the AV software blocks Bisq or Tor, delete files in the data directory [2] or app directory [1]) or cause such a long delay at startup that Tor gets terminated and a file remains locked which can cause that Bisq cannot be started afterwards. To resolve that you need to restart Windows then the lock get released. We are working on solutions to fix those issues.
If you use Crypto currencies on your Windows system be aware that Windows is much more vulnerable to malware than Linux or OSX. Consider to use a dedicated non-Windows system when dealing with cryptocurrencies.
[1] Application directory (contains application installation files): C:\Users<username>\AppData\Local\Bisq
[2] Data directory (contains all Bisq data including wallet): C:\Users<username>\AppData\Roaming\Bisq\btc_mainnet\tor (you can delete everything except the hiddenservice directory)
Hint for Debian users:
If you have problems starting Bisq on Debian use: /opt/bisq/bin/Bisq
If your Linux distro does not support .deb files please follow this instruction:
cd ~/Downloads
mkdir tmp
cd tmp
ar x ../Bisq-64bit-1.8.0.deb
sudo tar Jxvf data.tar.xz
sudo cp -rp opt/Bisq /opt/
That instruction is not tested on many different distros. If you encounter problems please report it in a Github issue so we can improve it.
Thanks to everyone who directly contributed to this release:
- @cbeams
- @cd2357
- @chimp1984
- @ghubstan
- @Jakub-CZ
- @jmacxx
- @m52go
- @ripcurlx
- @sqrrm
- @wiz
As well as to everyone that helped with translations on Transifex.
Go to Repo Go to ReleasePublished: 2021-12-10 06:36:47 UTC
Published: 2021-12-09 21:48:57 UTC
Dependabot updates and pinning unchained-libraries
Go to Repo Go to ReleasePublished: 2021-12-09 21:42:01 UTC
Dependabot updates and pinning unchained-libraries
Go to Repo Go to ReleasePublished: 2021-12-09 11:45:41 UTC
tr()
script expressions in UR:crypto-outputmaxServerTimeout
batchPageSize
Published: 2021-12-07 19:22:17 UTC
Changelog:
Published: 2021-11-30 11:39:32 UTC
There are two types of binaries:
It's a windowed GUI application with Specter server included. Supported platforms: Windows, MacOS, Linux (x86_64)
Note on Linux: you need to set up udev rules (included in the archive). Check out readme.
Note on macOS: The current build supports only macOS Catalina (10.15) or higher. If you'd like to run Specter on an older macOS version, you can install Specter from Pip.
It's a command-line program that only runs Specter server. Supported platforms: Windows, MacOS, Linux (x86_64)
SHA256SUMS file contains sha256 hashes of all binary files and signed with "Specter Signer's" GPG key.
You can get the public key from here.
Fingerprint of the key is 785A 2269 EE3A 9736 AC1A 4F4C 864B 7CF9 A811 FEF7
This key has been signed by @k9ert's key which you might have used for validating th 1.7.0 release.
no_wait
option to rpc calls #1485 (kdmukai)Published: 2021-11-27 13:22:11 UTC
Umbrel 0.4.9 brings two-factor authentication (2FA) to add an extra layer of security to your Umbrel, LND 0.14.1, two brand new apps in the Umbrel App Store — Tallycoin Connect and Syncthing, updated apps, bug fixes, and more.
Go to Repo Go to ReleasePublished: 2021-11-25 14:43:12 UTC
ADD: Log openURL error
FIX: Can't adjust multisig setting on 4" iPhone #4206
FIX: Rare crash on multisig wallet details screen
FIX: Use containedModal on macOS to unblock prompt UI
FIX: Pull-to-refresh on main screen
FIX: refresh lndhub wallet balance after paying for invoice by scanning qrcode on main screen
FIX: import custom derivation path with passphrase
FIX: 0 amounts in custom receive would result in undefined
FIX: lnPayURL scan wallet currency in BTC or local currency
FIX: Use haptic system settings for biometrics use
FIX: scroll index was being reset on focus
FIX: lightning address should now work with .onion addresses
FIX: Dont allow navigation to other screens when loading
DEL: Remove contextMenuHidden
TST: cosign with non-zero account (HD single-sig)
Published: 2021-11-24 23:33:17 UTC
This marks the first minor release of the 0.14.x
release cycle! This is primarily a bug fix release that fixes: an issue that would arise with lnd
nodes older than 2 years in certain circumstances, a fix to ensure we always advertise a consistent of feature bits, and most importantly a fix to ensure compatibility for new channel opens with the latest versions of c-lightning+eclair.
There are two database migrations for this version in lnd
(that were included in 0.14.0): One optimizes the storage structure of HTLCs for faster payments and the other removes old channel state data from closed channels to free up disk space. See the release notes v0.14.0-beta
(and v0.14.1-beta
) for more information.
NOTE: Compacting the DB is recommended after running the migration to reclaim the freed up space.
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 the keys that have signed this release if you haven't done so already:
curl https://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/guggero.asc | gpg --import
Once you have the required PGP keys, you can verify the release (assuming manifest-guggero-v0.14.1-beta.sig
and manifest-v0.14.1-beta.txt
are in the current directory) with:
gpg --verify manifest-guggero-v0.14.1-beta.sig manifest-v0.14.1-beta.txt
You should see the following if the verification was successful:
gpg: Signature made Wed 24 Nov 2021 11:15:46 PM CET
gpg: using RSA key F4FC70F07310028424EFC20A8E4256593F177720
gpg: Good signature from "Oliver Gugger <gugger@gmail.com>" [ultimate]
Primary key fingerprint: F4FC 70F0 7310 0284 24EF C20A 8E42 5659 3F17 7720
That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256
hash of the archive with shasum -a 256 <filename>
, compare it with the corresponding one in the manifest file, and ensure they match exactly.
From this new version onwards, in addition time-stamping the git tag with OpenTimeStamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-guggero-v0.14.1-beta.sig.ots
.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-guggero-v0.14.1-beta.sig.ots -f manifest-guggero-v0.14.1-beta.sig
Alternatively, the open timestamps website can be used to verify timestamps if one doesn't have a bitcoind
instance accessible locally.
These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.
Our release binaries are fully reproducible. Third parties are able to verify that the release binaries were produced properly without having to trust the release manager(s). See our reproducible builds guide for how this can be achieved.
The release binaries are compiled with go1.17.3
, which is required by verifiers to arrive at the same ones.
They include the following build tags: autopilotrpc
, signrpc
, walletrpc
, chainrpc
, invoicesrpc
, routerrpc
, watchtowerrpc
and monitoring
. Note that these are already included in the release script, so they do not need to be provided.
The make release
command can be used to ensure one rebuilds with all the same flags used for the release. If one wishes to build for only a single platform, then make release sys=<OS-ARCH> tag=<tag>
can be used.
Finally, you can also verify the tag itself with the following command:
$ git verify-tag v0.14.1-beta
gpg: Signature made Wed 24 Nov 2021 11:04:06 PM CET
gpg: using RSA key F4FC70F07310028424EFC20A8E4256593F177720
gpg: Good signature from "Oliver Gugger <gugger@gmail.com>" [ultimate]
Primary key fingerprint: F4FC 70F0 7310 0284 24EF C20A 8E42 5659 3F17 7720
To verify the lnd
and lncli
binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):
shell
$ docker run --rm --entrypoint="" lightninglabs/lnd:v0.14.1-beta /verify-install.sh v0.14.1-beta
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/lnd [command-line options]
Users are able to rebuild the target release themselves without having to fetch any of the dependencies. In order to do so, assuming
that vendor.tar.gz
and lnd-source-v0.14.1-beta.tar.gz
are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf lnd-source-v0.14.1-beta.tar.gz
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.14.1-beta" ./cmd/lnd
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.14.1-beta" ./cmd/lncli
The -mod=vendor
flag tells the go build
command that it doesn't need to fetch the dependencies, and instead, they're all enclosed in the local vendor directory.
Additionally, it's now possible to use the enclosed release.sh
script to bundle a release for a specific system like so:
make release sys="linux-arm64 darwin-amd64"
⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️
Read the full release notes here: https://github.com/lightningnetwork/lnd/blob/master/docs/release-notes/release-notes-0.14.0.md and here: https://github.com/lightningnetwork/lnd/blob/master/docs/release-notes/release-notes-0.14.1.md
Abubakar Nur Khalil Adrian-Stefan Mares Alex Bosworth Alyssa Hertig András Bánki-Horváth Bjarne Magnussen Carla Kirk-Cohen Carsten Otto Conner Fromknecht Elle Mouton ErikEk Eugene Siegel Hampus Sjöberg Harsha Goli Jamie Turley Jesse de Wit Johan T. Halseth Johnny Holton Joost Jager Jordi Montes Juan Pablo Civile Kishin Kato Leonhard Weese Martin Habovštiak Michael Rhee Naveen Srinivasan Olaoluwa Osuntokun Oliver Gugger Priyansh Rastogi Roei Erez Simon Males Stevie Zollo Torkel Rogstad Wilmer Paulino Yong Yu Zero-1729 benthecarman de6df1re github2k20 mateuszmp nathanael nayuta-ueno offerm positiveblue xanoni
Go to Repo Go to ReleasePublished: 2021-11-20 13:53:08 UTC
Published: 2021-11-19 21:05:07 UTC
https://github.com/romanz/electrs/blob/master/RELEASE-NOTES.md#093-nov-20-2021
Go to Repo Go to ReleasePublished: 2021-11-17 21:22:27 UTC
lnd
0.14.0 has a known issue regarding channel negotiation (e.g. opening channels) with other Lightning implementations. Please upgrade to lnd
0.14.1 which mitigates this issue.
There are two database migrations for this version in lnd
: One optimizes the storage structure of HTLCs for faster payments and the other removes old channel state data from closed channels to free up disk space. See the release notes for more information.
NOTE: Compacting the DB is recommended after running the migration to reclaim the freed up space.
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 the keys that have signed this release if you haven't done so already:
curl https://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import
Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.14.0-beta.sig
and manifest-v0.14.0-beta.txt
are in the current directory) with:
gpg --verify manifest-roasbeef-v0.14.0-beta.sig manifest-v0.14.0-beta.txt
You should see the following if the verification was successful:
gpg: Signature made Wed Nov 17 13:20:26 2021 PST
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]
That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256
hash of the archive with shasum -a 256 <filename>
, compare it with the corresponding one in the manifest file, and ensure they match exactly.
From this new version onwards, in addition time-stamping the git tag with OpenTimeStamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.14.0-beta.txt.asc.ots
.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.14.0-beta.sig.ots -f manifest-roasbeef-v0.14.0-beta.sig
Alternatively, the open timestamps website can be used to verify timestamps if one doesn't have a bitcoind
instance accessible locally.
These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.
Our release binaries are fully reproducible. Third parties are able to verify that the release binaries were produced properly without having to trust the release manager(s). See our reproducible builds guide for how this can be achieved.
The release binaries are compiled with go1.17.3
, which is required by verifiers to arrive at the same ones.
They include the following build tags: autopilotrpc
, signrpc
, walletrpc
, chainrpc
, invoicesrpc
, routerrpc
, watchtowerrpc
and monitoring
. Note that these are already included in the release script, so they do not need to be provided.
The make release
command can be used to ensure one rebuilds with all the same flags used for the release. If one wishes to build for only a single platform, then make release sys=<OS-ARCH> tag=<tag>
can be used.
Finally, you can also verify the tag itself with the following command:
$ git verify-tag v0.14.0-beta
gpg: Signature made Wed 17 Nov 2021 08:04:23 PM UTC using RSA key ID 9B280306
gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>"
To verify the lnd
and lncli
binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):
shell
$ docker run --rm --entrypoint="" lightninglabs/lnd:v0.14.0-beta /verify-install.sh v0.14.0-beta
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/lnd [command-line options]
Users are able to rebuild the target release themselves without having to fetch any of the dependencies. In order to do so, assuming
that vendor.tar.gz
and lnd-source-v0.14.0-beta.tar.gz
are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf lnd-source-v0.14.0-beta.tar.gz
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.14.0-beta" ./cmd/lnd
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.14.0-beta" ./cmd/lncli
The -mod=vendor
flag tells the go build
command that it doesn't need to fetch the dependencies, and instead, they're all enclosed in the local vendor directory.
Additionally, it's now possible to use the enclosed release.sh
script to bundle a release for a specific system like so:
make release sys="linux-arm64 darwin-amd64"
⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️
Read the full release notes here: https://github.com/lightningnetwork/lnd/blob/master/docs/release-notes/release-notes-0.14.0.md
Abubakar Nur Khalil Adrian-Stefan Mares Alex Bosworth Alyssa Hertig András Bánki-Horváth Bjarne Magnussen Carla Kirk-Cohen Carsten Otto Conner Fromknecht Elle Mouton ErikEk Eugene Siegel Hampus Sjöberg Harsha Goli Jesse de Wit Johan T. Halseth Johnny Holton Joost Jager Jordi Montes Juan Pablo Civile Kishin Kato Leonhard Weese Martin Habovštiak Michael Rhee Naveen Srinivasan Olaoluwa Osuntokun Oliver Gugger Priyansh Rastogi Roei Erez Simon Males Stevie Zollo Torkel Rogstad Wilmer Paulino Yong Yu Zero-1729 benthecarman de6df1re github2k20 mateuszmp nathanael offerm positiveblue xanoni
Go to Repo Go to ReleasePublished: 2021-11-15 13:57:07 UTC
Published: 2021-11-15 13:45:11 UTC
Umbrel 0.4.8 brings a new security feature — unique cryptographically secure default app passwords derived from your 24 secret words. This will help protect your Umbrel even if an app's unique Tor URL gets leaked and you have not changed that app's default password.
If you have currently installed ThunderHub, Lightning Terminal, Ride The Lightning, Squeaknode or Code Server on your Umbrel, their default passwords will automatically upgrade to the newer, more secure passwords which can be found on their app store listing pages. In case you have already updated passwords of these apps manually, you can continue to use the same.
Go to Repo Go to ReleasePublished: 2021-11-11 19:27:21 UTC
Published: 2021-11-10 12:22:19 UTC
This version of Umbrel brings LND 0.13.4 and updated apps (BTCPay Server, Specter Desktop, Pi-hole, Lightning Terminal, and more) to the Umbrel App Store.
LND 0.13.4 fixes a bug discovered in the previous version which will break Neutrino functionality after the Taproot activation in ~3 days. Because Neutrino is only used when Bitcoin Core is still syncing, in short: if Bitcoin Core on your Umbrel hasn't finished syncing, please update immediately. If Bitcoin Core on your Umbrel is 100% synced already, you remain unaffected by this bug and can update at your convenience.
Go to Repo Go to ReleasePublished: 2021-11-09 19:19:31 UTC
This is a small patch release that fixes a Taproot related bug for Neutrino. If you run neutrino in production, we strongly recommend you update to this version before Taproot activation to ensure your node keeps moving forward in the chain.
This release only contains a single commit on top of the prior 0.13.3 minor release: https://github.com/lightningnetwork/lnd/compare/0-13-3-branch...0-13-4-branch?expand=1
This release does not contain any database migrations.
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 the keys that have signed this release if you haven't done so already:
curl https://keybase.io/bitconner/pgp_keys.asc | gpg --import
curl https://keybase.io/roasbeef/pgp_keys.asc | gpg --import
Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.13.4-beta.sig
and manifest-v0.13.4-beta.txt
are in the current directory) with:
gpg --verify manifest-roasbeef-v0.13.4-beta.sig manifest-v0.13.4-beta.txt
You should see the following if the verification was successful:
gpg: Signature made Wed Sep 30 17:35:20 2020 PDT
gpg: using RSA key 4AB7F8DA6FAEBB3B70B1F903BC13F65E2DC84465
gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]
That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256
hash of the archive with shasum -a 256 <filename>
, compare it with the corresponding one in the manifest file, and ensure they match exactly.
From this new version onwards, in addition time-stamping the git tag with OpenTimeStamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.13.4-beta.txt.asc.ots
.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.13.4-beta.sig.ots -f manifest-roasbeef-v0.13.4-beta.sig
Alternatively, the open timestamps website can be used to verify timestamps if one doesn't have a bitcoind
instance accessible locally.
These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.
Our release binaries are fully reproducible. Third parties are able to verify that the release binaries were produced properly without having to trust the release manager(s). See our reproducible builds guide for how this can be achieved.
The release binaries are compiled with go1.16.3
, which is required by verifiers to arrive at the same ones.
They include the following build tags: autopilotrpc
, signrpc
, walletrpc
, chainrpc
, invoicesrpc
, routerrpc
, watchtowerrpc
and monitoring
. Note that these are already included in the release script, so they do not need to be provided.
The make release
command can be used to ensure one rebuilds with all the same flags used for the release. If one wishes to build for only a single platform, then make release sys=<OS-ARCH> tag=<tag>
can be used.
Finally, you can also verify the tag itself with the following command:
$ git verify-tag v0.13.4-beta
gpg: Signature made Tue Sep 15 18:55:00 2020 PDT
gpg: using RSA key 4AB7F8DA6FAEBB3B70B1F903BC13F65E2DC84465
gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]
To verify the lnd
and lncli
binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):
shell
$ docker run --rm --entrypoint="" lightninglabs/lnd:v0.13.4-beta /verify-install.sh v0.13.4-beta
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/lnd [command-line options]
Users are able to rebuild the target release themselves without having to fetch any of the dependencies. In order to do so, assuming
that vendor.tar.gz
and lnd-source-v0.13.4-beta.tar.gz
are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf lnd-source-v0.13.4-beta.tar.gz
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.13.4-beta" ./cmd/lnd
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.13.4-beta" ./cmd/lncli
The -mod=vendor
flag tells the go build
command that it doesn't need to fetch the dependencies, and instead, they're all enclosed in the local vendor directory.
Additionally, it's now possible to use the enclosed release.sh
script to bundle a release for a specific system like so:
make release sys="linux-arm64 darwin-amd64"
⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️
This release bumps the Neutrino dependency to the version that ignores not yet supported Taproot outputs in downloaded blocks.
Olaoluwa Osuntokun
Go to Repo Go to ReleasePublished: 2021-11-09 15:25:46 UTC
Published: 2021-11-05 20:09:19 UTC
There are two types of binaries:
It's a windowed GUI application with Specter server included. Supported platforms: Windows, MacOS, Linux (x86_64)
Note on Linux: you need to set up udev rules (included in the archive). Check out readme.
Note on macOS: The current build supports only macOS Catalina (10.15) or higher. If you'd like to run Specter on an older macOS version, you can install Specter from Pip.
It's a command-line program that only runs Specter server. Supported platforms: Windows, MacOS, Linux (x86_64)
SHA256SUMS file contains sha256 hashes of all binary files and signed with "Specter Signer's" GPG key.
You can get the public key from here.
Fingerprint of the key is 785A 2269 EE3A 9736 AC1A 4F4C 864B 7CF9 A811 FEF7
Published: 2021-11-05 03:38:10 UTC
Published: 2021-11-04 15:38:13 UTC
This feature include a critical security patch. The vulnerability impacts owner of shared instances which share their internal lightning nodes. Credits to @yilakb to have noticed us.
Published: 2021-11-03 17:48:57 UTC
We're pleased to announce the 0.10.2 release of c-lightning, named by @vincenzopalazzo.
This is a recommended upgrade: this release includes the patch for the recently disclosed CVE-2021-41592.
close
now reports the feeranges each side enforced, which allows users to determine which side caused a high or low feerate.setchannelfee
now has a grace period during which both old and new fee policies are considered. This prevents a fee update from making the channel unusable until the update propagated.datastore
, deldatastore
, and listdatastore
) exposes a simple key-value store, allowing plugin authors to store data in the c-lightning database.ping
now only works if we have a channel with the peer.More details can be found in the changelog.
Thanks to everyone for their contributions and bug reports; please keep them coming.
Since 0.10.1, we've had 333 commits from 19 different authors over 85 days.
A special thanks goes to the 4 first time contributors:
Cheers, Christian, Rusty, Lisa.
Go to Repo Go to ReleasePublished: 2021-11-03 03:33:02 UTC
lightning-invoice
crate - the InvoicePayer
. InvoicePayer
is a
struct which takes a reference to a ChannelManager
and a Router
and retries payments as paths fail. It limits retries to a configurable
number, but is not serialized to disk and may retry additional times across
a serialization/load. In order to learn about failed payments, it must
receive Event
s directly from the ChannelManager
, wrapping a
user-provided EventHandler
which it provides all unhandled events to
(#1059).get_route
has been renamed find_route
(#1059) and now takes a
RouteParameters
struct in replacement of a number of its long list of
arguments (#1134). The Payee
in the RouteParameters
is stored in the
Route
object returned and provided in the RouteParameters
contained in
Event::PaymentPathFailed
(#1059).ChannelMonitor
s must now be persisted after calls that provide new block
data, prior to MonitorEvent
s being passed back to ChannelManager
for
processing. If you are using a ChainMonitor
this is handled for you.
The Persist
API has been updated to Option
ally take the
ChannelMonitorUpdate
as persistence events that result from chain data no
longer have a corresponding update (#1108).routing::Score
now has a payment_path_failed
method which it can use to
learn which channels often fail payments. It is automatically called by
InvoicePayer
for failed payment paths (#1144).Scorer
implementation is now a type alias to a type generic
across different clocks and supports serialization to persist scoring data
across restarts (#1146).Event::PaymentSent
now includes the full fee which was spent across all
payment paths which were fulfilled or pending when the payment was fulfilled
(#1142).Event::PaymentSent
and Event::PaymentPathFailed
now include the
PaymentId
which matches the PaymentId
returned from
ChannelManager::send_payment
or InvoicePayer::pay_invoice
(#1059).NetGraphMsgHandler
now takes a Deref
to the NetworkGraph
, allowing for
shared references to the graph data to make serialization and references to
the graph data in the InvoicePayer
's Router
simpler (#1149).routing::Score::channel_penalty_msat
has been updated to provide the
NodeId
of both the source and destination nodes of a channel (#1133).ChannelMonitor
was persisted on disk), but the
ChannelManager
was not persisted prior to shutdown/crash, no
Event::PaymentPathFailed
event was generated if the HTLC was eventually
failed on chain. Events are now consistent irrespective of ChannelManager
persistence or non-persistence (#1104).Route
was generated using a previous version or for
which the payment was originally sent by a previous version of the library
will not be retried by an InvoicePayer
.This release was singularly focused and some contributions by third parties were delayed. In total, this release features 38 files changed, 4414 insertions, and 969 deletions in 71 commits from 2 authors, in alphabetical order:
Want to add another project? Make a PR!