--- Day changed Sun Jan 26 2020 01:45 -!- orlovsky [~dr-orlovs@194.230.155.171] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 02:05 -!- dr-orlovsky [~dr-orlovs@194.230.155.171] has joined ##taproot-bip-review 02:14 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has joined ##taproot-bip-review 02:19 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has quit [Ping timeout: 268 seconds] 02:44 -!- kabaum [~kabaum@2001:9b1:efd:9b00::281] has joined ##taproot-bip-review 02:53 -!- dr-orlovsky [~dr-orlovs@194.230.155.171] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 04:25 -!- dr-orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has joined ##taproot-bip-review 04:41 -!- dr-orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 07:25 -!- dr-orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has joined ##taproot-bip-review 07:28 -!- orlovsky [~dr-orlovs@194.230.155.171] has joined ##taproot-bip-review 07:31 -!- dr-orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has quit [Ping timeout: 268 seconds] 08:57 -!- pinheadmz [~matthewzi@pool-100-33-69-78.nycmny.fios.verizon.net] has quit [Quit: pinheadmz] 09:02 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has joined ##taproot-bip-review 09:07 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has quit [Quit: notmandatory] 09:21 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has joined ##taproot-bip-review 09:32 -!- pinheadmz [~matthewzi@pool-100-33-69-78.nycmny.fios.verizon.net] has joined ##taproot-bip-review 09:49 < pinheadmz> I notice in the actual PR to bitcoin core, gbt_force is set to true for taproot - was that the case for segwit as well? Or did miners have to specify "segwit" in the "rules" field for GBT? 09:51 < sipa> see bip145 09:52 < sipa> (i have not thought hard about interaction between GBT and taproot; code is obviously WIP) 09:55 < pinheadmz> i was asking more in reference to signaling and activation. IIUC, if gbt_force = false, the mining software (outside of bitcoin core) must specify the rule to set the bits in the version ? 10:20 < sipa> i don't exactly remember what the semantics of the GBT values and gbt_force are 10:26 < gmaxwell> uh there isn't any special need for mining support for this. 10:27 < gmaxwell> segwit was special. 10:43 < pinheadmz> right ok I think that answers my quesiton: for segwit, just upgrading to v13.1 wasn't enough to set the bit, because the gbt client had to be ready as well. 10:47 < sipa> right 10:50 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has quit [Quit: notmandatory] 10:55 -!- orlovsky [~dr-orlovs@194.230.155.171] has quit [Read error: Connection reset by peer] 10:56 -!- dr-orlovsky [~dr-orlovs@194.230.155.171] has joined ##taproot-bip-review 11:36 < luke-jr> pinheadmz: gbt_force is unrelated to miner required to specify.. it means the miner must reject the template if they don't support it 11:37 < luke-jr> unless taproot is significantly changing GBT itself (unlikely, though I'm not 100% sure) it should use gbt_force so old miners accept it 11:37 < luke-jr> the client-side rule list just tells the server what rules the client knows, so the server can prepare a compatible template 11:38 < sipa> ok so gbt_force should be false for taproot 11:39 < sipa> i'm pretty sure that miners need no adjustments 11:39 < luke-jr> sipa: true 11:39 < luke-jr> gbt_force = miners can ignore the rule if they use the template as-is 11:39 < luke-jr> gbt_force=false -> miners must support the rule period 11:40 < sipa> ah 11:40 < sipa> what if miners don't need to do anything at all? 11:40 -!- orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has joined ##taproot-bip-review 11:40 < luke-jr> miners must always understand all rules to make any modificatiosn to the template 11:41 < luke-jr> if they make no modifications, gbt_force=true allows them to use the template as-is 11:41 < sipa> ok 11:43 -!- dr-orlovsky [~dr-orlovs@194.230.155.171] has quit [Ping timeout: 265 seconds] 11:50 < gmaxwell> luke-jr: you can happily drop transactions and such, taproot is just a new signature style. 11:50 < gmaxwell> the only modification you can't make is adding transactions that didn't come from your mempool. 12:05 < luke-jr> gmaxwell: GBT isn't fine-grained enough to convey that :p 12:39 -!- orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has quit [Remote host closed the connection] 12:43 -!- dr-orlovsky [~dr-orlovs@194.230.147.90] has joined ##taproot-bip-review 12:44 -!- orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has joined ##taproot-bip-review 12:44 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net] 12:46 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined ##taproot-bip-review 12:47 -!- dr-orlovsky [~dr-orlovs@194.230.147.90] has quit [Ping timeout: 260 seconds] 13:04 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has joined ##taproot-bip-review 14:37 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has quit [Quit: notmandatory] 17:02 -!- orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 17:11 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 17:24 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has joined ##taproot-bip-review 18:50 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has quit [Quit: notmandatory] 20:16 -!- dr-orlovsky [~dr-orlovs@77-58-192-184.dclient.hispeed.ch] has joined ##taproot-bip-review 20:26 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has joined ##taproot-bip-review 23:49 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has quit [Quit: notmandatory]