Skip to content

Conversation

@UdjinM6
Copy link

@UdjinM6 UdjinM6 commented Aug 12, 2016

These features were introduced in bitcoin 0.11/0.12 and our 0.12.0.x nodes (which are bitcoin 0.10 based) are already running on higher protocol (70103). Bumping these to avoid banning nodes for misbehavior (bloom) and correctly (not) push sendheaders messages. Fixing related comments too.

@crowning-
Copy link

Nice find 👍
utACK

@schinzelh
Copy link

Yep, nice find - utACK 411ad29

@schinzelh schinzelh merged commit 625b5eb into dashpay:v0.12.1.x Aug 12, 2016
@UdjinM6 UdjinM6 deleted the protobumps branch August 28, 2016 12:23
PastaPastaPasta pushed a commit to PastaPastaPasta/dash that referenced this pull request Jul 17, 2020
…has never been used.

ac8a1d0 [RPC] Remove field in getblocktemplate help that has never been used (Conor Scott)

Pull request description:

  [BIP 22 - getblocktemplate](https://github.com/bitcoin/bips/blob/master/bip-0022.mediawiki#Transactions%20Object%20Format) specifies an optional flag, `required` if the transaction must be in the block.

  Luke's implementation dashpay#936 did not include this flag, and it was later added to the help description in dashpay#3246 (more than a year later) but the field was still never actually implemented. As far as I can tell, bitcoin core would have never actually included this in a `getblocktemplate` call, so it seems logical to remove it from the help description.

  If I am missing something or this is considered harmless - I can close the PR.

Tree-SHA512: f25dda51cc4e1512aff69309be04e3053bdccc1cf03c8d58e8866aa1fdf9d86cc57df872e85528351fc8a8d6d64a8f46a36c513680834762d854f368fbeb0f44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants