Weekly Edition for Thursday, Feb 7

Card Shuffle to Bitcoin Seed
Bitcoin seed generation is the most important event for any Bitcoin holder, as without this seed your wallet and ultimately your money is lost. We as users trust hardware and air gapped wallets to be correct and honest in their seed generation, which is hard to verify. A new bring-your-own-entropy method was proposed on the Bitcoin dev mailing list by developer Ryan Havar to allow users to create randomness they trust.
The Bitcoin Developer Network (BDN) Is Looking for Contributors

The Bitcoin Developer Network (BDN) aims to become a community-driven project looking at educating the next wave of Bitcoin developers. This is a public invitation for developers, authors, editors, proofreaders, enthusiasts and technical writers to get in touch so that we may reduce the barrier to entry in developing solutions at various layers of this technology.

Considering it’s a community-driven initiative, it only seems fair to do this collaboratively.

Get in touch at inbox@bitcoindev.network


Chaincode Labs Is Hosting Its Fourth Residency Program in Midtown Manhattan Over Summer 2019
Chaincode Labs announced its fourth residency program that will take place in Midtown Manhattan over summer 2019. Read the full announcement here Supporting the developer community and helping new contributors get their start in Bitcoin protocol development is a key part of our mission. Over the past three years, our residency programs have helped many developers start contributing to Bitcoin projects. Alex Bosworth and Johan Halseth (Lightning Labs), Neha Narula (MIT DCI), James O’Beirne and John Newbery (Chaincode Labs), Chris Stewart (SuredBits), Pierre Rochard (Lightning Node Launcher), Rene Pickhardt (LN developer and educator) and Will O’Beirne (Lightning Joule and WebLN) are all Chaincode Residency alumni.



project release date
lightning-peach-wallet v0.4.2-mainnet-beta

LightningPeach wallet v0.4.2-mainnet-beta

Release notes:

  • We have added a possibility to increase an amount of payment requests. It means that now you can add some tips to scanned payment requests. Such service as tippin.me also becomes available.
  • The Privacy Policy document has been updated.

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 LighntingPeach Wallet’s key if you haven’t done so already:

curl "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x3B50C645039078ED" | gpg --import

Once you have LighntingPeach Wallet’s PGP key you can verify the release (assuming manifest-v0.4.2-mainnet-beta.txt and manifest-v0.4.2-mainnet-beta.txt.sig are in the current directory) with:

gpg --verify manifest-v0.4.2-mainnet-beta.txt.sig

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries and executables you’ve downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary or executable, and compare that with the following hashes (which are included in the manifest file):

b9f7f74b549be6d15872912115649ec3454de605a7f13015b083d8181c2a69de  lightning-peach-wallet_0.4.2-mainnet-beta_amd64.deb
f1fcef32ef0f2e600ca1d4987a1a4520f550d297c154869bded8a845cadf751e  lightning-peach-wallet-0.4.2-mainnet-beta.dmg
cc4dee17b928e11874407d9934754765a285b7255580f8e4a2659eccfbae2acc  lightning-peach-wallet-0.4.2-mainnet-beta.exe
a2a04fd8f710f3821f80e9da47a6595c3c45a89ce01857583d3975a53ce20c99  lightning-peach-wallet-0.4.2-mainnet-beta-mac.zip
5ecf14bb130f7244bcb2e22c7bc92926f041e39f14d6a3fc737b874c06f36164  lightning-peach-wallet-0.4.2-mainnet-beta-x86_64.AppImage
d3351faa811e319827b88df3422216287b234ae966dfbba27a6a92032cc25b13  lightning-peach-wallet-setup-0.4.2-mainnet-beta.exe

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



type rfc # title date status
bolt transactions BOLT 3: add test vectors for htlc-transactions in case where CLTV is used as tie-breaker for sorting 2019-02-06 Update
bolt routing gossip BOLT 7: add extended channel queries 2019-02-06 Closed
slip X Add Snowblossom 2019-02-06 Merged
bolt X WIP: Dual Funding (v2 Channel Establishment protocol) 2019-02-06 Update
bolt X WIP: First draft of option_simplfied_commitment: 2019-02-05 Update
bolt X Access to the minutes of the IRC meetings? 2019-02-05 Closed
bolt onion routing BOLT 4: Correct "16-byte" to "12-byte" (padding) 2019-02-05 Merged
bolt X Rephrase Forwarding HTLCs Requirements 2019-02-05 Merged
bolt X Clarify ownership of max_htlc limits at receiving update_add_htlc 2019-02-04 Merged
bolt X Specify OP_DATA to express accepted/offered_htlc_script with same 2019-02-04 Merged
bolt X option_data_loss_protect: concretely define `my_current_per_commitment_point` 2019-02-04 Update
bolt X Recurring Payments 2019-02-04 Update
bolt X Agenda for 2019-02-04 2019-02-04 Update
bolt X Demand revoke_and_ack before more updates 2019-02-04 Update
slip X Add Energy Web 2019-02-04 Merged
bolt X When does receiver revoke? 2019-02-04 New Issue
bolt routing gossip BOLT7: reply_channel_range parameter 2019-02-04 Update
bolt X Keep HMAC case consistent 2019-02-04 Update
bolt X Add last per_hop padding 2019-02-04 Update
bolt onion routing BOLT 4: Clarify final_incorrect_cltv_expiry data 2019-02-04 Update
bolt routing gossip BOLT7: extend channel range queries with optional fields 2019-02-04 Update
bolt X limit `max_value_in_flight` to channel capacity. 2019-02-01 Closed
slip slip-0044 slip44: Add IoTE 2019-02-07 Merged