--- Day changed Fri Apr 06 2018 00:03 -!- rods1 [~r251d@2600:1700:e350:37f0:bd76:a85b:4402:2605] has quit [Read error: Connection reset by peer] 00:03 -!- rods1 [~r251d@2600:1700:e350:37f0:bd76:a85b:4402:2605] has joined #bitcoin-core-dev 00:07 -!- aruns [~indistylo@119.82.105.106] has quit [Ping timeout: 240 seconds] 00:24 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 276 seconds] 00:25 -!- booyah_ [~bb@193.25.1.157] has joined #bitcoin-core-dev 00:26 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 00:29 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev 00:34 -!- zarez [~Thunderbi@fs-93-93-44-38.fullsave.info] has joined #bitcoin-core-dev 00:49 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 01:05 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev 01:07 -!- Madisen45Reynold [~Madisen45@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 276 seconds] 01:13 -!- atroxes [~atroxes@unaffiliated/atroxes] has quit [Ping timeout: 268 seconds] 01:15 -!- atroxes [~atroxes@unaffiliated/atroxes] has joined #bitcoin-core-dev 01:20 -!- murrayn [~dafuq@unaffiliated/murrayn] has quit [Read error: Connection reset by peer] 01:21 -!- murrayn [~dafuq@S01061cabc0b054b3.ok.shawcable.net] has joined #bitcoin-core-dev 01:21 -!- murrayn [~dafuq@S01061cabc0b054b3.ok.shawcable.net] has quit [Changing host] 01:21 -!- murrayn [~dafuq@unaffiliated/murrayn] has joined #bitcoin-core-dev 01:34 -!- unholymachine [~quassel@2601:8c:c003:9f16:1188:b7f7:521a:56c4] has quit [Ping timeout: 265 seconds] 01:35 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 01:37 -!- unholymachine [~quassel@c-69-248-123-139.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 01:40 -!- promag [~promag@bl19-45-51.dsl.telepac.pt] has joined #bitcoin-core-dev 01:42 -!- promag [~promag@bl19-45-51.dsl.telepac.pt] has quit [Remote host closed the connection] 01:43 -!- rex4539 [~textual@2a02:587:3514:8600:fb:9274:e68:7c8c] has quit [Remote host closed the connection] 01:46 -!- rex4539 [~textual@2a02:587:3514:8600:fb:9274:e68:7c8c] has joined #bitcoin-core-dev 01:47 -!- lman [5530383d@gateway/web/cgi-irc/kiwiirc.com/ip.85.48.56.61] has joined #bitcoin-core-dev 01:47 -!- murrayn [~dafuq@unaffiliated/murrayn] has quit [Read error: Connection reset by peer] 01:48 -!- murrayn [~dafuq@unaffiliated/murrayn] has joined #bitcoin-core-dev 01:58 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 01:59 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 02:02 -!- zigen [~zigen@fs276ed17b.tkyc008.ap.nuro.jp] has joined #bitcoin-core-dev 02:02 -!- Eldora75Hettinge [~Eldora75H@ns334669.ip-5-196-64.eu] has joined #bitcoin-core-dev 02:06 -!- zigen [~zigen@fs276ed17b.tkyc008.ap.nuro.jp] has quit [Ping timeout: 256 seconds] 02:11 < bitcoin-git> [bitcoin] practicalswift opened pull request #12901: build: Show enabled sanitizers in configure output (master...print-enabled-sanitizers-in-configure-output) https://github.com/bitcoin/bitcoin/pull/12901 02:13 -!- Eldora75Hettinge [~Eldora75H@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 256 seconds] 02:15 -!- davec_ [~davec@cpe-24-243-249-218.hot.res.rr.com] has quit [Ping timeout: 264 seconds] 02:17 -!- DrOlmer [~DrOlmer@unaffiliated/drolmer] has quit [Ping timeout: 276 seconds] 02:17 -!- zigen [~zigen@fs276ed17b.tkyc008.ap.nuro.jp] has joined #bitcoin-core-dev 02:18 -!- DrOlmer [~DrOlmer@unaffiliated/drolmer] has joined #bitcoin-core-dev 02:23 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 02:25 -!- cryptojanitor [uid278088@gateway/web/irccloud.com/x-hsdcdvrymuvyzncd] has joined #bitcoin-core-dev 02:27 -!- zigen [~zigen@fs276ed17b.tkyc008.ap.nuro.jp] has quit [Remote host closed the connection] 02:27 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 260 seconds] 02:36 -!- davec [~davec@cpe-24-243-249-218.hot.res.rr.com] has joined #bitcoin-core-dev 02:37 -!- zigen [~zigen@fs276ed17b.tkyc008.ap.nuro.jp] has joined #bitcoin-core-dev 02:39 -!- gwillen [~gwillen@unaffiliated/gwillen] has quit [Ping timeout: 264 seconds] 02:42 -!- gwillen [~gwillen@unaffiliated/gwillen] has joined #bitcoin-core-dev 02:44 -!- zigen [~zigen@fs276ed17b.tkyc008.ap.nuro.jp] has quit [Remote host closed the connection] 02:55 -!- arbitrary_guy [~arbitrary@c-67-183-30-122.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 03:02 -!- Conner40VonRuede [~Conner40V@ns334669.ip-5-196-64.eu] has joined #bitcoin-core-dev 03:08 -!- jtimon [~quassel@142.29.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 03:17 -!- maxmatics [d80dc684@gateway/web/freenode/ip.216.13.198.132] has joined #bitcoin-core-dev 03:18 < maxmatics> hello world. 03:32 -!- arbitrary_guy [~arbitrary@c-67-183-30-122.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 03:39 -!- arbitrary_guy [~arbitrary@c-67-183-30-122.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 03:41 -!- maxmatics [d80dc684@gateway/web/freenode/ip.216.13.198.132] has quit [Quit: Page closed] 03:44 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 03:45 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 04:04 -!- pyericz [~pyericz@183.250.230.254] has joined #bitcoin-core-dev 04:05 -!- pyericz [~pyericz@183.250.230.254] has quit [Client Quit] 04:10 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 04:11 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 04:15 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 256 seconds] 04:19 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 04:23 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has quit [Ping timeout: 240 seconds] 04:26 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has joined #bitcoin-core-dev 04:31 -!- jojeyh [~delphi@2602:306:b8b6:b970:e941:3d05:c46d:48a3] has joined #bitcoin-core-dev 04:37 -!- mrannanay [uid222022@gateway/web/irccloud.com/x-ckctdhphfrfigjrw] has joined #bitcoin-core-dev 04:43 -!- pyericz [~pyericz@183.250.230.254] has joined #bitcoin-core-dev 04:44 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 04:48 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 255 seconds] 04:49 -!- Conner40VonRuede [~Conner40V@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 268 seconds] 04:50 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has quit [Read error: Connection reset by peer] 04:50 -!- esotericnonsens_ [~esotericn@unaffiliated/esotericnonsense] has joined #bitcoin-core-dev 04:58 -!- zautomata1 [~zautomata@41.232.208.46] has quit [Quit: WeeChat 1.9.1] 05:02 -!- Jaleel25Walter [~Jaleel25W@ns334669.ip-5-196-64.eu] has joined #bitcoin-core-dev 05:18 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has quit [Ping timeout: 240 seconds] 05:27 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has joined #bitcoin-core-dev 05:27 -!- pyericz [~pyericz@183.250.230.254] has quit [Quit: This computer has gone to sleep] 05:29 -!- Jaleel25Walter [~Jaleel25W@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 240 seconds] 05:36 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 260 seconds] 05:40 -!- esotericnonsens_ is now known as esotericnonsense 05:51 -!- jojeyh [~delphi@2602:306:b8b6:b970:e941:3d05:c46d:48a3] has quit [Ping timeout: 276 seconds] 05:51 -!- zarez [~Thunderbi@fs-93-93-44-38.fullsave.info] has quit [Ping timeout: 264 seconds] 06:02 -!- Blaze52Cormier [~Blaze52Co@ns334669.ip-5-196-64.eu] has joined #bitcoin-core-dev 06:09 -!- arubi_ [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 06:10 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #12898: Comment cleanup and consistency (master...patch-1) https://github.com/bitcoin/bitcoin/pull/12898 06:12 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 268 seconds] 06:14 -!- zarez [~Thunderbi@fs-93-93-44-38.fullsave.info] has joined #bitcoin-core-dev 06:17 -!- Blaze52Cormier [~Blaze52Co@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 260 seconds] 06:18 -!- qu4ku [~qu4ku@public-gprs351248.centertel.pl] has joined #bitcoin-core-dev 06:18 -!- zarez [~Thunderbi@fs-93-93-44-38.fullsave.info] has quit [Ping timeout: 240 seconds] 06:24 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 06:27 -!- wxss [~user@45.248.77.253] has joined #bitcoin-core-dev 06:30 -!- satwo [~textual@2602:306:378a:6fb0:3815:f5e3:df81:ad5c] has joined #bitcoin-core-dev 06:32 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 264 seconds] 06:34 -!- zarez [~Thunderbi@fs-93-93-44-38.fullsave.info] has joined #bitcoin-core-dev 06:39 -!- zarez [~Thunderbi@fs-93-93-44-38.fullsave.info] has quit [Ping timeout: 260 seconds] 06:40 -!- Deinogalerix21 [~Deinogale@185.169.255.9] has joined #bitcoin-core-dev 06:43 -!- qu4ku_ [~qu4ku@2a01:110f:f73:1b00:9438:52d4:feb5:1065] has joined #bitcoin-core-dev 06:43 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 06:44 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 06:44 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 06:45 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 06:46 -!- qu4ku [~qu4ku@public-gprs351248.centertel.pl] has quit [Ping timeout: 268 seconds] 06:48 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 255 seconds] 06:50 < bitcoin-git> [bitcoin] sdaftuar opened pull request #12902: [qa] Handle potential cookie race when starting node (master...2018-04-improve-dbcrash-restarts) https://github.com/bitcoin/bitcoin/pull/12902 06:51 -!- Deinogalerix21 [~Deinogale@185.169.255.9] has quit [Quit: WeeChat 2.1] 06:53 -!- satwo [~textual@2602:306:378a:6fb0:3815:f5e3:df81:ad5c] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 07:02 -!- satwo [~textual@2602:306:378a:6fb0:3815:f5e3:df81:ad5c] has joined #bitcoin-core-dev 07:02 -!- Hillary82Hartman [~Hillary82@ns334669.ip-5-196-64.eu] has joined #bitcoin-core-dev 07:03 -!- griswaalt [~griswaalt@155.56.40.59] has joined #bitcoin-core-dev 07:04 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 07:05 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 07:09 -!- Dizzle [~dizzle@108.171.182.16] has joined #bitcoin-core-dev 07:10 -!- qu4ku_ [~qu4ku@2a01:110f:f73:1b00:9438:52d4:feb5:1065] has quit [Ping timeout: 256 seconds] 07:10 -!- qu4ku [~qu4ku@2a01:110f:f73:1b00:3c14:67ca:5b5c:a72b] has joined #bitcoin-core-dev 07:13 -!- satwo [~textual@2602:306:378a:6fb0:3815:f5e3:df81:ad5c] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 07:16 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 07:20 -!- Hillary82Hartman [~Hillary82@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 260 seconds] 07:21 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 240 seconds] 07:22 -!- griswaalt [~griswaalt@155.56.40.59] has quit [Ping timeout: 265 seconds] 07:28 -!- geezas [uid253218@gateway/web/irccloud.com/x-giexdhaszaitgheb] has joined #bitcoin-core-dev 07:33 -!- d9b4bef9 [~d9b4bef9@207.38.94.106] has quit [Remote host closed the connection] 07:33 -!- moneyball [~moneyball@65.200.72.90] has joined #bitcoin-core-dev 07:34 -!- d9b4bef9 [~d9b4bef9@207.38.94.106] has joined #bitcoin-core-dev 07:36 < stevenroose> Does bitcoin core have a utxo cache? If so, could anyone point me to the file where it is defined? 07:36 -!- satwo [~textual@2602:306:378a:6fb0:3815:f5e3:df81:ad5c] has joined #bitcoin-core-dev 07:38 < stevenroose> Aha, I found -dbcache, which is the size in MiB for the utxo db cache 07:40 < stevenroose> I thought the cuckoocache was used as a sigcache. 07:40 < stevenroose> Is it also used for the utxo cache? 07:41 < sdaftuar> stevenroose: no, it is not. see src/coins.h and src/coins.cpp for more information about the utxo cache. 07:44 < stevenroose> sdaftuar: thanks! 07:45 < stevenroose> from the init code, I see that the -dbcache is split in 3, of which one is "chain state cache", what is that one for? 07:49 -!- satwo [~textual@2602:306:378a:6fb0:3815:f5e3:df81:ad5c] has quit [Quit: Textual IRC Client: www.textualapp.com] 07:52 -!- Giszmo [~leo@ip-115-236-219-201.nextelmovil.cl] has joined #bitcoin-core-dev 07:59 -!- zarez [~Thunderbi@fs-93-93-44-38.fullsave.info] has joined #bitcoin-core-dev 08:00 -!- nitramiz [~nitramiz@76.76.240.247] has joined #bitcoin-core-dev 08:07 -!- rex4539 [~textual@2a02:587:3514:8600:fb:9274:e68:7c8c] has quit [Ping timeout: 276 seconds] 08:07 -!- rex4539 [~textual@ppp-2-87-183-80.home.otenet.gr] has joined #bitcoin-core-dev 08:09 < bitcoin-git> [bitcoin] sdaftuar opened pull request #12904: [qa] Ensure bitcoind processes are cleaned up when tests end (master...2018-04-always-kill-bitcoind) https://github.com/bitcoin/bitcoin/pull/12904 08:09 -!- nitramiz [~nitramiz@76.76.240.247] has quit [Quit: Lost terminal] 08:20 -!- Murch [~murch@96.74.120.81] has joined #bitcoin-core-dev 08:24 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 08:25 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 08:28 -!- CubicEar_ [~cubiceart@xdsl-188-155-63-9.adslplus.ch] has quit [Remote host closed the connection] 08:29 -!- CubicEarths [~cubiceart@xdsl-188-155-63-9.adslplus.ch] has joined #bitcoin-core-dev 08:30 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 265 seconds] 08:33 -!- CubicEarths [~cubiceart@xdsl-188-155-63-9.adslplus.ch] has quit [Ping timeout: 240 seconds] 08:36 < sipa> stevenroose: for the UTXO set the layers are: (1) disk (with OS cache etc) (2) LevelDB's cache (3) Bitcoin Core's pcoinsTip (a CCoinsViewCache object) 08:36 < setpill> is there any way to actively check for conflicting transactions in the mempool for a given tx? 08:37 < sipa> stevenroose: there is another data set, the block index which is loaded entirely in memory, but is stored in a separate LevelDB database 08:38 < sipa> so the 3 pieces -dbcache is split over is the blockindex leveldb cache, the chainstate leveldb cache (=utxo), and pcoinTip 08:38 < setpill> i suppose trying to rebroadcast would give an error in some cases, but i am not sure how reliable that is, and i would prefer just simply checking without broadcasting 08:39 -!- qu4ku [~qu4ku@2a01:110f:f73:1b00:3c14:67ca:5b5c:a72b] has quit [Ping timeout: 245 seconds] 08:41 -!- zarez [~Thunderbi@fs-93-93-44-38.fullsave.info] has quit [Ping timeout: 264 seconds] 08:44 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 260 seconds] 08:45 -!- qu4ku [~qu4ku@2a01:110f:f73:1b00:3da8:d895:cd79:3fd4] has joined #bitcoin-core-dev 08:57 -!- qu4ku_ [~qu4ku@2a01:110f:f73:1b00:68dd:8c18:235:f9d2] has joined #bitcoin-core-dev 08:57 -!- qu4ku [~qu4ku@2a01:110f:f73:1b00:3da8:d895:cd79:3fd4] has quit [Ping timeout: 256 seconds] 09:04 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 09:05 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 09:06 -!- Dizzle [~dizzle@108.171.182.16] has quit [Quit: Leaving...] 09:09 -!- unholymachine [~quassel@c-69-248-123-139.hsd1.nj.comcast.net] has quit [Remote host closed the connection] 09:09 -!- grafcaps [~haroldbr@104.137.194.255] has joined #bitcoin-core-dev 09:12 -!- Aaronvan_ is now known as AaronvanW 09:12 -!- moneyball [~moneyball@65.200.72.90] has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…] 09:14 -!- zarez [~Thunderbi@fs-93-93-44-38.fullsave.info] has joined #bitcoin-core-dev 09:16 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Ping timeout: 256 seconds] 09:16 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-core-dev 09:20 -!- zarez [~Thunderbi@fs-93-93-44-38.fullsave.info] has quit [Quit: zarez] 09:20 -!- moneyball [~moneyball@65.200.72.90] has joined #bitcoin-core-dev 09:25 -!- qu4ku_ [~qu4ku@2a01:110f:f73:1b00:68dd:8c18:235:f9d2] has quit [Ping timeout: 265 seconds] 09:31 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 09:31 -!- Giszmo [~leo@ip-115-236-219-201.nextelmovil.cl] has quit [Ping timeout: 260 seconds] 09:32 -!- wxss [~user@45.248.77.253] has quit [Quit: leaving] 09:38 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 09:38 -!- geezas [uid253218@gateway/web/irccloud.com/x-giexdhaszaitgheb] has quit [Quit: Connection closed for inactivity] 09:40 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 09:41 -!- twistedline_ [~quassel@unaffiliated/twistedline] has quit [Ping timeout: 255 seconds] 09:42 -!- setpill [~setpill@unaffiliated/setpill] has quit [Quit: o/] 09:47 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has joined #bitcoin-core-dev 09:48 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #bitcoin-core-dev 09:48 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 09:49 -!- twistedline [~quassel@unaffiliated/twistedline] has joined #bitcoin-core-dev 10:01 -!- rex4539 [~textual@ppp-2-87-183-80.home.otenet.gr] has quit [Quit: Textual IRC Client: www.textualapp.com] 10:13 -!- williamayd [~williamay@c-73-53-44-111.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 10:14 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 10:16 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:17 -!- DrOlmer [~DrOlmer@unaffiliated/drolmer] has quit [Ping timeout: 240 seconds] 10:17 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 10:17 -!- DrOlmer [~DrOlmer@unaffiliated/drolmer] has joined #bitcoin-core-dev 10:18 -!- williamayd [~williamay@c-73-53-44-111.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 10:19 -!- lman [5530383d@gateway/web/cgi-irc/kiwiirc.com/ip.85.48.56.61] has quit [Disconnected by services] 10:22 -!- rex4539 [~textual@2a02:587:3514:8600:1d72:e3f0:4830:7050] has joined #bitcoin-core-dev 10:25 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:29 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 10:29 -!- Murch [~murch@96.74.120.81] has quit [Quit: Snoozing.] 10:32 -!- Murch [~murch@96.74.120.81] has joined #bitcoin-core-dev 10:35 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 10:35 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:36 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 10:36 -!- williamayd [~williamay@c-73-53-44-111.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 10:39 -!- williamayd [~williamay@c-73-53-44-111.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 10:40 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has joined #bitcoin-core-dev 10:43 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 10:43 -!- isis is now known as isis_ 10:47 -!- vicenteH [~user@248.red-79-159-36.dynamicip.rima-tde.net] has quit [Ping timeout: 255 seconds] 10:47 -!- jnewbery [~john@static-100-38-11-146.nycmny.fios.verizon.net] has quit [Quit: leaving] 10:49 -!- Murch [~murch@96.74.120.81] has quit [Quit: Snoozing.] 10:50 -!- Murch [~murch@96.74.120.81] has joined #bitcoin-core-dev 10:52 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 260 seconds] 10:57 -!- arubi_ is now known as arubi 11:00 -!- jb551 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #bitcoin-core-dev 11:00 -!- Murch [~murch@96.74.120.81] has quit [Quit: Snoozing.] 11:00 -!- Murch [~murch@96.74.120.81] has joined #bitcoin-core-dev 11:02 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 11:05 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 11:05 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 11:08 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has quit [Quit: probably someone interrupted me] 11:10 -!- dafunkiz_ [~dafunkizd@174.127.131.154] has joined #bitcoin-core-dev 11:11 -!- booyah_ is now known as booyah 11:13 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 11:14 -!- jnewbery [~john@static-100-38-11-150.nycmny.fios.verizon.net] has joined #bitcoin-core-dev 11:15 -!- jb551 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Ping timeout: 260 seconds] 11:16 -!- dafunki__ [~dafunkizd@174.127.143.202] has joined #bitcoin-core-dev 11:19 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 260 seconds] 11:19 -!- dafunkiz_ [~dafunkizd@174.127.131.154] has quit [Ping timeout: 255 seconds] 11:21 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #bitcoin-core-dev 11:24 -!- moneyball [~moneyball@65.200.72.90] has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…] 11:26 -!- moneyball [~moneyball@65.200.72.90] has joined #bitcoin-core-dev 11:28 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 11:28 < bitcoin-git> [bitcoin] sdaftuar opened pull request #12905: [rpcwallet] Clamp walletpassphrase value at 100M seconds (master...2018-04-wallet-encryption-timeout) https://github.com/bitcoin/bitcoin/pull/12905 11:33 -!- AhNo1 [~AhNo1@unaffiliated/ahno1] has joined #bitcoin-core-dev 11:34 -!- AhNo1 [~AhNo1@unaffiliated/ahno1] has quit [Client Quit] 11:35 -!- d9b4bef9 [~d9b4bef9@207.38.94.106] has quit [Remote host closed the connection] 11:38 -!- d9b4bef9 [~d9b4bef9@207.38.94.106] has joined #bitcoin-core-dev 11:39 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 11:42 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 260 seconds] 11:47 -!- commavir_ [vir@2604:180::502b:135a] has quit [Quit: leaving] 11:48 -!- commavir [vir@2604:180::502b:135a] has joined #bitcoin-core-dev 11:49 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 11:49 -!- Murch [~murch@96.74.120.81] has quit [Quit: Snoozing.] 11:50 < sdaftuar> setpill: unfortunately i don't think we have great tools right now. in the next release, we'll have an rpc called "testmempoolaccept" which you could use to determine whether a given transaction would be accepted to your mempool, which might be along the lines of what you'd want? 11:51 < sdaftuar> but it's tricky in general, because dealing with transaction chains is not easy 11:51 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 11:52 < sdaftuar> for instance, if someone sends you a transaction that depends on another unconfirmed transaction, and then a third transaction conflicts with the parent and evicts it from the mempool, it's hard to tell that your transaction is indirectly conflicted as well 11:53 -!- Murch [~murch@96.74.120.81] has joined #bitcoin-core-dev 11:55 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 264 seconds] 11:59 -!- sturles [~sturles@unaffiliated/sturles] has quit [Remote host closed the connection] 12:00 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 12:00 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 12:02 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 12:03 < stevenroose> sipa: the block index I understand 12:04 < stevenroose> "the chainstate leveldb cache (=utxo), and pcoinTip" -> so what exactly is the difference there? 12:04 < stevenroose> they are both used to cache the utxo set, right? 12:04 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 12:07 -!- sturles [~sturles@unaffiliated/sturles] has joined #bitcoin-core-dev 12:10 < jamesob> does POTENTIAL DEADLOCK DETECTED being logged by a node during functional test runs indicate something is definitely out of the ordinary? 12:19 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 12:20 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 264 seconds] 12:21 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 12:21 -!- dafunki__ [~dafunkizd@174.127.143.202] has quit [Quit: probably someone interrupted me] 12:21 < stevenroose> sipa: oh you meant with (=utxo) that it's just the leveldb cache for the store that has the utxo data 12:21 < stevenroose> ok, so the only thing core maintains itself is the CCoinsViewCache, right? 12:23 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has joined #bitcoin-core-dev 12:26 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has quit [Client Quit] 12:32 -!- jnewbery [~john@static-100-38-11-150.nycmny.fios.verizon.net] has quit [Ping timeout: 256 seconds] 12:32 -!- jamesob [~james@static-100-38-11-146.nycmny.fios.verizon.net] has quit [Read error: Connection reset by peer] 12:33 -!- jnewbery [~john@rrcs-67-251-193-154.nyc.biz.rr.com] has joined #bitcoin-core-dev 12:35 -!- jamesob [~james@static-100-38-11-146.nycmny.fios.verizon.net] has joined #bitcoin-core-dev 12:45 -!- cryptojanitor [uid278088@gateway/web/irccloud.com/x-hsdcdvrymuvyzncd] has quit [Quit: Connection closed for inactivity] 12:45 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 12:46 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 12:47 < sipa> stevenroose: yes, but that's thr most important source of speedups 12:47 < sipa> the leveldb cache helps ob systems with very slow i/o 12:48 < stevenroose> sipa: the coinsCache map is from outpoint to utxo entry, right? 12:48 < stevenroose> Doesn't that mean that for a new tx, the txhash is potentially added a lot of times? 12:49 < stevenroose> in btcd, we have a structure where we map txid to utxoentry that has a (potentially sparse) map from index to output 12:49 < stevenroose> but it 12:49 < stevenroose> 's currently not cached, and indeed, that's one of the mayor performance bottlenecks 12:51 < drexl> when an opcode has inputs, do these come from the stack? 12:51 -!- moneyball [~moneyball@65.200.72.90] has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…] 12:52 < sipa> stevenroose: i believe btcd's design was based on bitcoin core's previous 12:52 < sipa> we switched from per-tx to per-txout in 0.15 12:53 < sipa> leveldb deduplicates multiple key-value pairs with keys that share a prefix anyway, so on disk it's not all that impactful 12:53 -!- jamesob [~james@static-100-38-11-146.nycmny.fios.verizon.net] has quit [Quit: leaving] 12:54 < sipa> and it simplifies the in-memory cache and serialization overhead for read/writes significantly 12:54 < stevenroose> simplifies it a lot indeed 12:55 -!- rex4539 [~textual@2a02:587:3514:8600:1d72:e3f0:4830:7050] has quit [Quit: Textual IRC Client: www.textualapp.com] 12:55 < stevenroose> any numbers on extra memory usage /utxo stored? 12:55 < sipa> 500 MB on disk extra 12:56 < stevenroose> is disk more important than memory? 12:56 < sipa> imho, no 12:56 -!- jamesob [~james@static-100-38-11-146.nycmny.fios.verizon.net] has joined #bitcoin-core-dev 12:56 < sipa> it's a small constant factor extra disk 12:56 < stevenroose> I mean for initila sync mostly, a big memory cache can be very significant, no? 12:56 < sipa> but it makes memory usage for the cache faster, more effective, and more efficient 12:56 < stevenroose> hmm 12:57 < sipa> because now we don't need to load unrelated other unspent outputs into memory 12:57 < sipa> when one output is being spent 12:57 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 12:59 < stevenroose> oh, but you don't have to do that anyway, right? 12:59 < stevenroose> the entry map (index -> output) is sparce 12:59 < stevenroose> also on disk, you don't store entire txs, only the unspent outputs 12:59 < sipa> yes 13:00 -!- moneyball [~moneyball@65.200.72.90] has joined #bitcoin-core-dev 13:00 < sipa> but then you need a complex operation to write changes to disk 13:00 < sipa> and i don't see how you can easily perform the freshness optimization on that 13:00 -!- andytoshi [~apoelstra@wpsoftware.net] has joined #bitcoin-core-dev 13:01 -!- andytoshi [~apoelstra@wpsoftware.net] has quit [Changing host] 13:01 -!- andytoshi [~apoelstra@unaffiliated/andytoshi] has joined #bitcoin-core-dev 13:01 -!- cryptojanitor [uid278088@gateway/web/irccloud.com/x-fitwvxuxbfdosaaz] has joined #bitcoin-core-dev 13:01 < sipa> (that's the idea that if you create a utxo in memory, and then later spend it, in memory, it can be deleted from the cache, and nothing ever needs to hit disk, because both the create-txout and spent-txout operations are idempotent) 13:01 -!- rex4539 [~textual@2a02:587:3514:8600:dc32:806b:c481:8108] has joined #bitcoin-core-dev 13:02 < stevenroose> hmm, I only just started looking into this more deeply, but I don't see how storing utxos grouped per tx change that 13:02 < sipa> well it means you can only do that optimization if all utxos of a tx are spent before a flush 13:04 < sipa> i guess you can have a hybrid where you store them per-txout on disk, but with shared txids in memory 13:04 < sipa> i looked into doing that, but the memory usage savings are tiny 13:05 < stevenroose> I don't know what optimization you talk about tbh. let's say you add a tx with two outputs (you always add whole txs right? I don't think single outpoints make much sense), so you git txid -> (o1, o2) 13:05 < sipa> yup 13:06 < stevenroose> then, before a flush, o2 gets spent, so you keep txid -> (o1) and then when you flush, I don't see the overhead over writing txid1 -> o over txid -> (o1) 13:06 < stevenroose> (opposite overhead) 13:06 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-ivzbwbcgbekuebnt] has joined #bitcoin-core-dev 13:06 < sipa> that's actually a pretty significant overhead 13:06 < sipa> you need a dynamically allocated structure for variable-length output array 13:07 < sipa> it's hard to compare what we're talking about because there are so many variations, depending on how you do things in memory vs on disk 13:10 -!- harrymm [~harrymm@104.207.83.39] has quit [Ping timeout: 265 seconds] 13:10 < stevenroose> I realize, trying to see if it's worth turning the whole structure here upside down :) 13:11 < sipa> https://github.com/bitcoin/bitcoin/pull/10195 13:18 < stevenroose> Hmm, not reassuring :) 13:19 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has joined #bitcoin-core-dev 13:20 < sipa> what could be done is change the in-memory representation slightly where you have two maps, one txid->(int,coinbase,height,#unspents) and another (int,vout)->(amount,script) 13:20 < sipa> rather than the single map we currently have (txid,vout)->(amount,script,coinbase,height) 13:21 < sipa> but it becomes a lot more complicated in the presence of more complicated cache flushing strategies 13:22 < sipa> perhaps if average txn over time gain more txouts this becomes better 13:23 -!- harrymm [~harrymm@104.207.83.39] has joined #bitcoin-core-dev 13:23 < stevenroose> well, mostly to avoid changing all the db code etc, I will probably start with a cache on the current system 13:24 < stevenroose> the argument of txs becoming bigger could make sense, though 13:24 < stevenroose> if we want actual unlinkability with CT, coinjoin-like structures will become increasingly common 13:25 < stevenroose> but yeah the simplicity of a txout based structure is also very compelling 13:26 < sipa> in any case, i'm very skeptical that any attempts to share the txids and other tx metadata in memory are worthwhile 13:26 < sipa> and unfortunately the CCoinsViewCache code is pretty complicated as it takes advantage of a bunch of tricks that are specific to utxo data 13:27 < sipa> so it's not trivial to just drop in another cache design 13:27 < sipa> you may want to talk to eklitzke 13:28 < stevenroose> "a bunch of tricks that are specific to utxo data" hmm 13:28 < sipa> well in particular the freshness optimization 13:28 < sipa> that i mentioned above 13:29 < stevenroose> I was going through it a bit, will certainly do some more consideration before i dive into coding 13:29 < stevenroose> yeah, I'll look into that 13:29 < sipa> it seems like a very hard first project if you're not already somewhat familiar with the codebase :) 13:29 < stevenroose> how does it handle crashes? keeping latest flushed height or so and rebuilding newer blocks from disk in case of crash? 13:29 < sipa> ah! 13:31 < sipa> https://github.com/bitcoin/bitcoin/pull/10148 13:31 -!- ThinkOfANick [a5e3cffc@gateway/web/cgi-irc/kiwiirc.com/ip.165.227.207.252] has joined #bitcoin-core-dev 13:32 < stevenroose> thanks! 13:33 < stevenroose> when talking about cached "chain state", I suppose new blocks are always directly written to disk, no? 13:33 < sipa> the chain state is the utxo set 13:33 < sipa> blocks are stored completely independently 13:33 < stevenroose> ok, that clears it up 13:34 -!- mohsen_ [05d34794@gateway/web/freenode/ip.5.211.71.148] has joined #bitcoin-core-dev 13:34 < sipa> basically on disk there is a marker with a hash of a block that means "utxos created or spent after this block MAY be present" and another that means "all utxos created or spent before this block MUST be on disk" 13:34 -!- mohsen_ [05d34794@gateway/web/freenode/ip.5.211.71.148] has quit [Client Quit] 13:35 < sipa> and at startup all blocks before the first and the second hash are replayed and applied to the UTXO set 13:35 < sipa> this approach means we don't need to write the whole cache utxo set in one atomic operation, and also don't need to remember old deleted entries 13:37 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev 13:38 < ThinkOfANick> sipa: Wait, why not remember old entries? 13:38 < sipa> ThinkOfANick: because you want to save memory 13:38 -!- ThinkOfANick [a5e3cffc@gateway/web/cgi-irc/kiwiirc.com/ip.165.227.207.252] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client] 13:38 < stevenroose> sipa: I'm having difficulty to see how those two block locators are not the same 13:39 < setpill> sdaftuar: perhaps ill have to resort to adding all the "from" addresses of the entire chain as watch-only addresses... 13:39 < sipa> stevenroose: you have 1 million modified UTXO entries in memory 13:39 -!- mohsen_ [05d34794@gateway/web/freenode/ip.5.211.71.148] has joined #bitcoin-core-dev 13:39 -!- mohsen_ [05d34794@gateway/web/freenode/ip.5.211.71.148] has quit [Client Quit] 13:39 -!- ThinkOfANick [a5e3cffc@gateway/web/cgi-irc/kiwiirc.com/ip.165.227.207.252] has joined #bitcoin-core-dev 13:39 < sipa> stevenroose: you can't construct a single batch to write them all at once to memory, as that batch would be gigabytes in side 13:39 < sipa> so you write part of it 13:39 < sipa> *size 13:40 < sipa> say you last full flush was at block 400000 13:40 < sipa> the current tip is 450000 13:40 < sipa> that means your cache may include entries from up to block 450000 13:40 < stevenroose> (partial flush, right?) 13:40 < stevenroose> ah full 13:40 < stevenroose> srry didn't see 13:41 < sipa> you're now doing a partial flush, writing just some subset of UTXO cache entries to disk 13:41 < sipa> that may include UTXOs created up to block 450000 (or may miss things that were created between 400000 and 450000) 13:41 < sipa> but it's not guaranteed to contain everything up to 450000 (in fact, because you know it's partial, it can't be) 13:42 < sipa> so the range you write is 400000..450000 13:42 < sipa> and if a crash happens then and there 13:42 < sipa> at startup you'll need to replay everything between 400000 and 450000 13:43 < sipa> because all utxo creation and spending operations are idempotent, it never hurts to replay an operation that was already applied 13:43 < stevenroose> I see, I just don't see how the 450000 is not just the same as the tip.. you also said "utxos created or spent after this block MAY be present" that must have been "before" then? 13:43 < sipa> 450000 is the tip 13:43 < sipa> in this scenario 13:43 < stevenroose> yeah 13:43 < sipa> no 13:44 < sipa> utxos created or spent after 400000 MAY be present 13:44 < sipa> utxos created or spent before 450000 MUSt be present 13:44 < sipa> so the range is 400000..450000 13:44 -!- ThinkOfANick [a5e3cffc@gateway/web/cgi-irc/kiwiirc.com/ip.165.227.207.252] has left #bitcoin-core-dev [] 13:44 < sipa> eh, i guess this is vague 13:44 < stevenroose> > utxos created or spent before 450000 MUSt be present 13:44 < stevenroose> yeah that's where you lost me 13:44 < sipa> let me reformulate 13:45 < sipa> all operations up to block 400000 are guaranteed to be on disk 13:45 < stevenroose> you said "MUST be before" and "MAY be after" so I assume that is the same one 13:45 < sipa> all operations between 400000 and 450000 may be present on disk, but are not guaranteed to be 13:45 < sipa> my "may" and "must" were very confusing before 13:45 < stevenroose> yeah, that's what confused me 13:45 < sipa> but things after 450000 are guaranteed to not be on disk 13:46 < stevenroose> so now let's assume there is already a persistent chain tip indicator, then you only need to keep one, right? 13:46 < sipa> well this is the chain tip indicator 13:46 < sipa> instead of a tip, it's a range 13:46 < stevenroose> that's why I was confused for it to be two. ok ok, yeah I got it. I just assumed you would always need a chaintip anyways 13:46 < sipa> in the ideal scenario the two are the same 13:46 < sipa> after a full flush 13:47 < stevenroose> one last thing I'm missing 13:47 < stevenroose> how to know when to update that consistence height 13:47 < stevenroose> (the first one of the range) 13:47 < sipa> ah, right now it's very simple 13:48 < sipa> when we start a flush operation, we check what the previous lower-height (the 400000) was, and update it to (that lower height, current tip) 13:48 < sipa> after a flush operation completes, it's replaced with (current tip, current tip) 13:49 < stevenroose> oh, but then you still need full flushes? 13:49 < stevenroose> so you can't update in partial writes? 13:49 < sipa> well we only have full flushes now 13:49 < sipa> but they're implemented as a sequence of partial flushes 13:49 < sipa> longer term i want a system where we have a background thread that's constantly flushing 13:50 < sipa> and is always "running behind" on the tip 13:50 < sipa> to give the memory db a chance to cache creates/spends that cancel each other out before writing 13:50 < sipa> but keeping track of which is the lower hash in the range in that system is more complicated 13:51 < sipa> it's basically the lowest height of which you either have an unwritten create or unwritten spend 13:51 < sipa> but it's more tricky in the presence of reorganizations 13:51 < sipa> https://github.com/bitcoin/bitcoin/blob/master/src/txdb.cpp#L102L137 <- current flushing to disk logic 13:52 < stevenroose> oooooooh 13:53 < stevenroose> ok, I thought you were doing a partial flush when the cache was full 13:53 < stevenroose> (like LRI fashion or so) 13:53 < sipa> nope 13:53 < stevenroose> but it's just a way to reduce the size of the transaction 13:53 < stevenroose> ldb transaction 13:53 < sipa> i've experimented with various approaches for MRU eviction from the cache etc 13:53 < stevenroose> oh yeah than you can just do all batches and update the pointer 13:54 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has quit [Quit: probably someone interrupted me] 13:54 < sipa> but they're basically all slower than what we're doing now (on fast hw at least) 13:55 < stevenroose> sipa: yeah you'd have the problem of knowing to what hash it's consistent. you'd need to keep heights in entries and iterate over all entries once and a while to see what the most recent dirty one is 13:55 < sipa> the *least* recent dirty one, yes 13:55 < sipa> thankfully, utxo entries already have a height 13:55 < stevenroose> excuseer :p 13:56 < sipa> unfortunately, that's the creation height and not really the modification height (which may differ in the case of a spend or a reorg) 13:56 < stevenroose> yeah I keep having a hard time picturing reorg handling there 13:57 < stevenroose> because when you don't have a txindex and you delete an entry, it's impossible to get it back :D 13:57 < sipa> oh, we have undo data 13:57 < sipa> the *.rev files 13:57 < stevenroose> do you keep like "revert objects" for the last X blocks 13:57 < stevenroose> ah 13:57 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has joined #bitcoin-core-dev 13:58 < stevenroose> how many are there? (thinking hardfork races here where two chains constantly catch up with each other and fuck old nodes) 13:58 < sipa> there is one per block 13:58 < sipa> and we prune them along with the blocks themselves 13:59 < stevenroose> (technically wouldnt be a hardfork in that case though) 13:59 < stevenroose> wait, why keep for all? or are they only like pointers to the actual data? 14:00 < sipa> because we need to be able to reorg? 14:00 < stevenroose> I haven't seen any of that data in btcd's codebase, let me dig to that tomorrow :) 14:00 -!- jigawatt [~znc@45.76.29.188] has left #bitcoin-core-dev ["Leaving"] 14:00 < stevenroose> yeah I know, but well, reorging over half the chain is kinda unlikely, isn't it? 14:00 < sipa> yes 14:00 < stevenroose> I'd say at least before the last checkpoint makes no sense.. 14:01 < sipa> checkpoints need to go away 14:01 < stevenroose> oh 14:01 < sipa> but yes, sure, it's unlikely that deep reorgs happen 14:01 < stevenroose> what's the fundamental problem with checkpoints? 14:01 < sipa> they confuse people 14:01 < sipa> :) 14:02 < sipa> they're seen as a security measure 14:02 < stevenroose> more as an efficiency tool :p I mean you can skip verification up to that point 14:03 < sipa> we have assumevalid for that now, which is far less invasive 14:03 < stevenroose> (f.e. when syncing a node I always "ask my friends for the latest block they trust" (i.e. check some explorers) and do --addcheckpoint 14:03 < sipa> it doesn't restrict which chain is valid 14:03 < sipa> it just skips validation for any block that is an ancestor of a known valid block 14:03 < sipa> but if the best chain we see is different than the assumevalid one, we'll accept it (after validating) 14:04 < stevenroose> ok yeah that's a better version of a checkpoint 14:04 < sipa> yes, assumevalid is updated from time to time, but we haven't modified checkpoints in years 14:04 < stevenroose> but checkpoints are also usefull against eclipse attacks when you're just getting started 14:04 < sipa> no 14:05 < stevenroose> at least they let you know something is up, no? 14:05 < sipa> they're useful against being spammed with low difficulty headers 14:05 < sipa> but that's independent of eclipse attacks 14:05 < sipa> we need backward headers sync to remove that dependency on checkpoints 14:06 < stevenroose> backward header sync? 14:06 -!- laurentmt [~Thunderbi@ip124.67-202-83.static.steadfastdns.net] has joined #bitcoin-core-dev 14:06 < sipa> first learn the best header, and only then download headers along that path 14:06 < sipa> as opposed to downloading whatever header people give you, hoping that indeed it'll turn out to be one with more work than your current one 14:07 < sipa> (that's how it works now) 14:07 < stevenroose> how can you learn the best header? 14:08 < sipa> using a yet to be devised protocol :) 14:08 < stevenroose> asking all peers? (heighest checkpoint? :p) 14:08 < stevenroose> oh 14:08 -!- laurentmt [~Thunderbi@ip124.67-202-83.static.steadfastdns.net] has quit [Client Quit] 14:09 < sipa> there are some ideas about random sampling, where someone can send you a merkle sum tree over all their headers, and then you randomly query it a number of times to see if they indeed have the distribution of pow they claim 14:09 < stevenroose> I recently thought about a backwards sync mechanism for initila utxo building. but I guess it's kinda not worth the effort when there is a good utxo cache 14:10 < sipa> and once you've done enough queries, you know they actually have a chain with a certain amount of work 14:10 < sipa> and if that amount of work is good enough, you can start downloading the actual headers 14:10 < setpill> sipa: wouldn't just believing the claimed amount of accumulated work + ban on lie work? 14:11 < stevenroose> are checkpoints really that bad? 14:11 < sipa> stevenroose: people seem to misunderstand that if checkpoints ever have an effect, bitcoin is broken 14:11 < sipa> i'm much more comfortable to have much weaker assumptions about correctness of the code 14:12 < sipa> (which includes the checkpoints) 14:12 < sipa> setpill: how is that better than what we have now? 14:13 < sipa> stevenroose: i don't think they're terrible, but we also don't really need them anymore, except for this tiny DoS concern 14:13 < setpill> sipa: last blocks are likely to have more pow behind them so are more expensive to maliciously craft 14:13 < stevenroose> "if checkpoints ever have an effect, bitcoin is broken" you mean that when code breaks validity of an old block that no one will validate because checkpoints? 14:14 < sipa> stevenroose: i mean that if checkpoints ever prevent the network from reorging to an attacker chain, it's clear that the concept of PoW itself is brokenb 14:15 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 14:15 < stevenroose> and what if they prevent *a new node* from syncing a wrong chain? that's what their main use is imho 14:16 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has quit [Quit: probably someone interrupted me] 14:16 < sipa> stevenroose: that's not what they do 14:16 < sipa> stevenroose: they just prevent OOM 14:16 < stevenroose> I mean even as a spam vector, a decent miner right now can prob create a quite significantly long chain that is use in size (1MB blocks) and has legit work 14:16 < stevenroose> s/use/huge/ 14:16 < sipa> yes, absolutely - that's exactly the one thing they still do 14:17 < stevenroose> OOM? 14:17 < sipa> out of memory 14:17 < sipa> also, not actually blocks, just headers 14:17 < sipa> we don't download block data until a chain of validated headers is actually the best chain 14:18 < stevenroose> yeah true, so that would only work if eclipsed 14:18 < sipa> oh, and there is a known min amount of work 14:18 < sipa> independently of checkpoints 14:18 < stevenroose> "min amount of work at height x"? 14:18 < sipa> so we never accept a headers chain until it passes that point 14:19 < stevenroose> oh llike that 14:19 < stevenroose> cumulative 14:19 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has joined #bitcoin-core-dev 14:19 < stevenroose> thats neat 14:19 < setpill> sipa: interesting, i hadnt heard of that; is that documented somewhere? 14:21 < sipa> -minimumchainwork cmdline option 14:22 < stevenroose> well, thanks for the insights :) 14:23 < sipa> yw! 14:26 < setpill> sipa: ahh, so its another "checkpoint-esque" thing, as in a hardcoded value that gets updated periodically? 14:27 < setpill> for a second i was under the impression pow inflation somehow had a lower bound ^^' 14:27 < sipa> setpill: there is a minimum difficulty, but it's trivial 14:28 < setpill> yeah and wont help much against a malicious chain 14:28 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 264 seconds] 14:29 < sipa> a single modern CPU thread can create a minimum-difficulty block in a few minute 14:29 < sipa> modern HW miners can make 1000s per second 14:30 < setpill> yeah, so i thought there was a higher-than-that, actually useful lower bound on difficulty based on something i was unaware of 14:31 < sipa> there is also the max-divide-by-4 rule for difficulty changes 14:33 < stevenroose> sipa: is that a consensus rule?? 14:33 < sipa> yes 14:33 < stevenroose> was not aware of that 14:33 < sipa> always has been 14:33 < stevenroose> is there a max-multiply-by-x one? 14:33 < sipa> yes, by 4 14:34 < stevenroose> aha 14:34 < sipa> neither rule has ever been hit 14:34 < sipa> on mainnet at least 14:35 < stevenroose> I hate the zero-diff-after-20-mins testnet rule 14:35 < sipa> haha 14:35 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 14:35 < stevenroose> I used to try and testnet mine with an old butterfly labs jalapeno but somehow was never hitting one 14:35 < sipa> you need to set your timestamp in the future :) 14:35 < stevenroose> btcd didn't notify gbt long polls on the 20 minute hit 14:35 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 14:35 < stevenroose> also 14:36 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has quit [Ping timeout: 240 seconds] 14:43 -!- timothy [~tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!] 14:44 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 14:47 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 256 seconds] 14:47 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 14:54 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.0] 14:56 -!- Giszmo [~leo@ip-29-226-107-190.nextelmovil.cl] has joined #bitcoin-core-dev 15:10 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 15:12 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has quit [Quit: probably someone interrupted me] 15:18 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has joined #bitcoin-core-dev 15:24 -!- vicenteH [~user@35.233.15.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 15:26 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-ivzbwbcgbekuebnt] has quit [Quit: Connection closed for inactivity] 15:34 -!- d9b4bef9 [~d9b4bef9@207.38.94.106] has quit [Remote host closed the connection] 15:34 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 15:35 -!- d9b4bef9 [~d9b4bef9@207.38.94.106] has joined #bitcoin-core-dev 15:36 -!- d9b4bef9 [~d9b4bef9@207.38.94.106] has quit [Remote host closed the connection] 15:37 -!- d9b4bef9 [~d9b4bef9@207.38.94.106] has joined #bitcoin-core-dev 15:39 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Read error: Connection reset by peer] 15:45 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has quit [Quit: probably someone interrupted me] 15:47 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 265 seconds] 15:51 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has joined #bitcoin-core-dev 15:51 -!- cryptapus [~cryptapus@jupiter.osmus.org] has joined #bitcoin-core-dev 15:51 -!- cryptapus [~cryptapus@jupiter.osmus.org] has quit [Changing host] 15:51 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 15:53 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-mggovlkmcvxztwnq] has joined #bitcoin-core-dev 15:58 -!- rex4539 [~textual@2a02:587:3514:8600:dc32:806b:c481:8108] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 15:58 -!- CubicEarths [~cubiceart@xdsl-188-155-63-9.adslplus.ch] has joined #bitcoin-core-dev 16:03 -!- CubicEarths [~cubiceart@xdsl-188-155-63-9.adslplus.ch] has quit [Remote host closed the connection] 16:03 -!- CubicEarths [~cubiceart@xdsl-188-155-63-9.adslplus.ch] has joined #bitcoin-core-dev 16:05 < jtimon> sipa: re protocol to know the best chain: couldn't compact pow proofs be better for that than random sampling? 16:06 < jtimon> hi stevenroose 16:06 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has quit [Quit: probably someone interrupted me] 16:08 -!- CubicEarths [~cubiceart@xdsl-188-155-63-9.adslplus.ch] has quit [Ping timeout: 260 seconds] 16:08 < sipa> jtimon: compact pow proofs need consensus rules 16:08 < sipa> bitcoin doesn't have those 16:09 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has joined #bitcoin-core-dev 16:09 < jtimon> sure, I mean assuming a compact proofs sf 16:14 -!- setpill [~setpill@unaffiliated/setpill] has quit [Quit: o/] 16:16 < intcat> is there any (u)txo commitment design (close to becoming) a BIP? 16:16 < intcat> ive read some ml interaction between peter todd and bram cohen but it's a few years old and im not sure how much has happened on that since 16:33 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 265 seconds] 16:35 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 16:37 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 16:40 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has quit [Quit: probably someone interrupted me] 16:41 -!- harrymm [~harrymm@104.207.83.39] has quit [Read error: Connection reset by peer] 16:44 -!- arbitrary_guy [~arbitrary@c-67-183-30-122.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 16:46 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has joined #bitcoin-core-dev 16:48 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 16:49 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 16:51 -!- harrymm [~harrymm@104.207.83.36] has joined #bitcoin-core-dev 16:54 -!- Sinclair6 [sinclair6@gateway/vpn/privateinternetaccess/sinclair6] has quit [Ping timeout: 265 seconds] 17:00 -!- weez17 [~isaac@unaffiliated/weez17] has quit [Remote host closed the connection] 17:00 -!- weez17 [~isaac@unaffiliated/weez17] has joined #bitcoin-core-dev 17:01 -!- Sinclair6 [sinclair6@gateway/vpn/privateinternetaccess/sinclair6] has joined #bitcoin-core-dev 17:08 -!- arbitrary_guy [~arbitrary@c-67-183-30-122.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 17:17 -!- farsider350 [farsider35@161.43.207.14] has joined #bitcoin-core-dev 17:22 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 17:38 -!- moneyball [~moneyball@65.200.72.90] has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…] 17:43 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 240 seconds] 17:45 < jtimon> aj: thanks again for your help with https://github.com/bitcoin/bitcoin/pull/10757 and sorry I had kind of abandoned for a whiel 17:45 < jtimon> while 17:45 -!- Danilo_ [~quassel@201.6.135.38] has quit [Remote host closed the connection] 17:46 -!- farsider350 [farsider35@161.43.207.14] has quit [] 17:52 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 268 seconds] 17:52 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Ping timeout: 268 seconds] 17:52 -!- moneyball [~moneyball@253.sub-174-214-5.myvzw.com] has joined #bitcoin-core-dev 18:00 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has quit [Quit: probably someone interrupted me] 18:00 -!- Murch [~murch@96.74.120.81] has quit [Quit: Snoozing.] 18:01 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 18:02 -!- isis_ is now known as isis 18:02 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev 18:06 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-mggovlkmcvxztwnq] has quit [Quit: Connection closed for inactivity] 18:06 -!- moneyball [~moneyball@253.sub-174-214-5.myvzw.com] has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…] 18:10 -!- jcorgan [~jcorgan@unaffiliated/jcorgan] has quit [Quit: leaving] 18:17 -!- DrOlmer [~DrOlmer@unaffiliated/drolmer] has quit [Ping timeout: 264 seconds] 18:18 -!- DrOlmer [~DrOlmer@unaffiliated/drolmer] has joined #bitcoin-core-dev 18:20 -!- williamayd [~williamay@c-73-53-44-111.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 18:22 -!- williamayd [~williamay@c-73-53-44-111.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 18:44 -!- mrannanay [uid222022@gateway/web/irccloud.com/x-ckctdhphfrfigjrw] has quit [Quit: Connection closed for inactivity] 18:47 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 18:48 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 18:53 -!- williamayd [~williamay@c-73-53-44-111.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 19:03 -!- williamayd [~williamay@c-73-53-44-111.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 19:03 -!- williamayd [~williamay@c-73-53-44-111.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 19:06 -!- williamayd [~williamay@c-73-53-44-111.hsd1.wa.comcast.net] has quit [Client Quit] 19:06 -!- jcorgan [~jcorgan@unaffiliated/jcorgan] has joined #bitcoin-core-dev 19:08 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Quit: drexl] 19:11 -!- zhuzeng [68850947@gateway/web/freenode/ip.104.133.9.71] has joined #bitcoin-core-dev 19:12 -!- zhuzeng [68850947@gateway/web/freenode/ip.104.133.9.71] has left #bitcoin-core-dev [] 19:13 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has joined #bitcoin-core-dev 19:22 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has quit [Remote host closed the connection] 19:30 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 19:31 -!- arbitrary_guy [~arbitrary@c-67-183-30-122.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 19:31 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has quit [Quit: probably someone interrupted me] 19:33 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has joined #bitcoin-core-dev 19:45 -!- cryptojanitor [uid278088@gateway/web/irccloud.com/x-fitwvxuxbfdosaaz] has quit [Quit: Connection closed for inactivity] 19:48 -!- AriseChikun [Arise@gateway/vpn/privateinternetaccess/arisechikun] has quit [Remote host closed the connection] 19:48 -!- AriseChikun [Arise@gateway/vpn/privateinternetaccess/arisechikun] has joined #bitcoin-core-dev 19:51 -!- jojeyh [~delphi@2602:306:b8b6:b970:183d:63c3:2f:6e5c] has joined #bitcoin-core-dev 19:53 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has quit [Quit: probably someone interrupted me] 19:55 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has joined #bitcoin-core-dev 19:56 -!- moneyball [~moneyball@c-73-223-73-149.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 19:57 -!- murrayn [~dafuq@unaffiliated/murrayn] has quit [Read error: Connection reset by peer] 19:57 -!- murrayn [~dafuq@S01061cabc0b054b3.ok.shawcable.net] has joined #bitcoin-core-dev 19:57 -!- murrayn [~dafuq@S01061cabc0b054b3.ok.shawcable.net] has quit [Changing host] 19:57 -!- murrayn [~dafuq@unaffiliated/murrayn] has joined #bitcoin-core-dev 20:01 -!- karimofthecrop [~karim@69.12.80.147.adsl.inet-telecom.org] has joined #bitcoin-core-dev 20:01 -!- Giszmo [~leo@ip-29-226-107-190.nextelmovil.cl] has quit [Ping timeout: 265 seconds] 20:02 -!- AriseChikun [Arise@gateway/vpn/privateinternetaccess/arisechikun] has quit [Quit: Konversation terminated!] 20:06 -!- arbitrary_guy [~arbitrary@c-67-183-30-122.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 20:15 -!- Giszmo [~leo@ip-29-226-107-190.nextelmovil.cl] has joined #bitcoin-core-dev 20:26 -!- karimofthecrop [~karim@69.12.80.147.adsl.inet-telecom.org] has quit [Ping timeout: 264 seconds] 20:30 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 260 seconds] 20:35 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 20:36 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 20:47 -!- rex4539 [~textual@2a02:587:3514:8600:68ce:3cd8:2b59:78e1] has joined #bitcoin-core-dev 21:02 -!- d9b4bef9 [~d9b4bef9@207.38.94.106] has quit [Remote host closed the connection] 21:03 -!- d9b4bef9 [~d9b4bef9@207.38.94.106] has joined #bitcoin-core-dev 21:09 -!- dafunkiz_ [~dafunkizd@157.130.186.54] has quit [Quit: probably someone interrupted me] 22:11 -!- cryptojanitor [uid278088@gateway/web/irccloud.com/x-gaoqrvvrbfvukuum] has joined #bitcoin-core-dev 22:11 -!- moneyball [~moneyball@c-73-223-73-149.hsd1.ca.comcast.net] has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…] 22:41 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 22:47 -!- Giszmo [~leo@ip-29-226-107-190.nextelmovil.cl] has quit [Quit: Leaving.] 22:48 -!- arbitrary_guy [~arbitrary@c-67-183-30-122.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 22:56 -!- rods1 [~r251d@2600:1700:e350:37f0:bd76:a85b:4402:2605] has quit [Read error: Connection reset by peer] 22:57 -!- rods1 [~r251d@2600:1700:e350:37f0:ac24:4c91:5647:1fbe] has joined #bitcoin-core-dev 22:59 -!- arbitrary_guy [~arbitrary@c-67-183-30-122.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 23:04 -!- Krellan [~Krellan@2601:640:4000:9258:6d80:85a8:b4cd:5123] has joined #bitcoin-core-dev 23:10 -!- merehap_ [~merehap@204.152.214.26] has quit [Ping timeout: 265 seconds] 23:17 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 23:18 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 23:18 -!- rods1 is now known as r251d 23:21 -!- CubicEarths [~cubiceart@xdsl-188-155-63-9.adslplus.ch] has joined #bitcoin-core-dev 23:30 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 23:45 -!- jojeyh [~delphi@2602:306:b8b6:b970:183d:63c3:2f:6e5c] has quit [Ping timeout: 260 seconds]