v0.2.2-alpha

Release Notes

Custom Accounting Cateogories

This minor release contains the addition of custom reporting categories in the audit endpoint. These categories can be used to identify custom groups of transactions within your accounting report. The labels on lnd's on-chain transactions and invoices are used to match transactions against a set of regexes which identify a transaction as belonging in a custom group. At present, there is no labeling for off-chain payments and forwards, so they cannot be included in these categories.

When using the cli, categories should be specified as a json array:

./frcli audit --categories='[
		{ 
			"name": "test", 
			"on_chain": true, 
			"off_chain": false, 
			"label_patterns": ["test[0-9]*", "example(1|2)"] 
		},
		{
			...
		},
	]'

A default category for transactions involved in Lightning Loop swaps is included in the cli, and can be included in reports by using the --loop-category flag.

Bug Fixes

• A bug in the exchangerates api that would panic if no timestamps were provided was 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.2-alpha.txt and manifest-v0.2.2-alpha.txt.sig are in the current directory) with:

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

You should see the following if the verification was successful:

gpg: assuming signed data in 'manifest-v0.2.2-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 <kirkcohenc@gmail.com>" [ultimate]

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

cat manifest-v0.2.2-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.2-alpha

Contributors (Alphabetical Order)

André Neves
Carla Kirk-Cohen
Oliver Gugger