--- Log opened Sun Nov 14 00:00:32 2021
02:02 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has joined ##taproot-activation
02:02 -!- b10c [uid500648@ilkley.irccloud.com] has quit [Quit: Connection closed for inactivity]
05:02 -!- b10c [uid500648@ilkley.irccloud.com] has joined ##taproot-activation
05:03 < b10c> f2pool hadn't upgraded their infra to >v0.21.1: https://twitter.com/satofishi/status/1459868549674065926
05:03 -!- ksedgwic [~ksedgwicm@2001:470:69fc:105::ce1] has joined ##taproot-activation
05:04 -!- blkncd [sid505676@helmsley.irccloud.com] has joined ##taproot-activation
07:01 < nickler> only f2pool?
07:20 -!- b10c [uid500648@ilkley.irccloud.com] has quit [Quit: Connection closed for inactivity]
12:52 < DeanGuss> nor antpool it seems, the fist 3 blocks, 2 by antpool and 1 by f2pool didn't have any taproot spends although they were in the mempool at the time
14:54 -!- b10c [uid500648@ilkley.irccloud.com] has joined ##taproot-activation
15:59 < b10c> F2Pool and AntPool (I'm excluding two smaller pools that only mined a single block since activation): https://twitter.com/0xB10C/status/1460033874428317696
16:06 < darosior> So they were effectively lying by signaling readiness
16:33 < _aj_> not necessarily -- they could be generating blocks with an old node's getblocktemplate, but have that node only connect to the network through taproot-enforcing nodes
16:34 < _aj_> 2/3rds of blocks are still signalling on bit 2 post activation, which indicates they're manually setting the bit rather than getting it from getblocktemplate though
17:12 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has quit [Quit: Leaving...]
18:23 -!- b10c [uid500648@ilkley.irccloud.com] has quit [Quit: Connection closed for inactivity]
20:40 < luke-jr> smh
22:17 -!- CARO1 [~Cesar@2804:7f4:c1a5:6b60:1c72:f79f:ca48:33ef] has joined ##taproot-activation
22:17 -!- CARO [~Cesar@2804:7f4:c2a3:be42:2de5:c69:eb23:c5a9] has quit [Ping timeout: 246 seconds]
23:42 -!- virtu [~virtu@p5b15b1fe.dip0.t-ipconnect.de] has joined ##taproot-activation
23:43 < virtu> Hey! Is there already a standard way to measure Taproot adoption? Would you do a binary decision on the transaction-level based on whether one or more Taproot outputs are created or spent (like for segwit)? Or does something on the txout level make more sense? (e.g., using the ratio of the number of spent and created Taproot txouts vs. total number of txouts)
23:45 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has joined ##taproot-activation
--- Log closed Mon Nov 15 00:00:34 2021