1 2018-01-10 00:40:07 0|cfields|oh, i guess the port doesn't go over the wire for A/AAA queries anyway
2 2018-01-10 00:58:25 0|BlueMatt|cfields: yea, was gonna say, since when is there a *port* in dns queries?
3 2018-01-10 00:59:34 0|BlueMatt|I mean there's the stupid bullshit query stuff, but no one uses that garbage
4 2018-01-10 00:59:36 0|echeveria|BlueMatt: when I do a AAAA lookup there's lots of ports.
5 2018-01-10 00:59:43 0|BlueMatt|.........
6 2018-01-10 01:00:24 0|cfields|BlueMatt: yea, I was going by getaddrinfo and a bad reading of its man page. A look at the spec says otherwise, ofc.
7 2018-01-10 01:00:56 0|echeveria|not like we use non-standard ports
8 2018-01-10 01:28:02 0|luke-jr|A/AAAA doesn't support ports
9 2018-01-10 01:28:16 0|luke-jr|you need to use SRV (which does get used for other things) for that
10 2018-01-10 01:28:57 0|cfields|luke-jr: right
11 2018-01-10 01:32:06 0|BlueMatt|i mean not really...who the fuck uses SRV? Aside from SIP, apparently
12 2018-01-10 01:32:22 0|luke-jr|XMPP at least
13 2018-01-10 01:32:29 0|BlueMatt|lol who uses XMPP
14 2018-01-10 01:32:41 0|luke-jr|anyone who likes IM and open standards?
15 2018-01-10 01:32:49 0|BlueMatt|soooo...no one?
16 2018-01-10 01:32:58 0|luke-jr|lots of people
17 2018-01-10 01:33:26 0|luke-jr|ok, just my family
18 2018-01-10 01:33:32 0|luke-jr|:|
19 2018-01-10 01:37:52 0|BlueMatt|see? no one who cares enough about open standards to buck their social media trends uses IM cause they're all already using irc :p
20 2018-01-10 04:08:56 0|bitcoin-git|[13bitcoin] 15achow101 opened pull request #12136: Implement BIP 174 Partially Signed Bitcoin Transactions (06master...06psbt) 02https://github.com/bitcoin/bitcoin/pull/12136
21 2018-01-10 04:34:38 0|meshcollider|Wow lots of cool PRs opening today \o/
22 2018-01-10 07:01:38 0|battulga|Hello there! I'm a newbee here to seek you guys's counsel :)
23 2018-01-10 07:02:15 0|battulga|where i should look at first
24 2018-01-10 07:03:04 0|battulga|is there anyone?
25 2018-01-10 07:13:18 0|sipa|cfields: port?
26 2018-01-10 07:14:19 0|cfields|sipa: see follow-up. I misread what actually goes over the wire.
27 2018-01-10 07:17:32 0|sipa|ok
28 2018-01-10 13:05:48 0|wacawacawaca|
29 2018-01-10 15:41:53 0|JayBerg|hey guys - do you need help with qt for segwit?
30 2018-01-10 15:42:27 0|JayBerg|my latest QT/bitcoin project: https://github.com/SatoshiFantasy/--skillSale
31 2018-01-10 15:42:51 0|JayBerg|/test
32 2018-01-10 15:43:15 0|provoostenator|JayBerg: always... See e.g. https://github.com/bitcoin/bitcoin/issues?q=is%3Aissue+is%3Aopen+label%3AWallet and https://github.com/bitcoin/bitcoin/issues?q=is%3Aissue+is%3Aopen+label%3AGUI
33 2018-01-10 15:44:45 0|provoostenator|More specific to SegWit are #11403, #11937 and #11991.
34 2018-01-10 15:44:51 0|gribble|https://github.com/bitcoin/bitcoin/issues/11403 | SegWit wallet support by sipa ÷ Pull Request #11403 ÷ bitcoin/bitcoin ÷ GitHub
35 2018-01-10 15:44:53 0|gribble|https://github.com/bitcoin/bitcoin/issues/11937 | Qt: Setting for deciding address type (legacy, p2sh or bech32) by hsjoberg ÷ Pull Request #11937 ÷ bitcoin/bitcoin ÷ GitHub
36 2018-01-10 15:44:55 0|gribble|https://github.com/bitcoin/bitcoin/issues/11991 | [qt] Receive: checkbox for bech32 address by Sjors ÷ Pull Request #11991 ÷ bitcoin/bitcoin ÷ GitHub
37 2018-01-10 15:45:12 0|JayBerg|any talk on moving to QML instead of widgets?
38 2018-01-10 15:48:05 0|JayBerg|i appeciate the issues tracker, and will take a lookââ¬Â¦ its just that i spend all day coding QT for bitcoin/blockchain and have lots of code an insight that can help if there are big blocking issues etc. jay at protoblock dot com
39 2018-01-10 15:50:44 0|sipa|JayBerg: review and testing are always the bottlenecks ;)
40 2018-01-10 15:53:09 0|promag|JayBerg: problem with QML is JS engine
41 2018-01-10 15:53:36 0|JayBerg|Sipa: so your saying there is an implimentation already? maybe best bet would be to fork and create a new wallet outside of coreââ¬Â¦ segwit has been ready for years.. cant see major issues with qt front end..
42 2018-01-10 15:53:37 0|promag|something that most don't want to see
43 2018-01-10 15:54:06 0|JayBerg|promag: no need to use JS in qml
44 2018-01-10 15:54:14 0|JayBerg|promag: ok for security reasons?
45 2018-01-10 15:55:08 0|promag|JayBerg: probably there is more interest in something like #10973
46 2018-01-10 15:55:11 0|gribble|https://github.com/bitcoin/bitcoin/issues/10973 | Refactor: separate wallet from node by ryanofsky ÷ Pull Request #10973 ÷ bitcoin/bitcoin ÷ GitHub
47 2018-01-10 15:55:35 0|promag|JayBerg: reasons :)
48 2018-01-10 15:57:11 0|JayBerg|its not like QML will run client side JS from internet ââ¬Â¦ we see all the sourceââ¬Â¦ unless im missing somethingââ¬Â¦ c++ can do everyhting js can do ?
49 2018-01-10 15:57:45 0|promag|JayBerg: can you list pros of a qml wallet? I like qml, but I don't see why would it change
50 2018-01-10 15:58:07 0|JayBerg|qml will solve those display issues with differnt dpis
51 2018-01-10 15:58:52 0|promag|little issue to justify a big refactor
52 2018-01-10 15:59:05 0|sipa|JayBerg: segwit support for the bitcoin core *wallet* is the issue; UI will work automatically
53 2018-01-10 15:59:13 0|JayBerg|widgets is old buggy and no longer used
54 2018-01-10 15:59:23 0|sipa|there's nothing special that needs to be done in the UI
55 2018-01-10 15:59:32 0|JayBerg|ok sipa what is the issue? so what is a ââ¬Åwalletââ¬Â if not thegui
56 2018-01-10 15:59:42 0|promag|JayBerg: that's not true, even QtCreator is widget based
57 2018-01-10 16:00:35 0|sipa|JayBerg: the logic that determines which transactions are yours, construct paymemts, keep track of your balance, can import keys, ...
58 2018-01-10 16:01:19 0|JayBerg|sipa - is there a cli for sending segwit in core?
59 2018-01-10 16:01:32 0|JayBerg|or creating segwit tx ?
60 2018-01-10 16:01:46 0|sipa|JayBerg: all part of #11403
61 2018-01-10 16:01:52 0|gribble|https://github.com/bitcoin/bitcoin/issues/11403 | SegWit wallet support by sipa ÷ Pull Request #11403 ÷ bitcoin/bitcoin ÷ GitHub
62 2018-01-10 16:02:31 0|sipa|there was rudimentary support before, but it is not user friendly (it needed manual rpc calls to construct addresses etc; enough for testing, but not for users)
63 2018-01-10 16:03:41 0|JayBerg|ok - im assuming bech32 - is not included with ââ¬Åsegwit supportââ¬Â - to much at once
64 2018-01-10 16:03:57 0|JayBerg|ok will take a look.. and brb
65 2018-01-10 16:04:00 0|sipa|bech32 is already merged in master
66 2018-01-10 16:10:01 0|promag|sipa: regarding #11991
67 2018-01-10 16:10:03 0|gribble|https://github.com/bitcoin/bitcoin/issues/11991 | [qt] Receive: checkbox for bech32 address by Sjors ÷ Pull Request #11991 ÷ bitcoin/bitcoin ÷ GitHub
68 2018-01-10 16:10:23 0|promag|ping provoostenator
69 2018-01-10 16:11:59 0|promag|assuming bech32 is the default address type, it would be annoying always having the checkbox disabled there don't you think?
70 2018-01-10 16:12:49 0|promag|again, assuming bech32 is the default address type, does it make sense to create a payment to other address type?
71 2018-01-10 16:13:18 0|instagibbs|promag, "make a payment"?
72 2018-01-10 16:13:23 0|sipa|i think it will be years before p2sh witness won't be needed anymore
73 2018-01-10 16:13:29 0|instagibbs|err "create a payment"
74 2018-01-10 16:13:31 0|promag|for instance, receive a payment from an older wallet?
75 2018-01-10 16:13:40 0|sipa|promag: yes, exavtly that
76 2018-01-10 16:13:45 0|instagibbs|it will accept those, yes
77 2018-01-10 16:13:52 0|sipa|not every wallet software is going to support bech32 immediately
78 2018-01-10 16:14:29 0|promag|so, the wallet must allow a p2sh address in the UI
79 2018-01-10 16:14:54 0|promag|instagibbs: ya sorry, bad writing
80 2018-01-10 16:15:24 0|promag|so the checkbox is not an option
81 2018-01-10 16:15:34 0|sipa|hmmm
82 2018-01-10 16:15:37 0|sipa|?
83 2018-01-10 16:15:43 0|sipa|what is wrong with that
84 2018-01-10 16:16:24 0|promag|with -addresstype=bech32 how can I request a payment for p2sh?
85 2018-01-10 16:17:04 0|sipa|by specifying it explicitly
86 2018-01-10 16:17:25 0|sipa|i'm confused :)
87 2018-01-10 16:17:44 0|sipa|-addresstype only sets the default, it doesn't force anything
88 2018-01-10 16:18:56 0|sipa|for the GUI i would expect that -addresstype maybe controls what the checkbox is set to by default
89 2018-01-10 16:19:54 0|promag|but with -addresstype=bech32 the checkbox is disabled
90 2018-01-10 16:20:43 0|promag|See https://github.com/bitcoin/bitcoin/pull/11991#pullrequestreview-86170976
91 2018-01-10 16:20:56 0|sipa|oh, i haven't looked at any GUI prs
92 2018-01-10 16:21:33 0|promag|So with -addresstype=bech32 there is no way to request payment to p2sh
93 2018-01-10 16:21:47 0|sipa|that is bad :)
94 2018-01-10 16:47:15 0|owowo|very bad.
95 2018-01-10 17:24:50 0|JayBerg|b
96 2018-01-10 17:28:40 0|JayBerg|i have 20+ years of c++ for fintech.. and would love to contribute to bitcoin-core.. I just cant seem to find the time. however, half my time is for outside consulting gigs to pay bills, so if there are any bounties or paid consulting gigs that will allow me to contribute. im all ears.. otherwise, i should be able to contribute starting mid-Feburary (after Super Bowl)
97 2018-01-10 18:25:46 0|cfields|jonasschnelli: ping. mind going ahead and grabbing a temp codesigning key just in case?
98 2018-01-10 19:38:35 0|jonasschnelli|cfields: okay. Will do
99 2018-01-10 19:38:51 0|jonasschnelli|cfields: do you want to provide the CSR (aka hold the key)
100 2018-01-10 19:39:01 0|jonasschnelli|I guess you already do that for the current signing cert?
101 2018-01-10 19:40:15 0|cfields|jonasschnelli: I was going to suggest that you just do it, but I guess it doesn't make sense for us to additively hold up releases :(
102 2018-01-10 19:40:32 0|cfields|(though hopefully it will only be used ~once anyway)
103 2018-01-10 19:40:59 0|cfields|so.. I guess so
104 2018-01-10 19:42:17 0|cfields|jonasschnelli: will you be available for ~an hour? I'm going to try to create the CSR by hand as if for the threshold key
105 2018-01-10 19:47:29 0|jonasschnelli|cfields: Yes. I'm around for 1h. Okay... let me create one then
106 2018-01-10 19:51:52 0|jimpo|If anyone feels like reading some code, I'm looking for reviews on #11857
107 2018-01-10 19:51:54 0|gribble|https://github.com/bitcoin/bitcoin/issues/11857 | Build tx index in parallel with validation by jimpo ÷ Pull Request #11857 ÷ bitcoin/bitcoin ÷ GitHub
108 2018-01-10 19:58:24 0|cfields|jonasschnelli: heh, not sure what the plan is. Are you creating the CSR or me?
109 2018-01-10 20:23:13 0|jonasschnelli|cfields: sorry.. was off for some minutes... I dunno. What is preferable, I do it are you?
110 2018-01-10 20:23:28 0|jonasschnelli|I can hold the key in a relatively secure env... though not cold
111 2018-01-10 20:29:49 0|cfields|jonasschnelli: ok, sounds good to me
112 2018-01-10 20:30:56 0|jonasschnelli|cfields: okay. will do in the evening... (in 10h)
113 2018-01-10 20:31:34 0|cfields|jonasschnelli: if you happen to have it handy, could you go ahead and gen the key so that I can sign a message with the pubkey?
114 2018-01-10 20:31:49 0|cfields|If it's not convenient, no problem
115 2018-01-10 20:32:54 0|jonasschnelli|cfields: Okay. I have the key and the csr
116 2018-01-10 20:33:41 0|cfields|jonasschnelli: oh, perfect. If you send me the csr I can just grab the pubkey out of it
117 2018-01-10 20:34:04 0|jonasschnelli|Okay... comes per email
118 2018-01-10 20:34:31 0|cfields|thanks!
119 2018-01-10 20:35:20 0|jonasschnelli|The CRS or the CRT?
120 2018-01-10 20:35:23 0|jonasschnelli|*CSR
121 2018-01-10 20:35:48 0|jonasschnelli|I guess the cert hold the pkey... so the CSR
122 2018-01-10 20:37:00 0|cfields|oh heh, you already got a crt?
123 2018-01-10 20:37:38 0|cfields|yes, the csr. The crt should just be a cert containing the pubkey, signed by apple
124 2018-01-10 20:37:54 0|jonasschnelli|cfields: okay. Sent you the crt.
125 2018-01-10 20:38:06 0|jonasschnelli|Yes. I have also done the whole process (it's pretty easy nowadays).-
126 2018-01-10 20:38:50 0|cfields|got it. Thanks again!
127 2018-01-10 20:40:26 0|cfields|sorry for the rush, I'm hoping I can figure out how to get apple's timestamp server to sign something arbitrary before our cert expires
128 2018-01-10 20:48:32 0|jonasschnelli|cfields: no need to be sorry. :)
129 2018-01-10 20:48:38 0|jonasschnelli|Tell me also if you need more.
130 2018-01-10 20:48:46 0|jonasschnelli|I'm on/off today... so expect a delay
131 2018-01-10 20:49:57 0|cfields|no worries
132 2018-01-10 22:48:17 0|bitcoin-git|[13bitcoin] 15TheBlueMatt opened pull request #12138: Track best-possible-headers (06master...062017-10-best-header-tracking) 02https://github.com/bitcoin/bitcoin/pull/12138
133 2018-01-10 22:48:51 0|BlueMatt|jonasschnelli: if you ever want to revive your spv mode patch, you'll probably want that ^
134 2018-01-10 22:49:56 0|jonasschnelli|BlueMatt: thanks... will have a look.
135 2018-01-10 22:50:01 0|promag_|BlueMatt: #11041 is calling for you
136 2018-01-10 22:50:04 0|gribble|https://github.com/bitcoin/bitcoin/issues/11041 | Add LookupBlockIndex by promag ÷ Pull Request #11041 ÷ bitcoin/bitcoin ÷ GitHub
137 2018-01-10 22:50:08 0|jonasschnelli|I think the whole light client (SPV) mode needs discussion firsat
138 2018-01-10 22:50:10 0|jonasschnelli|*first
139 2018-01-10 22:50:31 0|BlueMatt|promag: I know, I know
140 2018-01-10 22:50:43 0|instagibbs|it's not that "light" :)
141 2018-01-10 22:52:08 0|jonasschnelli|instagibbs: you mean in regards of the code diff size? :)
142 2018-01-10 22:52:40 0|jonasschnelli|BlueMatt: 12138 pr description looks wrong formated
143 2018-01-10 22:53:43 0|BlueMatt|jonasschnelli: cause I copied from a comment in the code....picky picky ya'll
144 2018-01-10 22:54:14 0|jonasschnelli|BlueMatt: PR description is advertisement! You need to win some reviewers with it. :)
145 2018-01-10 22:54:38 0|BlueMatt|if that's our model of review I think we're screwed....
146 2018-01-10 22:54:52 0|jonasschnelli|heh,... that's indeed true.
147 2018-01-10 22:55:36 0|gribble|https://github.com/bitcoin/bitcoin/issues/10984 | Allow 2 simultaneous (compact-)block downloads by TheBlueMatt ÷ Pull Request #10984 ÷ bitcoin/bitcoin ÷ GitHub
148 2018-01-10 23:19:32 0|promag|forever alone #12083
149 2018-01-10 23:19:33 0|gribble|https://github.com/bitcoin/bitcoin/issues/12083 | Improve getchaintxstats test coverage by promag ÷ Pull Request #12083 ÷ bitcoin/bitcoin ÷ GitHub