--- Day changed Mon Jan 18 2021 00:19 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection] 01:04 < wumpus> queip: you mean the datagram based one? doing effectively bitcoin-P2P over UDP is a big change, yes, i'm not sure we really *need* that kind of performance, besides the choose-eviction logic there's nothing in the protocol that is latency sensitive 01:05 < wumpus> midnight: i'd like to know too (also why you can't be public about this) 01:45 < wumpus> queip: unless you're a miner and want to to propagate your blocks as quickly as possible, ofc 01:51 -!- midnight [~midnight@unaffiliated/midnightmagic] has quit [Ping timeout: 258 seconds] 01:53 -!- midnight [~midnight@unaffiliated/midnightmagic] has joined #bitcoin-core-pr-reviews 02:28 -!- sdaftuar [~sdaftuar@gateway/tor-sasl/sdaftuar] has quit [Ping timeout: 268 seconds] 02:30 -!- sdaftuar [~sdaftuar@gateway/tor-sasl/sdaftuar] has joined #bitcoin-core-pr-reviews 03:20 -!- Anabelle41Hills [~Anabelle4@static.57.1.216.95.clients.your-server.de] has joined #bitcoin-core-pr-reviews 03:25 -!- Anabelle41Hills [~Anabelle4@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 240 seconds] 03:36 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #bitcoin-core-pr-reviews 03:36 -!- SurajUpadhyay [uid421192@gateway/web/irccloud.com/x-qdlznhybtnwfiogk] has quit [Quit: Connection closed for inactivity] 03:39 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 256 seconds] 03:48 -!- seven_ [~seven@cpe-90-157-197-248.static.amis.net] has joined #bitcoin-core-pr-reviews 04:44 -!- belcher_ is now known as belcher 04:45 -!- mblackmblack [~matt@178.128.230.221] has quit [Ping timeout: 256 seconds] 04:47 -!- mblackmblack [~matt@178.128.230.221] has joined #bitcoin-core-pr-reviews 04:56 -!- Netsplit *.net <-> *.split quits: patriot2939, troygior1hev, notmandatory, gwillen, rjected, sanketcell 04:59 -!- drbrule [sid395654@gateway/web/irccloud.com/x-paaykgotjsetujxc] has quit [Ping timeout: 264 seconds] 04:59 -!- gwillen [~gwillen@unaffiliated/gwillen] has joined #bitcoin-core-pr-reviews 04:59 -!- notmandatory [notmandato@2600:3c00::f03c:92ff:fe8e:dce6] has joined #bitcoin-core-pr-reviews 04:59 -!- rjected [~weechat-h@natp-128-119-202-13.wireless.umass.edu] has joined #bitcoin-core-pr-reviews 04:59 -!- sanketcell [~sanketcel@ec2-100-24-255-95.compute-1.amazonaws.com] has joined #bitcoin-core-pr-reviews 04:59 -!- troygior1hev [~troygiors@d67-193-140-136.home3.cgocable.net] has joined #bitcoin-core-pr-reviews 04:59 -!- patriot2939 [~patriot29@unaffiliated/patriot2939] has joined #bitcoin-core-pr-reviews 05:00 -!- drbrule [sid395654@gateway/web/irccloud.com/x-giisfptxuqrnwclp] has joined #bitcoin-core-pr-reviews 05:02 -!- sunon [duncandean@gateway/shell/matrix.org/x-hdlpzrpouedmkkky] has quit [Ping timeout: 258 seconds] 05:03 -!- robert_spigler [robertspig@gateway/shell/matrix.org/x-tfhwtnqeceybafna] has quit [Ping timeout: 258 seconds] 05:19 -!- robert_spigler [robertspig@gateway/shell/matrix.org/x-gzvtgaykxeobebgj] has joined #bitcoin-core-pr-reviews 05:28 -!- sunon [duncandean@gateway/shell/matrix.org/x-bkyuiegjifatwxfv] has joined #bitcoin-core-pr-reviews 05:34 -!- robert_spigler [robertspig@gateway/shell/matrix.org/x-gzvtgaykxeobebgj] has quit [Ping timeout: 244 seconds] 05:35 -!- sunon [duncandean@gateway/shell/matrix.org/x-bkyuiegjifatwxfv] has quit [Ping timeout: 240 seconds] 05:43 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 265 seconds] 06:04 -!- robert_spigler [robertspig@gateway/shell/matrix.org/x-jarlquohwdvsreoz] has joined #bitcoin-core-pr-reviews 06:13 -!- sunon [duncandean@gateway/shell/matrix.org/x-sdwghipzkpdjhtnu] has joined #bitcoin-core-pr-reviews 06:23 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-core-pr-reviews 06:23 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-pr-reviews 06:57 < queip> wumpus: what I had on mind, is that with the default i2p torrent client i2p Snark, it was said that too bad it uses stream sockets instead message, as going for messages would be better for this kind of work load. due to low round-trip or smth. That was some time ago so better double check if I get this right 07:27 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 07:37 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 08:04 -!- pinheadmz [~pinheadmz@68.161.139.178] has quit [Quit: pinheadmz] 08:08 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 246 seconds] 08:12 -!- pinheadmz [~pinheadmz@68.161.139.178] has joined #bitcoin-core-pr-reviews 08:14 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-core-pr-reviews 08:43 -!- musdom1 [~Thunderbi@202.184.0.102] has joined #bitcoin-core-pr-reviews 08:44 -!- musdom [~Thunderbi@202.184.0.102] has quit [Ping timeout: 256 seconds] 08:44 -!- musdom1 is now known as musdom 08:56 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-pr-reviews 08:56 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Disconnected by services] 08:56 -!- vasild_ is now known as vasild 09:06 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 09:37 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 09:38 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 09:46 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 240 seconds] 09:53 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has joined #bitcoin-core-pr-reviews 10:09 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 10:10 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 10:18 -!- musdom [~Thunderbi@202.184.0.102] has quit [Ping timeout: 264 seconds] 10:35 -!- daniel10012 [ac4af2c5@cpe-172-74-242-197.sc.res.rr.com] has joined #bitcoin-core-pr-reviews 10:37 -!- daniel10012 [ac4af2c5@cpe-172-74-242-197.sc.res.rr.com] has quit [Client Quit] 10:41 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 10:42 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 11:13 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 11:14 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 11:34 -!- norisgOG [~norisgOG@185.254.75.53] has joined #bitcoin-core-pr-reviews 11:35 < norisgOG> Hi, I am having a basic question concering the sequence number field: what is the nlocktime used for when the nsequence number provides a time delta for the output being spent? 11:35 < norisgOG> BIP68 I guess 11:37 < pinheadmz> norisgOG might help: https://bitcoin.stackexchange.com/questions/88289/what-is-transaction-finality 11:39 < norisgOG> pinheadmz thanks perfect explanation in this article 11:45 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 11:46 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 11:47 -!- norisgOG [~norisgOG@185.254.75.53] has quit [Ping timeout: 264 seconds] 11:53 -!- norisgOG_ [~norisgOG@185.254.75.42] has joined #bitcoin-core-pr-reviews 12:05 < norisgOG_> pinheadmz just some question to this stackoverflow post, so the consensus code checks every transaction whether it is finalized right? 12:06 < norisgOG_> so the first check is if nlocktime = 0, so if its not set is atomatically finalised ? 12:07 < norisgOG_> https://github.com/bitcoin/bitcoin/blob/03858b23fe1d17e681eb18d24602b276020295a0/src/consensus/tx_verify.cpp#L17-L28 12:10 < norisgOG_> the second check is whether the nlocktime is smaller than either the blockheight or the blocktime (500000000) but why smaller, I thought should be bigger to be valid, I think something is really wrong in my understanding here 12:14 < norisgOG_> sorry I got it, think error 12:14 < norisgOG_> the blockheight is the block in which the transaction is currently in, now < makes sense 12:16 < pinheadmz> norisgOG_ well its not in that block *yet* right? It might be deemed invalid by this check 12:17 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 12:17 < norisgOG_> pinheadmz ohh totally right agree, do you know whether most of transactions set the nlocktime to 0 12:17 < norisgOG_> the normal transactions 12:18 < norisgOG_> p2pkh 12:18 < pinheadmz> norisgOG_ actually i think the bitcoin core default is to set locktime to the current block height or current height + 1 12:18 < pinheadmz> the reason is to dis-incentivize miners from trying to perform deep reorgs 12:18 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 12:18 < pinheadmz> because with the locktime in place, a deep reorg wont be able to "sweep" the last several blocks worht of TXs into one new block 12:19 < norisgOG_> ok still trying to grasp what a deep reorg is, so you mean miners reorging their mempool or already mined blocks? 12:20 < pinheadmz> consider: https://blockstream.info/tx/02b39aac581c6baf333734a44c50b5ce18bb91478a92217866e8261c140a8378 12:20 < pinheadmz> locktime 666648 confirmed in block 666649 12:21 < pinheadmz> if there is a reorg that disconnects block 666649 and 666648 - this TX will not be valid in the *NEW* 666648 12:21 < pinheadmz> because of its lock time 12:21 < pinheadmz> so as the miner subsidy decreases and TX fees become more important, a miner looking at this TX might think "hey Im going to reorg the chain so *I* can mine this tx instead of my competitor" 12:22 < pinheadmz> sorry this is tangential to your first question 12:22 < norisgOG_> ohh very good explanation understand it now 12:22 < pinheadmz> if you look through the block explorer you will see a lot of TXs with locktime 0 as well 12:27 < norisgOG_> pinheadmz so when considering coinbase transaction, the regtest mode said it can only be spent after 100 blocks, so the n locktime of the previous tx must also be checked so nlocktime of both the previous tx and the actual tx have to be checked right? 12:28 < pinheadmz> mmmm the coinbase 100-blocks thing is different. Thats a hard consensus rule that can not be changed by locktime 12:33 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Quit: The Lounge - https://thelounge.chat] 12:34 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #bitcoin-core-pr-reviews 12:35 < norisgOG_> ok thanks 12:44 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection] 12:44 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-pr-reviews 12:49 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 12:50 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 13:22 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 13:27 -!- jadi [~jadi@178.131.52.33] has quit [Ping timeout: 256 seconds] 13:41 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has quit [Ping timeout: 268 seconds] 14:02 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has joined #bitcoin-core-pr-reviews 14:04 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has quit [Client Quit] 14:32 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has joined #bitcoin-core-pr-reviews 14:34 < willcl_ark> norisgOG_: the common parlance is "fee sniping" https://bitcoin.stackexchange.com/questions/48384/why-bitcoin-core-creates-time-locked-transactions-by-default 15:15 < norisgOG_> willcl_ark thx 15:23 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 15:24 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 15:52 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 256 seconds] 15:53 -!- jonatack [~jon@109.202.107.5] has joined #bitcoin-core-pr-reviews 15:54 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 15:56 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 16:02 -!- norisgOG_ [~norisgOG@185.254.75.42] has quit [Ping timeout: 264 seconds] 16:15 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 16:16 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #bitcoin-core-pr-reviews 16:26 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 16:27 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 16:58 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 16:59 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 17:30 -!- queip [~queip@unaffiliated/rezurus] has quit [Remote host closed the connection] 17:31 -!- queip [~queip@unaffiliated/rezurus] has joined #bitcoin-core-pr-reviews 18:05 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 18:06 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 18:37 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 18:38 -!- musdom [~Thunderbi@202.184.0.102] has joined #bitcoin-core-pr-reviews 18:39 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 19:10 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 19:11 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 20:14 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 20:20 -!- jadi [~jadi@178.131.52.33] has quit [Ping timeout: 264 seconds] 20:56 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Disconnected by services] 20:56 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-pr-reviews 20:56 -!- vasild_ is now known as vasild 22:15 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 22:16 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 22:47 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 22:48 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 23:18 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews 23:19 -!- jadi [~jadi@178.131.52.33] has quit [Remote host closed the connection] 23:29 -!- musdom1 [~Thunderbi@202.184.0.102] has joined #bitcoin-core-pr-reviews 23:31 -!- musdom [~Thunderbi@202.184.0.102] has quit [Ping timeout: 256 seconds] 23:31 -!- queip [~queip@unaffiliated/rezurus] has quit [Remote host closed the connection] 23:31 -!- musdom1 is now known as musdom 23:32 -!- queip_ [~queip@unaffiliated/rezurus] has joined #bitcoin-core-pr-reviews 23:33 -!- queip_ is now known as queip 23:49 -!- jadi [~jadi@178.131.52.33] has joined #bitcoin-core-pr-reviews