[bitcoin-dev] Bitcoin Guarantees Strong, not Eventual, Consistency.
There seems to be a perception out there that Bitcoin is eventually consistent. I wrote this post to describe why this perception is completely false. Bitcoin Guarantees Strong, not Eventual, Consistency http://hackingdistributed.com/2016/03/01/bitcoin-guarantees-strong-not-eventual-consistency/ I hope we can lay this bad meme to rest. Bitcoin provides a strong guarantee. - egs ___ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[bitcoin-dev] Proposed BIP extension to BIP 0070
The following draft BIP proposes an update to the Payment Protocol. Motivation: The motivation for defining this extension to the BIP70 Payment Protocol is to allow 2 parties to exchange payment information in a permissioned and encrypted way such that wallet address communication can become a more automated process. Additionally, this extension allows for the requestor of a PaymentRequest to supply a certificate and signature in order to facilitate identification for address release. This also allows for automated creation of off blockchain transaction logs that are human readable, containing who you transacted with, in addition to the information that it contains today. The motivation for this extension to BIP70 is threefold: 1. Ensure that the payment details can only be seen by the participants in the transaction, and not by any third party. 2. Enhance the Payment Protocol to allow for store and forward servers in order to allow, for example, mobile wallets to sign and serve Payment Requests. 3. Allow a sender of funds the option of sharing their identity with the receiver. This information could then be used to: * Make bitcoin logs more human readable * Give the user the ability to decide who to release payment details to * Allow an entity such as a political campaign to ensure donors match regulatory and legal requirements * Allow for an open standards based way for regulated financial entities to meet regulatory requirements * Automate the active exchange of payment addresses, so static addresses and BIP32 X-Pubs can be avoided to maintain privacy and convenience In short we wanted to make bitcoin more human, while at the same time improving transaction privacy. Full proposal here: https://github.com/techguy613/bips/blob/master/bip-invoicerequest-extension.mediawiki We look forward to your thoughts and feedback on this proposal! Justin -- Justin W. Newton Founder/CEO Netki, Inc. jus...@netki.com +1.818.261.4248 ___ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[bitcoin-dev] Bitcoin Knots 0.12.0.knots20160226 release candidate 1 available
Binaries for Bitcoin Knots version 0.12.0.knots20160226.rc1 are available from: https://bitcoinknots.org/files/0.12.x/0.12.0.knots20160226/test/rc1/ Source code can be found on GitHub under the signed tag: https://github.com/bitcoinknots/bitcoin/tree/v0.12.0.knots20160226.rc1 This is a release candidate for a new major version release, bringing new features, bug fixes, as well as other improvements. Preliminary release notes for the release can be found here: https://github.com/bitcoinknots/bitcoin/blob/0.12.x-knots/doc/release-notes.md Release candidates are test versions for releases. When no critical problems are found, this release candidate will be tagged as final. Please report bugs using the issue tracker at GitHub: https://github.com/bitcoinknots/bitcoin/issues Additional Gitian signatures are welcome. Please submit via GitHub pull request to: https://github.com/bitcoinknots/gitian.sigs ___ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[bitcoin-dev] Soft fork for BIPs 68, 112, and 113
Bitcoin Core is ready to move towards deployment of a soft fork which will implement BIP's 68, 112, and 113. BIP 68 - Relative lock-time using consensus-enforced sequence numbers - https://github.com/bitcoin/bips/blob/master/bip-0068.mediawiki BIP 112 - CHECKSEQUENCEVERIFY - https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki BIP 113 - Median time-past as endpoint for lock-time calculations - https://github.com/bitcoin/bips/blob/master/bip-0113.mediawiki BIP 113 logic was introduced in the 0.11.2 release as a standardness rule and BIP 68 and BIP 112 logic has been merged into master*. What remains to be done is finish testing, merge the logic to activate the soft forks and backport the code to supported releases. The exact rollout mechanism is still being finalized but will be coordinated with the community. This email is meant to serve as a readiness announcement and confirm that there are no outstanding concerns. Thanks, Alex * - BIP 68 and BIP 112 logic is only enforced when the tx version is >= 2 which will only become standard with the release of the soft fork code. ___ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[bitcoin-dev] IRC meetings moved to #bitcoin-core-dev
It seems that MeetingBot was deactivated in #bitcoin-dev, so the last two weeks the weekly developer meeting (Thursday 19:00-20:00 UTC) was held in #bitcoin-core-dev. Let's keep it at that. Wladimir ___ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
