< andytosh1> achow101: re writing a miniscript BIP, i'm happy to help in principle, though would need to sync with sipa about how the BIP would relate to his website then (should the website be largely replaced by the BIP? what if they differ? etc)
< sipa> i'd like to first get the sites and implementations in sync before writing a BIP
< andytosh1> makes sense
< prayank> Sorry if this is offtopic. Has anyone tried reading messages in Wireshark that bitcoin nodes use? Couldn't see anything helpful in INV or GETDATA or TX
< sipa> i thought wireshark had a bitcoin protocol analyzer
< sipa> though it may be very outdated
< sipa> prayank: that output looks correct?
< sipa> it's reporting an inv with 1 entry, which has type 5, and hash 1a72fe...
< sipa> it seems it doesn't know that type 5 is MSG_WTX (defined in BIP339)
< sipa> but otherwise this is fine
< gwillen> prayank: the annotated hex dumps you linked were hand-annotated by a person, I think, not automatically by an app
< prayank> It has a filter for bitcoin protocol. So I have two regtest nodes and did transaction from one which got relayed. I was expecting to see tx id in some message.
< sipa> the txid is there; 1a72fe...
< sipa> (it's a wtxid, because it's a MSG_WTX)
< sipa> also printed in reverse, i assume
< prayank> Interesting. Will check again.
< sipa> what i don't understand is why the dump in your screenshot doesn't include the string "inv"
< prayank> Not sure
< sipa> what if you click on reassembled TCP?
< prayank> Hex dump changes below in last section
< sipa> does it include the string "inv" then?
< prayank> Yes
< sipa> ok
< prayank> But I still couldn't find tx id. Let me share value for INV GETDATA TX from Wireshark and my actual Tx ID
< sipa> the txid isn't there
< sipa> the wtxid is
< sipa> and i assume it's printed in reverse (because the human-readable formatting of txids/wtxids is in the opposite order of the wire protocol)
< sipa> you can also use the -capturemessages feature btw, which will dump the p2p messages sent/received
< sipa> and the included contrib/message-capture/message-capture-parser.py tool can parse and print those
< prayank> Cool. Thanks. One last question. Maybe dumb q. Where do I check wtxid? I don't see in decoderawtransaction
< sipa> oh, it reports the wtxid as "hash"
< sipa> for silly historical reasons
< prayank> Thanks
< prayank> And yes I found WTXID in Wireshark. You are right about it being reverse.
< prayank> INV: f84ef7024f4a9d91605a5c1eae28664391ce0c8dc29d2fb396af24fe5c3a6499
< prayank> WTXID: 99643a5cfe24af96b32f9dc28d0cce91436628ae1e5c5a60919d4a4f02f74ef8
< michaelfolkson> andytosh1: If I had to guess there would be a transitional period where the spec moves from the website to a draft BIP. While the BIP is in draft it can still be changed
< michaelfolkson> andytosh1: But the website would still be used for the interactive parts, compiler, analyzer etc
< michaelfolkson> For the question on what is the authoritative resource if the C++ implementation disagrees with the Rust implementation that disagrees with the website that disagrees with the draft BIP that is definitely a question for sipa, you, Sanket etc ;)
< michaelfolkson> Perhaps this can/should move ##miniscript
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/da1c0c64fd09...6499928bfb19
< bitcoin-git> bitcoin/master 8a4f0fc Alex Groce: Document faster throughput configuration
< bitcoin-git> bitcoin/master 6499928 MarcoFalke: Merge bitcoin/bitcoin#22573: fuzz: document faster throughput configuratio...
< bitcoin-git> [bitcoin] MarcoFalke merged pull request #22573: fuzz: document faster throughput configuration (master...patch-1) https://github.com/bitcoin/bitcoin/pull/22573
< hebasto> laanwj: the German (de) translation has been restored in Transifex.com -- https://github.com/bitcoin/bitcoin/pull/22536#issuecomment-890323524
< laanwj> hebasto: thank you!
< tutwidi[m]> I test running bitcoin core on Redhat Enterprize Linux 8.4 sha256sum --ignore-missing --check SHA256SUMS.asc
< tutwidi[m]> bitcoin-0.21.1-x86_64-linux-gnu.tar.gz: OK
< tutwidi[m]> sha256sum: WARNING: 20 lines are improperly formatted
< bitcoin-git> [bitcoin] theStack opened pull request #22593: test: refactor: remove `hex_str_to_bytes` helper (master...202107-test-remove_unneeded_hexstrtobytes) https://github.com/bitcoin/bitcoin/pull/22593