1 2018-03-08 07:42:08 <FraJah> moinings
2 2018-03-08 10:27:59 <TyrfingMjolnir> Which function in bitcoin core loads the blockchain?
3 2018-03-08 10:31:43 <esotericnonsense> TyrfingMjolnir: main()
4 2018-03-08 10:32:01 <esotericnonsense> that's, err, a pretty general question?
5 2018-03-08 13:13:46 <setpill> Hey all, I'm trying to set up automated gitian builds using docker, does anyone have experience with gdm85's setup?
6 2018-03-08 13:15:52 <setpill> Specifically, I am running into problems with verifying the debian keyring - I can't seem to match it to anything from the official package
7 2018-03-08 13:35:22 <esotericnonsense> jredondo: there is no way of knowing that
8 2018-03-08 13:37:30 <jredondo> esotericnonsense: thank you man.
9 2018-03-08 13:38:32 <esotericnonsense> it would be challenging if not impossible to devise a scheme that would make those timestamps secure anyway
10 2018-03-08 13:38:46 <esotericnonsense> consider: if the timestamp isn't signed by the originator of the tx, anyone can just mutate it
11 2018-03-08 13:38:58 <jredondo> Yes.
12 2018-03-08 13:39:00 <esotericnonsense> if the timestamp is signed, either you have two signatures for the tx or you bloat the size of a tx
13 2018-03-08 13:39:19 <jredondo> Yes. Makes sense.
14 2018-03-08 13:39:31 <esotericnonsense> and even if the timestamp is signed - what stops the sender from emitting a tx with a timestamp months in the past for example
15 2018-03-08 17:03:24 <setpill> devrando1: I'm in the process of setting up automated gitian builds, going through gdm85's scripts and dockerfiles and updating where needed (stretch instead of wheezy, etc)
16 2018-03-08 17:04:35 <setpill> Noticed that it checkouts a gitian-builder commit from December 2014, so figured I should update that as well - but the latest release is from 2015. Is master considered stable?
17 2018-03-08 17:06:50 <setpill> Ah, just noticed there's a #gitian channel, will move convo there.
18 2018-03-08 17:26:25 <TyrfingMjolnir> esotericnonsense: main() is not a function loading the block chain into memory
19 2018-03-08 19:41:26 <esotericnonsense> TyrfingMjolnir: are you after ReadBlockFromDisk or something?
20 2018-03-08 19:42:17 <esotericnonsense> src/validation.cpp, two functions
21 2018-03-08 19:45:54 <kallewoof> esotericnonsense: you *could* check if the timestamp of the block of all inputs are < the supplied timestamp. still makes it possible but puts a cap on it at least.
22 2018-03-08 19:46:53 <esotericnonsense> kallewoof: with a 2 hour window or something.
23 2018-03-08 19:47:21 <esotericnonsense> tip could be <now+2h> and then me relaying a tx should be able to work with <now>.
24 2018-03-08 19:48:54 <TyrfingMjolnir> esotericnonsense: I would like to read the block chain into memory
25 2018-03-08 19:49:35 <TyrfingMjolnir> For the purpose of querying
26 2018-03-08 19:50:53 <esotericnonsense> TyrfingMjolnir: sure, start from readblockfromdisk then. I thought you basically just meant 'what function does bitcoin' earlier. :P
27 2018-03-08 19:52:31 <TyrfingMjolnir> Thanks