:: Re: [Libbitcoin] Eric, what's the …
Top Pagina
Delete this message
Reply to this message
Auteur: Eric Voskuil
Datum:  
Aan: mlmikael, Xinxi Wang, libbitcoin
Onderwerp: Re: [Libbitcoin] Eric, what's the BIP support situation now - BIP:s 68, 112, 113 and SEGWIT (that's 141, 143, 144, 145)?
Libbitcoin implements all activated chain forks, and makes them all
optional in the node/server via boolean config settings:

[fork]
# Allow minimum difficulty blocks, defaults to false (use true for testnet).
easy_blocks = false
# Add pay-to-script-hash processing, defaults to true (soft fork).
bip16 = true
# Disallow collision of unspent transaction hashes, defaults to true
(hard fork).
bip30 = true
# Coinbase input must include block height, defaults to true (soft fork).
bip34 = true
# Require strict signature encoding, defaults to true (soft fork).
bip66 = true
# Add check locktime verify op code, defaults to true (soft fork).
bip65 = true
# Assume transaction hash collisions cannot happen, defaults to false
(hard fork).
allow_collisions = true
# Assume bip34, bip65, and bip66 activation if enabled, defaults to
false (hard fork).
deep_freeze = true

[note that deep_freeze has subsequently been written up as BIP90]

Assuming segwit activates we will support it as well, but we are not in
the habit of picking winners in terms of chain forks.

Version3 supports all combinations of network protocol versions between
31402 and 70012. This is a broader range than Bitcoin Core currently
supports and is fully configurable.

[network]
# The maximum network protocol version, defaults to 70012.
protocol_maximum = 70012
# The minimum network protocol version, defaults to 31402.
protocol_minimum = 31402

We have no intent of supporting bloom filtering (part of BIP37) or node
identity (BIPs 150/151).

There is also pretty broad standards support in wallet types (including
stealth) although there is no API for wallet structure.

There is no specific list by BIP but you are welcome to write it up on
the wiki.

e

On 01/19/2017 02:58 AM, mlmikael wrote:
> (resend forgot 141 in the list below)
>
> Hi Eric,
>
> What's the BIP support situation now - BIP:s 68, 112, 113 and SEGWIT
> (that's 141, 143, 144, 145)?
>
> (Also if the list of fully or partially supported BIP:s is written up
> anywhere please let me know.)
>
> I.e.:
>
> "Relative lock-time using consensus-enforced sequence numbers"
> https://github.com/bitcoin/bips/blob/master/bip-0068.mediawiki
>
> "CHECKSEQUENCEVERIFY"
> https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki
>
> "Median time-past as endpoint for lock-time calculations"
> https://github.com/bitcoin/bips/blob/master/bip-0113.mediawiki
>
> "Segregated Witness (Consensus layer)"
> https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki
>
> "Transaction Signature Verification for Version 0 Witness Program"
> https://github.com/bitcoin/bips/blob/master/bip-0143.mediawiki
>
> "Segregated Witness (Peer Services)"
> https://github.com/bitcoin/bips/blob/master/bip-0144.mediawiki
>
> "getblocktemplate Updates for Segregated Witness"
> https://github.com/bitcoin/bips/blob/master/bip-0145.mediawiki
>
> Mlmikael