The other strategy is to have an informational BIP to define "safe" use
of Bitcoin.
1. scriptPubKey must be one of the following types: P2PK, P2PKH, P2SH,
n-of-m multisig with m < 4 (with or without CLTV or CSV, we should
define standard use of CLTV and CSV)
2. For P2SH, the serialized scrip
On 02/11/15 14:33, Gavin Andresen via bitcoin-dev wrote:
> I like those guidelines, although I'm sure there may be lots of arguing
> over what fits under "protects the integrity of the network" or what
> constitutes "reasonable notice" (publish a BIP at least 30 days before
> rolling out a change?
The Bitcoin.org Development Guide has grown by leaps in bounds this year,
and has two great introductions:
1. https://bitcoin.org/en/development for an overview of how a developer
can contribute,
2. https://bitcoin.org/en/developer-reference for in-detail reference to
how the whole system works.
On Sun, Nov 1, 2015 at 6:46 PM, Tier Nolan via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> For guidelines
>
> * Transaction version numbers will be increased, if possible
> * Transactions with unknown/large version numbers are unsafe to use with
> locktime
> * Reasonable notice i
Hey,
I'm interested in helping out with the development of Bitcoin Core.
I'm used to getting involved with huge projects by starting to write unit
tests (in order to get familiar with the project's tools, infrastructure
etc).
Is there any ramp up process (like for example any documentation) that
Google Docs formatted version:
https://docs.google.com/document/d/1t3kGkAUQ-Yui57P29YhDll5WyJuTiGrUhCW8so-E-iQ/edit?usp=sharing
Meeting Title:
#bitcoin-dev Weekly Development Meeting
Meeting Date:
2015-10-29
Meeting Time:
19:00-20:00 UTC
Participants in Attendance:
dstadulis
morcos
sipa
jgarzik
