You've already forked specification
Additional modifications to BIP/HF layout, added BIP-35.
This commit is contained in:
@@ -27,17 +27,25 @@
|
||||
[Bitcoin Keys (Public/Private)](/protocol/blockchain/cryptography/keys) — [Signatures (ECDSA/Schnorr)](/protocol/blockchain/cryptography/signatures) — [Multisignature (M-of-N multisig)](/protocol/blockchain/cryptography/multisignature)
|
||||
|
||||
### Network upgrades
|
||||
**Pre-BCH:** [Bip-9](/protocol/forks/bip-0009) — [Bip-16](/protocol/forks/bip-0016) — [Bip-34](/protocol/forks/bip-0034) — [Bip-37](/protocol/forks/bip-0037) — [Bip-65](/protocol/forks/bip-0065) — [Bip-66](/protocol/forks/bip-0066) — [Bip-68](/protocol/forks/bip-0068) — [Bip-112](/protocol/forks/bip-0112) — [Bip-113](/protocol/forks/bip-0113) — [Bip-133](/protocol/forks/bip-0133) — [Bip-152](/protocol/forks/bip-0152) — [Bip-157](/protocol/forks/bip-0157) — [Bip-158](/protocol/forks/bip-0158) — [Bip-159](/protocol/forks/bip-0159)
|
||||
|
||||
**2017:** [BCH-UAHF (BUIP-55)](/protocol/forks/bch-uahf) — [HF-20171113](/protocol/forks/hf-20171113)
|
||||
#### Pre-BCH
|
||||
|
||||
**2018:** [HF-20180515](/protocol/forks/hf-20180515) — [HF-20181115](/protocol/forks/hf-20181115)
|
||||
| Year (Creation) | BIPs |
|
||||
|------|-------|
|
||||
| 2012 | [Bip-16](/protocol/forks/bip-0016) — [Bip-34](/protocol/forks/bip-0034) — [BIP-35](/protocol/forks/bip-0035) — [Bip-37](/protocol/forks/bip-0037) |
|
||||
| 2014 | [Bip-65](/protocol/forks/bip-0065) |
|
||||
| 2015 | [Bip-66](/protocol/forks/bip-0066) — [Bip-68](/protocol/forks/bip-0068) — [Bip-112](/protocol/forks/bip-0112) — [Bip-113](/protocol/forks/bip-0113) — [Bip-9](/protocol/forks/bip-0009) |
|
||||
| 2016 | [Bip-133](/protocol/forks/bip-0133) — [Bip-152](/protocol/forks/bip-0152) |
|
||||
| 2017 | [Bip-157](/protocol/forks/bip-0157) — [Bip-158](/protocol/forks/bip-0158) — [Bip-159](/protocol/forks/bip-0159) |
|
||||
|
||||
**2019:** [HF-20190515](/protocol/forks/hf-20190515) — [HF-20191115](/protocol/forks/hf-20191115)
|
||||
|
||||
**2020:** [HF-20200515](/protocol/forks/hf-20200515) — [HF-20201115](/protocol/forks/hf-20201115)
|
||||
|
||||
**2021:** [HF-20210515](/protocol/forks/hf-20210515)
|
||||
#### BCH
|
||||
| Year (Activation) | Hard Forks |
|
||||
|------|---------------|
|
||||
| 2017 | [BCH-UAHF (BUIP-55)](/protocol/forks/bch-uahf) — [HF-20171113](/protocol/forks/hf-20171113) |
|
||||
| 2018 | [HF-20180515](/protocol/forks/hf-20180515) — [HF-20181115](/protocol/forks/hf-20181115) |
|
||||
| 2019 | [HF-20190515](/protocol/forks/hf-20190515) — [HF-20191115](/protocol/forks/hf-20191115) |
|
||||
| 2020 | [HF-20200515](/protocol/forks/hf-20200515) — [HF-20201115](/protocol/forks/hf-20201115) |
|
||||
| 2021 | [HF-20210515](/protocol/forks/hf-20210515) |
|
||||
|
||||
### Network protocol
|
||||
[Network Messages](/protocol/network/messages) — [Handshake](/protocol/network/node-handshake)
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# UAHF
|
||||
# BCH-UAHF: Bitcoin Cash User-Activated Hard Fork
|
||||
|
||||
layout: specification
|
||||
title: UAHF Technical Specification
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# BIP-0009
|
||||
# BIP-9
|
||||
BIP: 9
|
||||
Title: Version bits with timeout and delay
|
||||
Author: Pieter Wuille <pieter.wuille@gmail.com>
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# BIP-0016
|
||||
# BIP-16
|
||||
|
||||
BIP: 16
|
||||
Layer: Consensus (soft fork)
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# BIP-0034
|
||||
# BIP-34
|
||||
|
||||
BIP: 34
|
||||
Layer: Consensus (soft fork)
|
||||
|
||||
@@ -0,0 +1,41 @@
|
||||
# BIP-35
|
||||
|
||||
BIP: 35
|
||||
Layer: Peer Services
|
||||
Title: mempool message
|
||||
Author: Jeff Garzik <jgarzik@exmulti.com>
|
||||
Comments-Summary: No comments yet.
|
||||
Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0035
|
||||
Status: Final
|
||||
Type: Standards Track
|
||||
Created: 2012-08-16
|
||||
|
||||
## Abstract
|
||||
|
||||
Make a network node's transaction memory pool accessible via a new "mempool" message. Extend the existing "getdata" message behavior to permit accessing the transaction memory pool.
|
||||
|
||||
## Motivation
|
||||
|
||||
Several use cases make it desireable to expose a network node's transaction memory pool:
|
||||
1. SPV clients, wishing to obtain zero-confirmation transactions sent or received.
|
||||
2. Miners, to avoid missing lucrative fees, downloading existing network transactions after a restart.
|
||||
3. Remote network diagnostics.
|
||||
|
||||
## Specification
|
||||
|
||||
1. The mempool message is defined as an empty message where pchCommand == "mempool"
|
||||
2. Upon receipt of a "mempool" message, the node will respond with an "inv" message containing MSG_TX hashes of all the transactions in the node's transaction memory pool, if any.
|
||||
3. The typical node behavior in response to an "inv" is "getdata". However, the reference Satoshi implementation ignores requests for transaction hashes outside that which is recently relayed. To support "mempool", an implementation must extend its "getdata" message support to querying the memory pool.
|
||||
4. Feature discovery is enabled by checking two "version" message attributes:
|
||||
- Protocol version >= 60002
|
||||
- NODE_NETWORK bit set in nServices
|
||||
|
||||
Note that existing implementations drop "inv" messages with a vector size > 50000.
|
||||
|
||||
## Backward compatibility
|
||||
|
||||
Older clients remain 100% compatible and interoperable after this change.
|
||||
|
||||
## Implementation
|
||||
|
||||
https://github.com/bitcoin/bitcoin/pull/1641
|
||||
@@ -1,4 +1,4 @@
|
||||
# BIP-0037
|
||||
# BIP-37
|
||||
|
||||
BIP: 37
|
||||
Layer: Peer Services
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# BIP-0065
|
||||
# BIP-65
|
||||
|
||||
BIP: 65
|
||||
Layer: Consensus (soft fork)
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# BIP-0066
|
||||
# BIP-66
|
||||
|
||||
BIP: 66
|
||||
Layer: Consensus (soft fork)
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# BIP-0068
|
||||
# BIP-68
|
||||
|
||||
BIP: 68
|
||||
Layer: Consensus (soft fork)
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
BIP-0112
|
||||
# BIP-112
|
||||
|
||||
BIP: 112
|
||||
Layer: Consensus (soft fork)
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# BIP-0113
|
||||
# BIP-113
|
||||
|
||||
BIP: 113
|
||||
Layer: Consensus (soft fork)
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# BIP-0133
|
||||
# BIP-133
|
||||
|
||||
BIP: 133
|
||||
Layer: Peer Services
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# BIP-0157
|
||||
# BIP-157
|
||||
|
||||
BIP: 157
|
||||
Layer: Peer Services
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# BIP-0158
|
||||
# BIP-158
|
||||
|
||||
BIP: 158
|
||||
Layer: Peer Services
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# BIP-0159
|
||||
# BIP-159
|
||||
|
||||
BIP: 159
|
||||
Layer: Peer Services
|
||||
|
||||
@@ -3,6 +3,8 @@
|
||||
Requests that the recipient notify the sender of transactions that are currently in its [mempool](/protocol/blockchain/memory-pool).
|
||||
Recipients of a `mempool` message MAY respond with a set of transaction hashes currently in their mempool via an [`inv`](/protocol/network/messages/inv) message.
|
||||
|
||||
The mempool message was defined in [BIP-35](/protocol/forks/bip-0035).
|
||||
|
||||
## Message Format
|
||||
This message has no contents.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user