Weekly Edition for Thursday, Jan 31

Simple Proof of Reserves Transactions

Proof-of-reserve transactions are transactions provided by a certain custodian to prove ownership for an amount of funds. For example, lets say an Exchange currently holds 30 thousand Bitcoins on behalf of its users, if anything happens to the exchange, say a hack, the exchange might need to prove to its customers that their Bitcoin is in safe hands, currently any company that wants to perform a proof-of-reserve must do it in its own way and accordingly, their users have to understand the construction to be able to verify it, this makes the process not very common among custodian companies as it’s both tiresome and would require educating their users on technical terms.

A new BIP was proposed as a way to formalize a standard format for constructing these proofs, making it easier for custodians and users with existing wallet infrastructures to understand these proofs. Proofs are formatted as a regular Bitcoin transaction with small differences. This transaction must be unspendable as its sole purpose is to demonstrate the availability of the funds, not spending them. The proof must be linked to the issuer, preventing custodians from just copying other custodians’ proofs.

Unification of Feature Bits

We’ve talked about feature bits before. They are bits that nodes look for in other nodes communication to check if they support a certain feature they’re looking to use.

A proposal was suggested by developer Rusty Russels with a few amends to the implementation of feature bits. It consists of renaming local features to peer features and global features to routing features and having them share a number space so they don’t overlap. Then we can put both ‘features’ in node announcements but never using even bits for peer features.

This facilitates using node_announcement as both connecting to a peer that supports a certain feature and asking the question “can I route through this node?”. Further discussions are available on the mailing list here.

Newsletters

Releases

project release date
ledger-live-desktop v1.3.4
🐛 This release contains important bug fixes. 🐛

General

  • Fix a UI glitch displaying miscalculated or negative fees in operation details and send flow.
  • Allow Ledger Live to display notifications for crypto asset events.
  • Added two more platforms to buy crypto: BTC-Direct and Coinberry.
  • Minor improvements in UI.
  • Prepare future support of XSN and KMD through Sapling.
  • ETH and ETC: scan for Metamask accounts.
  • DCR: fix transaction bug affecting some users.
  • HSR and POSW: blockchain synchronization and send feature fixed.
  • Other crypto assets: fix “getVarint” errors for various assets.
2019-01-29
bitcoinjs-lib v4.0.3

4.0.3

fixed - Fixed TransactionBuilder to require that the Transaction has outputs before signing (#1151) - Fixed payments.p2sh, which now takes the network from the redeem attribute if one is not given in the object argument (#1232) - Fixed Block.calculateTarget to allow for exponents up to 29 (#1285) - Fixed some low priority rarely occurring bugs with multisig payments and TransactionBuilder multisig processing (#1307)

added - Regtest network object to networks (#1261)

2019-01-30
bitcoinjs-lib v4.0.3 2019-01-25

RFC

type rfc # title date status
bip X fixed minor typo 2019-01-29 New PR
bip bip-0143 Typo of test data in bip 143 2019-01-29 Update
slip X add swtc coin 2019-01-28 Merged
slip slip-0044 [slip-0044] Add Snowblossom Coin Type(s) 2019-01-28 Closed
slip X Add MOAC coin at 314 (0x8000013a) 2019-01-28 Merged
slip slip-0044 SLIP-0044 - Duplicate ticker symbols 2019-01-28 Closed
bip bip-0079 fix typos in bip79 2019-01-27 Update
bip bip-0039 Add Slovenian wordlist for BIP0039 2019-01-27 Update
bip bip-0079 Fix mistake in bip-0079 2019-01-27 Update
bolt X Sighash type unspecified 2019-01-31 Closed