Skip to content

Releases: benthecarman/PSBT-Toolkit

PSBT Toolkit v0.1.2

03 Dec 01:44
129e6e0
Compare
Choose a tag to compare

Release Notes

  • Various Improvements to PSBT parsing (no longer requires previous transaction)
  • Added ability to decode and analyze PSBT
  • Added new Script Pub Key crafter
  • Fixed bug when closing app

Running PSBT Toolkit

To run PSBT Toolkit you will need Java installed, checkout the beginning instructions about building from source for help.

If you want to run the standalone binaries, after verifying PGP signatures, you can run it with ./psbt-toolkit to start the app. If you are on Windows it will instead need to run psbt-toolkit.exe or if just want to execute the jar you can generally just double click it, or use java -jar psbt-toolkit.jar.

Verifying signatures

This release is signed with benthecarman's signing key with fingerprint 0AD83877C1F0CD1EE9BD660AD7CC770B81FD22A8

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 it's file name.
After doing that you can use gpg --verify to authenticate the signature.

Example:

$ sha256sum psbt-toolkit
87e0c0274b9a32703b5adfdc48e7d46641c6de13d9b43baec2886f34fcb010b1 psbt-toolkit
$ gpg --verify SHA256SUMS.asc 
gpg: Signature made Wed 02 Dec 2020 07:25:37 PM CST
gpg:                using RSA key 0AD83877C1F0CD1EE9BD660AD7CC770B81FD22A8
gpg: Good signature from "Ben Carman <benthecarman@live.com>" 

PSBT Toolkit v0.1.1

10 Aug 03:35
625c654
Compare
Choose a tag to compare

Release Notes

  • Various Improvements to PSBT parsing
  • Adds ability to fetch relevant PSBT data from blockstream.info (clearnet be careful)
  • New Transaction Builder
  • New Crypto Tab that allows for signing and hashing arbitrary data

Running PSBT Toolkit

To run PSBT Toolkit you will need Java installed, checkout the beginning instructions about building from source for help.

If you want to run the standalone binaries, after verifying PGP signatures, you can run it with ./psbt-toolkit to start the app. If you are on Windows it will instead need to run psbt-toolkit.exe or if just want to execute the jar you can generally just double click it, or use java -jar psbt-toolkit.jar.

Verifying signatures

This release is signed with benthecarman's signing key with fingerprint 0AD83877C1F0CD1EE9BD660AD7CC770B81FD22A8

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 it's file name.
After doing that you can use gpg --verify to authenticate the signature.

Example:

$ sha256sum psbt-toolkit
81f29d358597ee6ccddc56ff742d34de0937859b0c6c6f064a3efdc2bd263c1f psbt-toolkit
$ gpg --verify SHA256SUMS.asc 
gpg: Signature made Sun 09 Aug 2020 10:19:16 PM CDT
gpg:                using RSA key 0AD83877C1F0CD1EE9BD660AD7CC770B81FD22A8
gpg: Good signature from "Ben Carman <benthecarman@live.com>"

PSBT Toolkit v0.1.0

07 Jul 13:55
f6121ed
Compare
Choose a tag to compare

Running PSBT Toolkit

To run PSBT Toolkit you will need Java installed, checkout the beginning instructions about building from source for help.

If you want to run the standalone binaries, after verifying PGP signatures, you can run it with ./psbt-toolkit to start the app. If you are on Windows it will instead need to run psbt-toolkit.exe or if just want to execute the jar you can generally just double click it, or use java -jar psbt-toolkit.jar.

Verifying signatures

This release is signed with benthecarman's signing key with fingerprint 0AD83877C1F0CD1EE9BD660AD7CC770B81FD22A8

To do the verification, first use sha256sum on the file you will be using.
You should check that the result is listed in the SHA256SUMS.asc file next to it's file name.
After doing that you can use gpg --verify to authenticate the signature.

Example:

$ sha256sum psbt-toolkit
8230313a79ecebb86b013dca9a6beb0f8558f6d6e90a870e43457f3f491f911b  psbt-toolkit
$ gpg --verify SHA256SUMS.asc
gpg: Signature made Tue 07 Jul 2020 08:34:26 AM CDT
gpg:                using RSA key 0AD83877C1F0CD1EE9BD660AD7CC770B81FD22A8
gpg: Good signature from "Ben Carman <benthecarman@live.com>"