--- Log opened Fri Apr 16 00:00:27 2021 00:44 -!- bizzy [49ae29b1@c-73-174-41-177.hsd1.wv.comcast.net] has joined ##taproot-activation 00:45 -!- bizzy [49ae29b1@c-73-174-41-177.hsd1.wv.comcast.net] has quit [Client Quit] 00:56 -!- kabaum [~kabaum@h-13-35.A163.priv.bahnhof.se] has quit [Ping timeout: 246 seconds] 01:09 -!- kabaum [~kabaum@h-13-35.A163.priv.bahnhof.se] has joined ##taproot-activation 01:14 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection] 01:14 -!- shesek [~shesek@unaffiliated/shesek] has joined ##taproot-activation 01:59 -!- Emcy_ [~Emcy@unaffiliated/emcy] has joined ##taproot-activation 02:02 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 246 seconds] 03:02 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has joined ##taproot-activation 03:03 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 03:09 -!- RusAlex [~Chel@unaffiliated/rusalex] has quit [Ping timeout: 265 seconds] 03:18 -!- RusAlex [~Chel@unaffiliated/rusalex] has joined ##taproot-activation 03:39 -!- gevs [~greg@244.red-79-153-37.dynamicip.rima-tde.net] has joined ##taproot-activation 03:39 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net] 03:41 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined ##taproot-activation 03:52 -!- BB-Martino [~martino@bitbargain.co.uk] has joined ##taproot-activation 03:52 -!- belcher_ is now known as belcher 03:55 -!- duringo [ad004d10@173.0.77.16] has quit [Quit: Connection closed] 04:02 -!- intx [intx@unaffiliated/intx] has joined ##taproot-activation 04:16 -!- livestradamus [~quassel@unaffiliated/livestradamus] has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.] 04:17 -!- livestradamus [~quassel@unaffiliated/livestradamus] has joined ##taproot-activation 05:06 -!- faketoshi [~quassel@static-198-54-131-60.cust.tzulo.com] has quit [Ping timeout: 260 seconds] 05:07 -!- bcman [~quassel@static-198-54-131-60.cust.tzulo.com] has joined ##taproot-activation 05:43 -!- mips [~mips@gateway/tor-sasl/mips] has quit [Remote host closed the connection] 05:43 -!- mips [~mips@gateway/tor-sasl/mips] has joined ##taproot-activation 06:05 -!- Matviy [45b56c08@c-69-181-108-8.hsd1.ca.comcast.net] has joined ##taproot-activation 06:08 -!- ctrlbreak_MAD [~ctrlbreak@159.2.165.130] has joined ##taproot-activation 06:52 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection] 06:53 -!- shesek [~shesek@unaffiliated/shesek] has joined ##taproot-activation 06:59 < AaronvanW> iiuc, mixing MTP and block height could lead to a statistically-implausible-but-not-impossible scenario where activation height actually comes before the end of the signaling period. (namely, if blocks are consistently mined much faster than the 10-minute average for a few months.) out of curiosity: could that be a problem in any way? 07:01 < AaronvanW> I guess a somewhat-real-world example of such a scenario would be a sudden breakthrough in ASIC technology. 07:02 < aj> AaronvanW: if the economy doesn't upgrade to software that enforces the new rules, miners could signal activation, then mine taproot-invalid txs into the chain after the activation height, without those blocks getting rejected (because people haven't upgraded quickly enough) leaving the few people that have upgraded following a dead chain 07:02 <@michaelfolkson> AaronvanW: Not impossible but close to zero probability. There would need to be *very* large increases in total network hash power at the beginning of every difficulty adjustment period 07:03 <@michaelfolkson> AaronvanW: To drag the activation block height forward months 07:03 < aj> AaronvanW: that's not particularly because of any mixture of MTP and height, it's because the activation is by height, and height comes earlier than expected, while people upgrading comes as late as expected 07:07 <@michaelfolkson> aj AaronvanW: This (extremely unlikely) scenario would complicate the scenario of some nodes using block height and some nodes using MTP on the network though 07:07 < AaronvanW> aj: My question is basically, what happens when the signaling threshold is met at a point in time that comes later than the block height at which it should be activated. 07:08 < AaronvanW> which is extremely unlikely but not impossible. 07:09 < aj> AaronvanW: if the threshold is met and lock in occurs before the min_activation_height, activation is delayed until min_activation_height is reached; if min_activation_height is earlier, then activation occurs 2016 blocks after lockin occurs 07:12 < AaronvanW> I see, thanks. 07:18 < aj> AaronvanW: you'd need a block to be found every 6m on average between now and august to trigger that behaviour i think 07:21 -!- copumpkin [~copumpkin@unaffiliated/copumpkin] has quit [Ping timeout: 240 seconds] 07:27 -!- duringo [ad004d10@173.0.77.16] has joined ##taproot-activation 07:27 -!- Majes [c0a1e550@192-161-229-192-161-229-80.cpe.sparklight.net] has joined ##taproot-activation 07:35 -!- OP_NOP_ [OP_NOP@gateway/vpn/privateinternetaccess/opnop/x-41418994] has quit [Ping timeout: 268 seconds] 07:50 <@michaelfolkson> Latest update on Taproot activation releases https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-April/018790.html 07:51 <@michaelfolkson> I would like to analyze the likelihood of one activating and one not re: "Bitcoin Core" and "Bitcoin Core 0.21.0-based Taproot Client" during their Speedy Trial deployments 07:51 -!- copumpkin [~copumpkin@unaffiliated/copumpkin] has joined ##taproot-activation 07:52 -!- commmon [~common@unaffiliated/common] has joined ##taproot-activation 07:53 <@michaelfolkson> It was pointed out to me that I don't even understand BIP 9 MTP versus pure MTP versus say BIP 113 MTP. So I need to sort that out... 07:56 -!- common [~common@unaffiliated/common] has quit [Ping timeout: 260 seconds] 07:57 -!- common [~common@unaffiliated/common] has joined ##taproot-activation 07:58 -!- commmon [~common@unaffiliated/common] has quit [Ping timeout: 240 seconds] 08:08 -!- copumpkin [~copumpkin@unaffiliated/copumpkin] has quit [Remote host closed the connection] 08:10 -!- p0x [~pox@gateway/tor-sasl/pox] has joined ##taproot-activation 08:10 -!- pox [~pox@gateway/tor-sasl/pox] has quit [Remote host closed the connection] 08:12 -!- OP_NOP [OP_NOP@gateway/vpn/privateinternetaccess/opnop/x-41418994] has joined ##taproot-activation 08:14 -!- copumpkin [~copumpkin@unaffiliated/copumpkin] has joined ##taproot-activation 08:16 -!- proofofkeags [~proofofke@97-118-239-55.hlrn.qwest.net] has joined ##taproot-activation 08:17 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-wozivfdmchvrtxja] has joined ##taproot-activation 08:23 -!- bcman is now known as faketoshi 08:28 -!- leevancleef [8074ecf1@128-116-236-241.static.eolo.it] has joined ##taproot-activation 08:45 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Ping timeout: 240 seconds] 08:48 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined ##taproot-activation 09:00 -!- mips [~mips@gateway/tor-sasl/mips] has quit [Remote host closed the connection] 09:01 -!- mips [~mips@gateway/tor-sasl/mips] has joined ##taproot-activation 09:09 -!- proofofkeags [~proofofke@97-118-239-55.hlrn.qwest.net] has quit [Ping timeout: 260 seconds] 09:24 -!- cguida [~Adium@205.209.28.54] has joined ##taproot-activation 09:34 -!- cguida [~Adium@205.209.28.54] has quit [Quit: Leaving.] 09:50 -!- mips [~mips@gateway/tor-sasl/mips] has quit [Remote host closed the connection] 09:51 -!- mips [~mips@gateway/tor-sasl/mips] has joined ##taproot-activation 09:51 < CubicEarth> what is the ST activation threshold? 90 % 09:52 <@michaelfolkson> CubicEarth: Yes 09:52 < CubicEarth> great 09:52 < CubicEarth> thanks 09:52 < CubicEarth> So much better than if it were 95% :) 10:12 <@michaelfolkson> CubicEarth: Right, I think so too. That was merged into BIP 8 back in February https://github.com/bitcoin/bips/pull/1069 10:14 <@michaelfolkson> CubicEarth: Or at least the recommendation for 90% was merged. Future soft forks (if they use BIP 8) aren't forced to use 90% 10:16 -!- cguida [~Adium@205.209.28.54] has joined ##taproot-activation 10:16 -!- OP_NOP [OP_NOP@gateway/vpn/privateinternetaccess/opnop/x-41418994] has quit [Remote host closed the connection] 10:17 -!- OP_NOP [OP_NOP@gateway/vpn/privateinternetaccess/opnop/x-41418994] has joined ##taproot-activation 10:22 -!- OP_NOP [OP_NOP@gateway/vpn/privateinternetaccess/opnop/x-41418994] has quit [Ping timeout: 268 seconds] 10:32 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 268 seconds] 10:33 -!- proofofkeags [~proofofke@205.209.28.54] has joined ##taproot-activation 11:04 -!- duringo [ad004d10@173.0.77.16] has quit [Quit: Connection closed] 11:05 -!- michaelfolkson changed the topic of ##taproot-activation to: Discussion of Taproot activation. Meetings on any Taproot activation topics may be scheduled by request and by submitting agenda to the bitcoin-dev mailing list. Logs: http://gnusha.org/taproot-activation/ Discussion on Taproot itself belongs in ##taproot-bip-review. 11:05 -!- mol [~mol@unaffiliated/molly] has joined ##taproot-activation 11:52 -!- sugarpuff [sid92283@gateway/web/irccloud.com/x-nacbdqrwazgydsoa] has joined ##taproot-activation 11:54 < sugarpuff> Sorry folks, I'm sure this has already been discussed in this channel, but I missed the discussion and can't find the info on bitcoincore.org ... Is 0.21.1 doing LOT=true or LOT=false by default...? How is Core activating taproot? 11:55 < jeremyrubin> the activation you may have heard about e.g. on twitter is not a release from Bitcoin Core org, the release mentioned by michaelfolkson on the mailing list will be announced when it is ready, shortly 11:55 < jeremyrubin> That will be a release from Bitcoin Core and will have information on bitcoincore.org updated as well as signatures from the usual 11:56 < sugarpuff> I'm referring to : https://github.com/bitcoin/bitcoin/releases/tag/v0.21.1rc1 11:56 < sugarpuff> what is that doing? LOT=true? LOT=false? Something differently entirely? 11:56 < jeremyrubin> different entirely, it's called Speedy Trial 11:57 < jeremyrubin> it does not have LOT=true though, but in general the LOT concept doesn't apply because the timeout for Speedy Trial is too fast for LOT to be considered 11:57 < jeremyrubin> timeout is in august this year 11:58 < sugarpuff> so it does this? https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-March/018583.html 11:58 < jeremyrubin> essentially, yes. That's a bit abstract on the concrete details, but the one merged is a narrowing of that doc 12:01 < luke-jr> sugarpuff: for a proper BIP8 (LOT=True) release, see https://bitcointaproot.cc 12:02 < jeremyrubin> factual statement: you can evaluate if you should run that or not independently. many core developers have suggested caution / advised against running it, and it is not the release being created by bitcoin core. "proper" is by fiat of luke-jr; DYOR 12:02 < jonatack> sugarpuff: https://twitter.com/jonatack/status/1383032324363845633 12:03 < jonatack> (https://bitcoinops.org/en/newsletters/2021/03/10/#a-short-duration-attempt-at-miner-activation with these parameters: https://github.com/bitcoin/bitcoin/pull/21686/files) 12:04 < luke-jr> jeremyrubin: quit trolling with these lies 12:04 < jeremyrubin> please point out the lie above 12:05 < jeremyrubin> 1. You can evaluate to run or not independently 12:05 < jeremyrubin> 2. many core devs have advised caution or not to run 12:05 < luke-jr> ""proper" is by fiat of luke-jr" 12:05 < jeremyrubin> 3. it's not being created by core 12:05 < luke-jr> it has widespread community support 12:06 < luke-jr> and there is no entity "Core" 12:06 < sugarpuff> Guys this has got the be the most confusing thing I've seen in a while, at least to lay people, and maybe even miners. With the link jonatack mentioned, with this ST thing, do miners need to set a parameter manually to indicate support? 12:06 < luke-jr> sugarpuff: yes, with any activation in general.. 12:06 < jeremyrubin> 4. You are the one declaring it to be "proper" here -- sugarpuff should DYOR to determine if that's accurate 12:07 < sugarpuff> Is this parameter that miners will be setting with 0.21.1 the LOT=true parameter or some other parameter? 12:07 < jeremyrubin> proper is a normative statement; and you are (to the extent you are accusing me of lying) lying by suggesting Core's release is not proper 12:07 < luke-jr> sugarpuff: miners don't set those parameters, just a bit signal in the block header 12:07 < luke-jr> jeremyrubin: it isn't. 12:08 < sugarpuff> ok, so they set some other parameter (would be great to know its name), and the whole process is opt-in, determined by PoW (miners)? 12:08 < harding> sugarpuff: if they run bitcoind and use the information provided by getblocktemplate, they sholudn't need to set anything. However, many (most?) miners do modify the block version they send manually; those miners will need to update a configuration variable. 12:09 < sugarpuff> ok, so... some miners will have the parameter set for them by default, and some will need to opt-in? 12:10 < sugarpuff> (is the parameter merely the version string?) 12:10 < harding> sugarpuff: yes, whether taproot activates with the initial speedy trial attempt or whether we need to consider other activation methods (including getting more people to use BIP8(LOT=True) depends on 90% of blocks signaling readiness for taproot in a retarget period; there should be about 6 or 7 periods, each 2,016 blocks long (about two weeks), where those signals will be counted. 12:11 < harding> sugarpuff: yes, the things miners will need to signal is a bit in the version bits field (which used to be called nVersion). 12:11 < harding> s/things/thing/ 12:12 < sugarpuff> so then, if all miners simply upgrade to 0.21.1, then taproot is guaranteed to activate? 12:12 < sugarpuff> (unless they modified their version thing?) 12:12 < harding> Exactly. 12:13 < sugarpuff> ok, perfect. Wow. Would be awesome to see that explained like on bitcoincore.org or something. thanks for helping me understand! 12:14 < harding> (If they update within the alotted time window, which is about three months.) 12:15 <@michaelfolkson> jeremyrubin: You can't say "factual statement" and then "proper is by fiat of luke-jr". There are other contributors to https://bitcointaproot.cc other than luke-jr 12:15 <@michaelfolkson> factual statement: you can evaluate if you should run that or not independently. many core developers have suggested caution / advised against running it, and it is not the release being created by bitcoin core. "proper" is by fiat of luke-jr; 12:16 <@michaelfolkson> Nowhere does it say, has Luke said, or anybody else involved in that release said that it is "fiat of luke-jr" 12:16 < jeremyrubin> I can say it 12:17 < harding> sugarpuff: 0.21.1 should include release notes explaining that. It's currently in Release Candidate (RC) where people are testing it and so, in theory, we could remove any features. For that reason, we don't usually publish official documentation about those new features. 12:17 < jeremyrubin> The software code has been written and reviewed by several Bitcoin Core developers. The releases are, however, maintained by two community members, Bitcoin Mechanic and Shinobi. Luke Dashjr has helped advise and make sure things get done properly and safely. 12:17 <@michaelfolkson> I'd prefer if you stuck to facts. But if you are going to stray from facts don't say it is a factual statement. 12:17 < jeremyrubin> it literally says luke-jr's role was in determining propriety 12:17 <@michaelfolkson> That is your opinion 12:17 < jeremyrubin> I'm quoting the site 12:17 < jeremyrubin> If others determined the propriety, let me know 12:18 < luke-jr> jeremyrubin: stop trolling. we were talking about the activation method, which was determined by community agreement. 12:18 < jeremyrubin> You called me a liar 12:18 < luke-jr> you lied. stop that and I won't have to. 12:19 < jeremyrubin> I substantiated the factual statement 12:20 < jeremyrubin> feel free to join #jeremy-is-a-liar if you're interested in discussing the matter further, feels off topic for here 12:20 < luke-jr> yes, keep your lies out of here. preferably just don't lie at all anymore. 12:20 <@michaelfolkson> I think this is for #bitcoin or somewhere else 12:21 -!- _joerodgers [joerodgers@gateway/vpn/mullvad/joerodgers/x-62861712] has quit [Quit: Leaving] 12:22 < harding> jeremyrubin: is there any agenda for the Tuesday meeting? 12:22 < harding> (preliminary agenda, obviously) 12:22 < jeremyrubin> trying to determine if meeting is required? 12:22 < jeremyrubin> Seems rc1 is on-track 12:23 < jeremyrubin> can just be a party, but I doubt AJ will be up at 5 for it 12:23 <@michaelfolkson> If you want to cancel please let me know. I'll inform mailing list 12:23 <@michaelfolkson> At the moment I've said there's a meeting 12:23 -!- OP_NOP [OP_NOP@gateway/vpn/privateinternetaccess/opnop/x-41418994] has joined ##taproot-activation 12:24 -!- stortz [c8b9c69a@unaffiliated/stortz] has joined ##taproot-activation 12:24 -!- stortz [c8b9c69a@unaffiliated/stortz] has quit [Client Quit] 12:24 < sugarpuff> harding: noted. btw guys, i hope y'all aren't going to start infighting, it's sad to see. if anyone needs counseling services feel free to DM and I'll do my best if around XD 12:25 <@michaelfolkson> sugarpuff: As long as you got answers to your questions that's all that matters. Things are a little tense 12:25 < jeremyrubin> sugarpuff: are you licensed? I've been told that I'm a liar so frequently I'm worried that it might pathological -- any diagnosis? 12:26 < harding> jeremyrubin: I can't think of anything that needs discussing at this point. I think it's probably fine to wait until Sunday to cancel if anyone is worried something will come up. 12:26 < BlueMatt> sugarpuff: I don't really think anyone is bothered with "infighting", basically only 3-5 people are pushing the weird fork client thing. 12:26 <@michaelfolkson> Please move this to a private conversation or #bitcoin jeremyrubin sugarpuff if it isn't activation related 12:27 < sugarpuff> roger! 12:27 < jeremyrubin> ver? 12:27 < luke-jr> ban roger 12:27 < sugarpuff> lol 12:27 < Murch> sugarpuff: There are just slight discrepancies in how people assay community consensus and what the best path forward is. My perception is that the two ideas have very different levels of support and it will work itself out naturally. 12:27 < jeremyrubin> consensus reached 12:27 < jeremyrubin> (actually roger was quite pleasant the other week on clubhouse) 12:28 <@michaelfolkson> Again this is #bitcoin territory I think 12:28 <@michaelfolkson> Let's leave this for activation discussion and questions please 12:29 < Murch> michaelfolkson: You mean me? 12:29 <@michaelfolkson> Murch: No you were fine. Discussion of Roger Ver I don't think is Taproot activation related unless he has a Taproot activation view 12:34 -!- Murch is now known as murch 12:36 -!- murch is now known as Murch 12:43 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net] 12:43 -!- blap [~gk@69.4.234.60] has joined ##taproot-activation 12:44 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined ##taproot-activation 13:05 < gevs> Jeez ok it even got me smiling xD don't let the politics rule! Out of this I am taking that activation will be available in 13:06 < gevs> *different fashions ; will be following for more info. Great to see many of you answering some basic questions. 13:07 < gevs> it would be the first time I am actively mining during such activation period ; that's why I am looking into a bit more details. Nothing big here though, using a pool actually so I'd think I have to do nothing ... but still interested. 13:08 < jeremyrubin> which pool are you using? 13:08 < jeremyrubin> Your pool might not allow you to customize signaling 13:08 < jeremyrubin> do your miners talk to your node? 13:09 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net] 13:09 -!- OP_NOP [OP_NOP@gateway/vpn/privateinternetaccess/opnop/x-41418994] has quit [Remote host closed the connection] 13:09 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined ##taproot-activation 13:22 -!- OP_NOP [OP_NOP@gateway/vpn/privateinternetaccess/opnop/x-41418994] has joined ##taproot-activation 13:27 < gevs> my miners use too much power for this planet ... they don't talk to a node of mine, sadly they needz the Google to connect with bitcoin :P 13:28 < gevs> You answer taught me just enough for the night I think ; 1) ill go and head down on own node setup ; 2) pool was probably too lazy of a choice, shoulda been running that node for much longer :) 13:28 < jeremyrubin> there are reasons to use a pool! 13:28 < jeremyrubin> depends how much hashrate you have 13:29 < jeremyrubin> if too small, then you'll not see regular income 13:30 < gevs> Even with pool I don't see regular income ... should tell you enough of my hashrate. 13:32 < gevs> Don't worry though, not trying to get the most of it here ; forging my own opinion is worth the bucks/setup-fun too :) 14:02 -!- mips [~mips@gateway/tor-sasl/mips] has quit [Remote host closed the connection] 14:02 -!- mips [~mips@gateway/tor-sasl/mips] has joined ##taproot-activation 14:27 -!- mol [~mol@unaffiliated/molly] has quit [Read error: Connection reset by peer] 14:27 -!- mol_ [~mol@unaffiliated/molly] has joined ##taproot-activation 14:29 -!- kabaum [~kabaum@h-13-35.A163.priv.bahnhof.se] has quit [Ping timeout: 252 seconds] 14:31 -!- gevs [~greg@244.red-79-153-37.dynamicip.rima-tde.net] has quit [Ping timeout: 240 seconds] 14:44 -!- greg [~greg@194.red-81-33-44.dynamicip.rima-tde.net] has joined ##taproot-activation 14:47 -!- blap [~gk@69.4.234.60] has quit [Quit: Leaving] 15:01 -!- grubles [~user@gateway/tor-sasl/grubles] has quit [Remote host closed the connection] 15:02 -!- grubles [~user@gateway/tor-sasl/grubles] has joined ##taproot-activation 15:30 -!- OP_NOP [OP_NOP@gateway/vpn/privateinternetaccess/opnop/x-41418994] has quit [Remote host closed the connection] 15:30 -!- OP_NOP [OP_NOP@gateway/vpn/privateinternetaccess/opnop/x-41418994] has joined ##taproot-activation 15:34 -!- OP_NOP [OP_NOP@gateway/vpn/privateinternetaccess/opnop/x-41418994] has quit [Ping timeout: 240 seconds] 15:36 -!- OP_NOP [OP_NOP@gateway/vpn/privateinternetaccess/opnop/x-41418994] has joined ##taproot-activation 15:38 -!- bcman [~quassel@static-198-54-131-171.cust.tzulo.com] has joined ##taproot-activation 15:40 -!- faketoshi [~quassel@static-198-54-131-60.cust.tzulo.com] has quit [Ping timeout: 240 seconds] 15:40 -!- bcman is now known as faketoshi 15:43 -!- OP_NOP [OP_NOP@gateway/vpn/privateinternetaccess/opnop/x-41418994] has quit [Ping timeout: 246 seconds] 15:56 -!- duringo [ad004d10@173.0.77.16] has joined ##taproot-activation 16:11 -!- OP_NOP [OP_NOP@gateway/vpn/privateinternetaccess/opnop/x-41418994] has joined ##taproot-activation 16:35 -!- mips_ [~mips@gateway/tor-sasl/mips] has joined ##taproot-activation 16:37 -!- mips [~mips@gateway/tor-sasl/mips] has quit [Ping timeout: 240 seconds] 16:39 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 16:42 -!- cguida [~Adium@205.209.28.54] has quit [Quit: Leaving.] 16:59 -!- belcher_ [~belcher@unaffiliated/belcher] has joined ##taproot-activation 17:02 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds] 17:07 -!- belcher_ is now known as belcher 17:11 -!- cguida [~Adium@2601:282:200:ae00:c5f0:2b22:cad6:ea19] has joined ##taproot-activation 17:13 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 240 seconds] 17:18 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined ##taproot-activation 17:24 -!- mol [~mol@unaffiliated/molly] has joined ##taproot-activation 17:24 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 252 seconds] 17:40 -!- cguida [~Adium@2601:282:200:ae00:c5f0:2b22:cad6:ea19] has quit [Quit: Leaving.] 17:41 -!- cguida [~Adium@2601:282:200:ae00:c5f0:2b22:cad6:ea19] has joined ##taproot-activation 17:43 -!- cguida [~Adium@2601:282:200:ae00:c5f0:2b22:cad6:ea19] has quit [Client Quit] 18:06 -!- copumpkin [~copumpkin@unaffiliated/copumpkin] has quit [Quit: Hmmm] 18:07 -!- proofofkeags [~proofofke@205.209.28.54] has quit [Ping timeout: 240 seconds] 18:09 -!- willcl_ark [~quassel@unaffiliated/willcl-ark/x-8282106] has quit [Quit: No Ping reply in 180 seconds.] 18:12 -!- willcl_ark [~quassel@unaffiliated/willcl-ark/x-8282106] has joined ##taproot-activation 18:59 -!- Murch [murch@gateway/shell/hashbang/x-ggcrxwvisrzglhkt] has quit [Read error: Connection reset by peer] 19:24 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined ##taproot-activation 19:27 -!- OP_NOP [OP_NOP@gateway/vpn/privateinternetaccess/opnop/x-41418994] has quit [Ping timeout: 252 seconds] 19:29 -!- mol_ [~mol@unaffiliated/molly] has joined ##taproot-activation 19:32 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 246 seconds] 19:36 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 265 seconds] 19:38 -!- mol_ [~mol@unaffiliated/molly] has joined ##taproot-activation 19:53 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds] 20:12 -!- Matviy [45b56c08@c-69-181-108-8.hsd1.ca.comcast.net] has quit [Quit: Connection closed] 20:21 -!- mips_ is now known as mips 20:45 -!- OP_NOP [OP_NOP@gateway/vpn/privateinternetaccess/opnop/x-41418994] has joined ##taproot-activation 21:51 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined ##taproot-activation 22:23 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 23:04 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 240 seconds] 23:05 -!- faketoshi [~quassel@static-198-54-131-171.cust.tzulo.com] has quit [Read error: Connection reset by peer] 23:06 -!- bcman [~quassel@static-198-54-131-171.cust.tzulo.com] has joined ##taproot-activation 23:14 -!- copumpkin [~copumpkin@unaffiliated/copumpkin] has joined ##taproot-activation 23:19 -!- contrapumpkin [~copumpkin@unaffiliated/copumpkin] has joined ##taproot-activation 23:22 -!- copumpkin [~copumpkin@unaffiliated/copumpkin] has quit [Ping timeout: 246 seconds] 23:55 -!- contrapumpkin [~copumpkin@unaffiliated/copumpkin] has quit [Read error: Connection reset by peer] --- Log closed Sat Apr 17 00:00:28 2021