1 2016-02-10 01:43:29 <Chris_Stewart_5> How do you tell the difference between numbers in Bitcoin script vs things like hashes
 2 2016-02-10 01:43:47 <Chris_Stewart_5> is there a cap on how big numbers can be, i.e. 64 bits?
 3 2016-02-10 01:44:38 <gmaxwell> data on the stack is just data. it's type is deteremined by the operations that act on it.
 4 2016-02-10 01:44:49 <gmaxwell> there is a maximum size for a push of 520 bytes.
 5 2016-02-10 01:45:04 <gmaxwell> the opcodes that act on numbers won't work on numbers beyond 4 bytes.
 6 2016-02-10 01:48:09 <Chris_Stewart_5> So trying to type 'data' on the stack is unwise then?
 7 2016-02-10 01:48:25 <Chris_Stewart_5> I.e. typing something as an Integer vs a script constant
 8 2016-02-10 01:49:11 <gmaxwell> It's not that it's "unwise" but .. just unrelated to how the system actually works. :)
 9 2016-02-10 01:52:42 <Chris_Stewart_5> gmaxwell: Gotcha. It is sort of confusing for test cases like this in core's script test suite ["0x09 0x00000000 0x00000000 0x10", "", "P2SH,STRICTENC", "equals zero when cast to Int64"]
10 2016-02-10 01:54:32 <Chris_Stewart_5> the best way to parse something like that is grouping all of those bytes into a single stream or breaking them out into four individual items
11 2016-02-10 02:10:58 <Chris_Stewart_5> also, is there a dedicated config files style for bitcoin/sidechains?
12 2016-02-10 04:39:00 <cluelessperson> In seriousness,   If you had a business interested in buying ~$1 Million in BTC.  How would you go about it?
13 2016-02-10 04:43:54 <Luke-Jr> cluelessperson: off-topic, take it to #bitcoin
14 2016-02-10 04:44:47 <cluelessperson> Luke-Jr, sorry, I thought I was in OTC :)
15 2016-02-10 04:45:05 <gruez> just wondering, when a new bitcoin version is released, why doesn't a dev announce it on bitcointalk?
16 2016-02-10 04:45:30 <gruez> the announcements there are usually delayed by around 12 hours
17 2016-02-10 04:54:58 <Luke-Jr> gruez: most(?) of us left bitcointalk years ago
18 2016-02-10 04:55:19 <Luke-Jr> due to lack of moderation; too much noise
19 2016-02-10 04:55:39 <gruez> :\
20 2016-02-10 04:58:07 <bsm1175321> bitcointalk is a cespool.
21 2016-02-10 04:59:08 <gmaxwell> gruez: I can pin things in the main forum, when I've posted announcements hostfat has created his own and pinned it rather than mine.
22 2016-02-10 05:10:32 <gruez> <@gmaxwell> gruez: I can pin things in the main forum, when I've posted announcements hostfat has created his own and pinned it rather than mine.
23 2016-02-10 05:10:48 <gruez> you mean you can't pin things in the main forum?
24 2016-02-10 05:30:36 <rusty> kanzure, btcdrak: thoughts on https://lists.linuxfoundation.org/mailman/admindb/bitcoin-dev?sender=voisine%40gmail.com ?
25 2016-02-10 05:37:19 <rusty> kanzure, btcdrak: when we're rejecting for content (eg. misunderstandings), I might start wording it as a reply on bitcoin-dev-moderation, so others can read it too.
26 2016-02-10 06:01:42 <kanzure> rusty: "obviously not reach that limit" haha... miners can't check the actula bandwidth of the network anyway.
27 2016-02-10 06:01:49 <kanzure> rusty: i think we just need to start rejecting obviously wrong broken stuff :(
28 2016-02-10 06:02:04 <rusty> kanzure: yes, but we also need to correct it publicly.
29 2016-02-10 06:02:29 <rusty> kanzure: also, by that logic miners wouldn't be mining 1MB blocks today.
30 2016-02-10 06:24:43 <rusty> kanzure: done. https://lists.ozlabs.org/pipermail/bitcoin-dev-moderation/2016-February/000073.html
31 2016-02-10 08:32:37 <dansmith_btc> Just a meta suggestion to the webmaster of bitcoinstats.com where the logs of this chan are stored: Please index your website with Google. I tried to search the archive via google with a few keywords that Im sure were present in a convo and came up empty. So, deffinitely the logs are not getting indexed properly.
32 2016-02-10 09:17:04 <dansmith_btc> Running v0.12-rc4, seems like it doesn't respond to SIGTERM, whenever I do Ctrl+c or kill PID, it keeps on syncing acc.to debug.log, FWIW Im running with args -datadir=<path> -prune=550 -checkblocks=1 -keypool=0
33 2016-02-10 09:20:27 <phantomcircuit> dansmith_btc, sigterm sets a shutdown flag but wont break into things like ActivateBestChain
34 2016-02-10 09:20:37 <phantomcircuit> it will exit but not immediately
35 2016-02-10 09:22:58 <dansmith_btc> that explains it, thanks
36 2016-02-10 09:38:08 <dansmith_btc> When gettxoutsetinfo makes a utxo hash, does it take into account that utxo is fully loaded in RAM or does it always hash from the disk?
37 2016-02-10 09:45:43 <phantomcircuit> dansmith_btc, does it matter?
38 2016-02-10 09:48:26 <dansmith_btc> speed-wise it matters whether to hash from disk or from RAM.
39 2016-02-10 09:50:44 <dansmith_btc> ah ok, maybe the OS would already know the mapping and take data from RAM
40 2016-02-10 10:53:37 <sturles> Where would be the most proper place to suggest increasing the default value of -blockmaxsize from 750000 to 1000000 bytes?  List, here or just a pull request?
41 2016-02-10 10:58:23 <Luke-Jr> sturles: nowhere.
42 2016-02-10 10:58:53 <sturles> Hmm.  Increasing -blockminsize then?
43 2016-02-10 10:59:02 <Luke-Jr> sturles: nowhere.
44 2016-02-10 10:59:41 <Luke-Jr> convince miners to set them if you want (but anything other than down is bad advice)
45 2016-02-10 11:00:16 <sturles> The default for -blockminsize is 0.  Can it be negative?
46 2016-02-10 13:22:31 <waxwing> so if blockminsize is -1MB, remove the last block? :)
47 2016-02-10 13:23:32 <waxwing> we could get the much requested feature of transaction reversibility. the govt. would be pleased :)
48 2016-02-10 13:26:51 <phantomcircuit> sturles, the default should actually be more like 250kB
49 2016-02-10 13:27:04 <phantomcircuit> that it's 750kB is a quirk of history
50 2016-02-10 13:28:17 <buZz> waxwing: bitundo would not like it if you made it a native functionality
51 2016-02-10 16:22:15 <jeremias_> https://notehub.org/8k84i any comments on this
52 2016-02-10 16:22:30 <jeremias_> comments also welcome on reddit: https://www.reddit.com/r/Bitcoin/comments/452h4j/idea_how_to_save_blockchain_space_for_micro/
53 2016-02-10 20:28:02 <fakesatoshi> we can release a new release every time classic releases an old release. This way they'll be one version behind forever
54 2016-02-10 20:28:21 <fakesatoshi> we can release 0.12 now that they released 0.11.2
55 2016-02-10 20:36:37 <bitcoin-dev474> https://www.reddit.com/r/btc/comments/454cwd/ipv6_bug_in_bu_where_to_report_bu_core/