Skip to content

v0.2.1-alpha
Compare
Choose a tag to compare
@carlaKC carlaKC released this 15 Sep 08:14
· 233 commits to master since this release
v0.2.1-alpha
This tag was signed with the committer’s verified signature.
carlaKC Carla Kirk-Cohen
GPG key ID: 4CA7FE54A6213C91
Learn about vigilant mode.
9391f27
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Release Notes

Accounting Reports

This Faraday release contains full accounting reports for on-chain and off-chain transactions produced by lnd. This much-requested feature provides node operators and business building on Lightning to produce a full report of their node’s activity, and better account for their operational expenses and movement of funds. The report is specifically lightning focused, separating transactions such as circular rebalances and on channel transactions into their own categories. The Harmony reporting standard is used for these reports, and they can be conveniently exported to a csv file using frcli audit --csvdir={location}. Please see our full accounting documentation for details.

Authentication and Transport Security

Faraday’s grpc and REST endpoints are now encrypted with TLS and secured with macaroon authentication, as is the case for lnd. A single macaroon, faraday.macaroon, and the TLS cert/key pair are stored in ~/.faraday/<network>/faraday.macaroon (or /Users/<username>/Library/ApplicationSupport/Faraday/<network> on mac) by default. Note that the macaroon and cert pair are separate to those used by lnd.

The --faradaydir flag can be used to set a different location for the macaroon and cert pair, or they can be individually set using --tlscertpath, --tlskeypath and --macaroondir. If you are running on mainnet, frcli will automatically look for the cert and macaroon in the default path. However, if you are running on regtest or testnet, the --network flag is required to point Faraday to the correct directory.

Bug Fixes

A bug in the pagination used by insights endpoint to query lnd for forwarding events which was triggered for nodes with > 2000 forwards has been fixed.

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 carlakirkcohen's key from keybase:

curl https://keybase.io/carlakirkcohen/pgp_keys.asc | gpg --import

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

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

You should see the following if the verification was successful:

gpg: assuming signed data in 'manifest-v0.2.1-alpha.txt'
gpg: Signature made Thu Mar 19 09:19:19 2020 SAST
gpg:                using RSA key 15E7ECF257098A4EF91655EB4CA7FE54A6213C91
gpg: Good signature from "Carla Kirk-Cohen <[email protected]>" [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.2.1-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.2.1-alpha

Contributors (Alphabetical Order)

Carla Kirk-Cohen
Joost Jager
Oliver Gugger
saubyk

Assets 26
Loading