ChanServ changed the topic of #bitcoin-core-dev to: Bitcoin Core development discussion and commit log | Feel free to watch, but please take commentary and usage questions to #bitcoin | Channel logs: http://www.erisian.com.au/bitcoin-core-dev/, http://gnusha.org/bitcoin-core-dev/ | Weekly Meeting Thursday @ 14:00 UTC | Meeting topics http://gnusha.org/bitcoin-core-dev/proposedmeetingtopics.txt
the_mariner has joined #bitcoin-core-dev
AaronvanW has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 252 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 256 seconds]
AaronvanW has quit [Ping timeout: 264 seconds]
kevkevin has quit [Ping timeout: 256 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 260 seconds]
baakeydow has quit [Quit: baakeydow]
baakeydow has joined #bitcoin-core-dev
AaronvanW has joined #bitcoin-core-dev
szkl has joined #bitcoin-core-dev
AaronvanW has quit [Ping timeout: 252 seconds]
kevkevin has joined #bitcoin-core-dev
the_mariner has joined #bitcoin-core-dev
kevkevin has quit [Read error: Connection reset by peer]
kevkevin has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 276 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 264 seconds]
Guest80 has joined #bitcoin-core-dev
kevkevin has quit [Remote host closed the connection]
the_mariner has joined #bitcoin-core-dev
Guest80 has quit [Quit: Client closed]
the_mariner has quit [Ping timeout: 268 seconds]
the_mariner has joined #bitcoin-core-dev
PaperSword has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 260 seconds]
zato has quit [Quit: Om mani padme hum]
the_mariner has joined #bitcoin-core-dev
AaronvanW has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 268 seconds]
szkl has quit [Quit: Connection closed for inactivity]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 256 seconds]
jarthur has quit [Quit: jarthur]
AaronvanW has quit [Ping timeout: 264 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 246 seconds]
boris- has joined #bitcoin-core-dev
boris has quit [Ping timeout: 276 seconds]
the_mariner has joined #bitcoin-core-dev
vysn has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 256 seconds]
cmirror has quit [Remote host closed the connection]
cmirror has joined #bitcoin-core-dev
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 260 seconds]
the_mariner has joined #bitcoin-core-dev
AaronvanW has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 255 seconds]
AaronvanW has quit [Ping timeout: 252 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 260 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 264 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 240 seconds]
bob_x2 has quit [Remote host closed the connection]
AaronvanW has joined #bitcoin-core-dev
bob_x2 has joined #bitcoin-core-dev
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 256 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 255 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 256 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 264 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 256 seconds]
jon_atack has joined #bitcoin-core-dev
jonatack has quit [Ping timeout: 256 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 240 seconds]
puchka has quit [Ping timeout: 256 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 260 seconds]
___nick___ has joined #bitcoin-core-dev
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 256 seconds]
___nick___ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
___nick___ has joined #bitcoin-core-dev
___nick___ has quit [Client Quit]
___nick___ has joined #bitcoin-core-dev
the_mariner has joined #bitcoin-core-dev
oneeyedalien has joined #bitcoin-core-dev
oneeyedalien has quit [Client Quit]
the_mariner has quit [Ping timeout: 252 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 268 seconds]
AaronvanW has quit [Quit: Leaving...]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 276 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 240 seconds]
cguida has joined #bitcoin-core-dev
szkl has joined #bitcoin-core-dev
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 255 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 256 seconds]
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 264 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 256 seconds]
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Read error: Connection reset by peer]
the_mariner has joined #bitcoin-core-dev
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Read error: Connection reset by peer]
the_mariner has quit [Ping timeout: 260 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 268 seconds]
the_mariner has joined #bitcoin-core-dev
kevkevin has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 256 seconds]
Guest22 has joined #bitcoin-core-dev
Guest22 has quit [Client Quit]
jon_atack has quit [Ping timeout: 255 seconds]
jonatack has joined #bitcoin-core-dev
jonatack has quit [Ping timeout: 255 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 256 seconds]
Guyver2 has joined #bitcoin-core-dev
Talkless has joined #bitcoin-core-dev
puchka has joined #bitcoin-core-dev
the_mariner has joined #bitcoin-core-dev
Guyver2 has quit [Read error: Connection reset by peer]
Guyver2 has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 255 seconds]
pablomartin has joined #bitcoin-core-dev
Lockesmith has quit [Ping timeout: 255 seconds]
Lockesmith has joined #bitcoin-core-dev
the_mariner has joined #bitcoin-core-dev
puchka has quit [Ping timeout: 276 seconds]
the_mariner has quit [Ping timeout: 268 seconds]
pablomartin4btc has joined #bitcoin-core-dev
pablomartin has quit [Ping timeout: 268 seconds]
jonatack has joined #bitcoin-core-dev
Guyver2 has left #bitcoin-core-dev [Closing Window]
cotsuka has quit [Remote host closed the connection]
the_mariner has joined #bitcoin-core-dev
cotsuka has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 246 seconds]
jonatack has quit [Ping timeout: 256 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 255 seconds]
pablomartin4btc has quit [Ping timeout: 264 seconds]
pablomartin4btc has joined #bitcoin-core-dev
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 256 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 255 seconds]
lbia has quit [Quit: lbia]
lbia has joined #bitcoin-core-dev
pablomartin4btc has quit [Ping timeout: 256 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 268 seconds]
AaronvanW has joined #bitcoin-core-dev
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 255 seconds]
brunoerg has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
<PaperSword> Question: Currently I am trying out the new submitpackage to test if a TX is consensus valid. The array size is one TX. I get this response.
<PaperSword> package topology disallowed. not child-with-parents or parents depend on each other.
<PaperSword> The prevouts are currently mined into a block.
<PaperSword> Here is my current RPC command for anyone that would be interested.
<PaperSword> ./src/bitcoin-cli submitpackage
<PaperSword> '["0100000000010171c895a9e47d160733d343189c89a8f322bc2772d3a05d2371cc7c9defcd043f0100000000ffffffff036fd2a81100000000160014307e69add0f095e3c52f29c7b5bc03bf611c929f0000000000000000160014fc55fae8118f10c5224bb06a21303ca8520558640100000000000000015102483045022100b32e104edc243d3e7b1ac3afe3135187be9dbe79941f6dfc3e770b08f99ed67b022063888d74f7f3e86c3eac78fb25a5f9d927193efa796b1136f4fd7131fefc43010121033db02ee63ce8554d401c3516579792c409b66a847e
<PaperSword> 00"]'
<PaperSword> testmempoolaccept and send rawtransaction both result in success.
<glozow> PaperSword: submitpackage requires at least 2 transactions
<glozow> (otherwise it's not really a package)
<PaperSword> Hmm, this error I get with an empty array is quite confusing then
<PaperSword> ./src/bitcoin-cli submitpackage '[]'
<PaperSword> Array must contain between 1 and 25 transactions.
<glozow> yeah see #29292
<gribble> https://github.com/bitcoin/bitcoin/issues/29292 | rpc: improve submitpackage documentation and other improvements by stickies-v · Pull Request #29292 · bitcoin/bitcoin · GitHub
<PaperSword> ^^^ Legend
<glozow> (feel free to leave a review)
<PaperSword> I will absolutely
<PaperSword> TY guys
<glozow> thanks!
<PaperSword> So here is a larger part of my question.
<PaperSword> I am concerned about a TX entering my mempool that is valid mempool policy but not valid consensus and my hashpower (testnet)
<PaperSword> How would I validate that TX by not just mempool acceptance but also consensus logic?
<PaperSword> Or is this already handled.
<glozow> That should never happen
<PaperSword> This is my reference,
<sipa> mempool policy is strictly stricter than consensus
<PaperSword> with 100% coverage?
<sipa> yes
<PaperSword> Okay thank you.
<sipa> the mempool _always_ consists of transactions that would be valid to include in the next block (but not all at once, obviously)
<PaperSword> Deeper down the rabbit hole why world submit package care to validate against consensus then if mempool acceptance would already be a pass.
Talkless has quit [Quit: Konversation terminated!]
<sipa> well it needs to verify both
<sipa> mempool acceptance = policy + consensus rules
PaperSword1 has joined #bitcoin-core-dev
<sipa> in the code "policy" is just the things that aren't consensus, we're not going to validate it twice
<PaperSword1> yeah, correct so policy is a subset of consensus?
the_mariner has joined #bitcoin-core-dev
<sipa> no
<PaperSword1> oh :( sorry for not understanding.
<sipa> consensus rules are a subset of acceptance rules
<sipa> policy rules are another subset
PaperSword has quit [Ping timeout: 276 seconds]
PaperSword1 is now known as PaperSword
<sipa> when you say "mempool policy" it can refer to "just the non-consensus policy rules", or it can refer to "the combined set of all rules that are necessary to enter the mempool" (which includes consensus rules too)
<PaperSword> Consensus Rules = The set of rules that would constitute valid bitcoin
<PaperSword> Policy Rules = The set of rules the node has to determine what set of txs it accepts into it's mempool
<PaperSword> Following that logic... Acceptance rules are?
<PaperSword> "when you say "mempool policy" it can refer to "just the non-consensus policy rules", or it can refer to "the combined set of all rules that are necessary to enter the mempool" (which includes consensus rules too)"
<PaperSword> TY
<sipa> but these are implementation details
the_mariner has quit [Ping timeout: 256 seconds]
<sipa> if you want the actual semantics... there are rules that are neccesary to be valid in a block (the consensus rules), and the rules to enter the mempool (which are a strict superset of those)
<PaperSword> yep :D
<PaperSword> Because the policy set is smaller than the consensus set, I never have to worry about my hashpower working on an invalid template
<sipa> indeed
<PaperSword> Thank you so much! For the sake of semantics, what are acceptance rules? I have never heard that term before.
<sipa> just informally... the rules necessary for a transaction to enter the mempool
<PaperSword> Does acceptance == policy?
<sipa> that depends on whether by "policy" you mean to include consensus rules or not
<sipa> policy is generally pretty vague
<PaperSword> I assume policy would include consensus since anything that is not consensus would not be of value.
<sipa> this is just a semantics discussion
<PaperSword> correct, sorry to take up time
<sipa> if by "policy" you mean "all the rules necessary to enter the mempool", then yes, acceptance == policy
<sipa> if by "policy" you mean "the rules that nodes are free to pick their own", then no, acceptance == policy + consensus
<PaperSword> I see what you mean, this also helps me understand what the /policy dir is for better
<sipa> what's in that directory is pretty narrow
<sipa> for example, resource limits (like standard transaction sizes) are in validation
<sipa> and script upgradability rules are in script
<sipa> (neither of which are consensus)
<PaperSword> correct, I am going to think about this a little deeper while I work. Thanks so much again for you time and help.
brunoerg has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 256 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 264 seconds]
the_mariner has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 256 seconds]
brunoerg has quit [Ping timeout: 276 seconds]
___nick___ has quit [Ping timeout: 260 seconds]
the_mariner has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 255 seconds]
brunoerg has joined #bitcoin-core-dev
the_mariner has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 260 seconds]
pablomartin4btc has joined #bitcoin-core-dev
Guest36 has joined #bitcoin-core-dev
Guest36 has quit [Client Quit]
the_mariner has quit [Ping timeout: 246 seconds]
vysn has quit [Remote host closed the connection]
AaronvanW has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 256 seconds]
meshcollider has quit [Ping timeout: 256 seconds]
brunoerg has joined #bitcoin-core-dev
the_mariner has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 264 seconds]
the_mariner has quit [Ping timeout: 264 seconds]
meshcollider has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 240 seconds]
PaperSword has quit [Ping timeout: 264 seconds]
AaronvanW has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 255 seconds]
AaronvanW has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 260 seconds]
PaperSword has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
the_mariner has joined #bitcoin-core-dev
aleggg has joined #bitcoin-core-dev
the_mariner has quit [Ping timeout: 255 seconds]
dikiy__ has joined #bitcoin-core-dev
jonatack has joined #bitcoin-core-dev
aleggg has quit [Remote host closed the connection]
dikiy__ has quit [Ping timeout: 250 seconds]
aleggg has joined #bitcoin-core-dev
jonatack has quit [Ping timeout: 255 seconds]
jonatack has joined #bitcoin-core-dev