1 2018-05-07 16:37:34 <rsrx> how do I mute gribble?
 2 2018-05-07 16:43:07 <teward> rsrx: "mute" gribble?
 3 2018-05-07 16:43:23 <rsrx> teward,  everytime I join the network gribble pms me
 4 2018-05-07 16:43:59 <teward> rsrx: the only way to 'mute' gribble is to do a /ignore on Gribble
 5 2018-05-07 16:44:08 <rsrx> ok
 6 2018-05-07 16:44:11 <rsrx> i'll do that
 7 2018-05-07 16:44:16 <teward> the other problem though
 8 2018-05-07 16:44:25 <teward> is that you have a broken client if i'm seeing your connection logs.
 9 2018-05-07 16:44:31 <teward> but this is all offtopic for this channel :;p
10 2018-05-07 16:44:38 <rsrx> connection logs?
11 2018-05-07 16:45:42 <rsrx> if you're talking about ctcp i dont see hows that useful
12 2018-05-07 16:46:19 <teward> i'm taking this discussion off-channel because it's not on topic for #bitcoin-dev
13 2018-05-07 16:46:48 <rsrx> lol
14 2018-05-07 23:27:14 <jimpo> satwo: nLockTime doesn't need to be at the input level because the transaction can either be fully included or not included (I guess only you are using weird sighash flags)
15 2018-05-07 23:27:51 <jimpo> and nSequence semantics, as per BIP 68, need to be at the input level because they specify a relative locktime to the corresponding spent output
16 2018-05-07 23:41:53 <satwo> That makes sense, thanks jimpo. I think the nSequence being used for RBF signaling threw me off, given that it applies to the entire transaction if only one input signals it.
17 2018-05-07 23:48:36 <jimpo> Yes, the RBF flag would make more sense at the transaction layer, but it is on nSequence instead because that was the only place to put it without changing the tx structure.