Users can top-up their rewards cards with several major cryptos including Bitcoin (BTC), Binance USD (BUSD), Binance Coin (BNB) and Ontology (ONT). Purchasing the Binance coin itself looks like a good investment for the future as the exchange plans to use their profits to buy back a portion of the coins every quarter and destroy them: hence decreasing the supply and making them more valuable for holders. Gregory Maxwell asks and answers a question about you could create a value that looked like an ECDSA signature corresponding to an arbitrary public key-such as one known to belong to Satoshi Nakamoto-but without having access to the private key. Pieter Wuille and Gregory Maxwell each answer a question about using Bitcoin private and public keys for encryption rather than their typical use for signing and verification. ● Two papers published on fast multiparty ECDSA: in multiparty ECDSA, two or more parties can cooperatively (but trustlessly) create a single public key that requires the parties also cooperate to create a single valid signature for youtu.be blog entry that pubkey. 14424: Fixes a likely regression in 0.17.0 for watch-only wallets that require users to import their public keys for multisig scripts (rather than just importing the script) in order for Bitcoin Core to attempt spending the script using RPCs such as fundrawtransaction with the includeWatching flag.</<br>r>
● Help test Bitcoin Core 0.17.1RC1: the first release candidate for this maintenance release has been uploaded. To the user, these will look no different than the built-in methods, including appearing in the list of supported methods returned by the help RPC. Unless there is a dramatic new change in hashrate during the next week, a difficulty adjustment is expected around Sunday that will mitigate most of the recent hashrate reductions. It is recalculated every 2016 blocks to a value such that the previous 2016 blocks would have been generated in exactly two weeks had everyone been mining at this difficulty. With this patch, your node will reject requests from an attacker to lock his funds and your funds for a period of more than 5,000 blocks (about 5 weeks). Upon upgrading, a rescan on the block chain will be performed so that the missing accounting information is recovered and your correct balance will be displayed. This release also fixes an accounting bug for users of the btcwallet backend where not all change payments to yourself may have been reflected in your displayed balance.
● Modern block explorer open sourced: after recently announcing a new block explorer website, Blockstream has announced the open source release of both its backend and frontend code. Notable code changes this week in Bitcoin Core, LND, C-lightning, and libsecp256k1. Although this particular tool mirrors functionality already provided by the lnwallet.Signer service, the mechanism used to enable this new service makes it possible for developers to extend the RPCs (gRPCs) provided through LND with gRPCs provided by other code on the local machine or even a remote service. The new desc fields are not expected to be particularly useful at the moment as they can currently only be used with the scantxoutset RPC, but they will provide a compact way of providing all the information necessary for making addresses solvable to future and upgraded RPCs for Bitcoin Core such as those used for interactions between offline/online (cold/hot) wallets, multisig wallets, coinjoin implementations, and other cases. 2081 adds RPCs that allow signing a transaction template where some inputs are controlled by LN
p>
Rusty Russell has opened a PR to the BOLT repository and started a mailing list thread for feedback on a proposal to modify the construction and signing of some of the LN transactions in order to allow both BIP125 Replace-by-Fee (RBF) fee bumping and Child-Pays-For-Parent (CPFP) fee bumping. All you need are two or more wallets that implement multiparty ECDSA key generation and signing. However, to make this safe for LN no matter how high fees get, nodes need to also support relaying packages of transactions that include both low-feerate ancestors plus high-feerate descendants in a way that doesn’t cause nodes to automatically reject the earlier transactions as being too cheap and so not see the subsequent fee bumps. To play this video you need to enable JavaScript in your browser. An address is solvable when a program knows enough about its scriptPubKey, optional redeemScript, and optional witnessScript in order for the program to generate an unsigned input spending funds sent to that address. Second, the scriptPubKey of the coins being spent is also included in the hash-this also helps secure hardware wallets and offline wallets by eliminating a current ambiguity about whether the script being spent is a scriptPubKey, P2SH redeemScript, or segwit witnessScript.