jojeyh: I think your question is more suited for #bitcoin though, btw.
kallewoof, thx i was wondering if someone had already done it
Does anyone know of software / a script that can say “if you merge this pull request, then pull requests X, Y, and Z will have to be rebased”? Google didn’t turn anything up so I’m interested in writing one
pierre_rochard: The folks on the #github channel have been helpful to me in the past. I suspect there's a good chance someone there might know of something like you describe if it exists.
I’ll ask them, thanks Randolf!
pierre_rochard: ajtowns[m] did some work in that direction (a script to figure out which PRs collide with which others) from what I remember
Looks like it's checked by default (I did some trial and error sabotage on my local machine).
bip173 lists tc1qw508d6qejxtdg4y5r3zarvary0c5xw7kg3g4ty as being invalid due to "invalid human-readable part", is it just that "tc" is not one of "bc", "tb", or "bcrt" or is there anything else to it? seems that apart from that it does encode a valid p2wpkh
right, in my mind hrp could be anything, but I see why it's not a "segwit address"
BIP173 only specifies bc and tb, so anything else is invalid
arubi: I believe the lightning people repurpose it. Don't know how the author feels about that usage though :-)
but it's certainly valid bech32... just not a valid segwit address
Chris_Stewart_5: bech32 is designed to be generally useful :)
right, so as long as some implementation keeps to its own hrp, we should all be fine
(though they violate the spec by exceeding 90 characters)
sipa: did you get a chance to read the mail i sent about soft-fork compatible sig aggregation? see any obvious problems, or worth sending to bitcoin-dev do you think?