1 2017-08-09 12:05:09 <Chicago> dakk, Have you looked at any of the blocks on Testnet or on the blocks w/ SW on Litecoin's Main network?  This links to one, https://twitter.com/SatoshiLite/status/862345830082138113 and this links to one from Bitcoin Test network, https://bitcointalk.org/index.php?topic=1758923.0
 2 2017-08-09 13:20:03 <dermoth> Hi... When I try to decode some of the largest transactions that made it into the chain using bitcoin-cli I get this error: _: line 12: bitcoin-cli: Argument list too long
 3 2017-08-09 13:26:53 <dermoth> this is os-level limitation I think, it there any other way to pass the tx, ex stdin?
 4 2017-08-09 13:50:52 <dakk> Chicago, thank you it's what I was looking for; I didn't known this explorer, the raw-hex feature is missing in almost all explorers
 5 2017-08-09 14:06:00 <Chicago> dakk, you're welcome.  If you happen to want to parse the raw blk data manually, find this page http://james.lab6.com/2012/01/12/bitcoin-285-bytes-that-changed-the-world/ on archive.org.  It goes a long way to making you read hex like Link, in The Matrix.
 6 2017-08-09 14:08:30 <dermoth> I think it'd be nice for bitcoin-cli to accept data from stdin
 7 2017-08-09 14:08:30 <dermoth> I worked around using rpc directly...
 8 2017-08-09 14:09:31 <dermoth> oh it does? :)
 9 2017-08-09 14:15:17 <dakk> Chicago, this how-to is awesome, thank you again
10 2017-08-09 14:16:07 <Chicago> dakk, you're welcome - have fun.  I recommend using a piece of paper with that Genesis block printed out so that you can take a ruler and underline the various sections -- and then label them for quick reference.
11 2017-08-09 14:16:50 <dakk> nice trick
12 2017-08-09 14:34:39 <jouke> Chicago, dakk: http://srv2.yogh.io/#block:last
13 2017-08-09 14:42:40 <Chicago> jouke, well that makes it easy
14 2017-08-09 14:42:49 <Chicago> so much for paper, pen and a ruler
15 2017-08-09 14:53:57 <Chris_Stewart_5> dakk: You are working on the OCaml implemenation right?
16 2017-08-09 14:55:05 <dakk> Chris_Stewart_5, yep this is the library https://github.com/dakk/bitcoinml (and this is a full-node implementation wip: https://github.com/dakk/letchain/; just a toy atm)
17 2017-08-09 14:56:24 <Chris_Stewart_5> cool, I'm a OCaml fan glad to see it's coming along.
18 2017-08-09 14:58:22 <dakk> Chris_Stewart_5, great, one potential user for my lib :) if you are an ocaml dev, I also wrote a secp256k1 wrapper: https://github.com/dakk/secp256k1-ml
19 2017-08-09 16:50:14 <Emcy_> What was the actual reasoning behind the 0.25bytes weight for segwits txns [giving a theoretical max hard cap of 4mb blocks]?
20 2017-08-09 16:50:46 <Emcy_> some people say its arbitrary, or has a reasoning other than technicals or something
21 2017-08-09 19:02:12 <ginseng> anyone with experience using berkeley databases know how to explore the data in a wallet.dat? i have been using the bsddb python module to explore it as a btree, but i just find a single key "main" with value '\x00\x00\x00\x02'
22 2017-08-09 19:04:32 <arubi> ginseng, I had success with the db-util package
23 2017-08-09 19:13:30 <arubi> ginseng, fwiw my past try at reverse engineering it a bit, it might save you some time :)  https://gist.github.com/fivepiece/74b6f8bfa8816ee7e283d25a36947629
24 2017-08-09 19:14:31 <arubi> worth to mention that this is a regtest wallet
25 2017-08-09 19:23:43 <ginseng> arubi: thanks for posting that. the comments you added are very helpful. i'm trying to replicate that with db_dump using -p to print out printable characters, it looks like you did more than this though to clean up the output
26 2017-08-09 19:35:52 <arubi> np, it's helpful to have walletdb.cpp open when navigating the file.  if you manage to figure out dumps with script stuff, transactions, watchonly..  I'd love to follow up
27 2017-08-09 19:49:05 <arubi> I think that was it.  if you read the logs ginseng, be advised
28 2017-08-09 19:49:05 <arubi> oh crap, I forgot that this dump was from the patch where you can set your own derivation path
29 2017-08-09 19:50:06 <arubi> I think that was it :\  so long ago
30 2017-08-09 20:54:04 <ptolemaus> when I make some btc escrow transactions and take shares myself
31 2017-08-09 20:54:25 <ptolemaus> should I create a new address for each share?
32 2017-08-09 20:55:12 <ptolemaus> coz if I were to collect and transfer all these cockroach shares then I would pay like 50 ct for each coz of transaction fees
33 2017-08-09 20:56:22 <ptolemaus> if I just put it on 1 address I could save a lot of dinero then
34 2017-08-09 21:04:34 <dermoth> ptolemaus, no
35 2017-08-09 21:05:12 <ptolemaus> then put it on multiple or really just one?
36 2017-08-09 21:05:20 <dermoth> even if you have a single address, each output will end up a tx input
37 2017-08-09 21:05:34 <dermoth> the transaction has to identify each previous transaction with unspent fund
38 2017-08-09 21:05:52 <ptolemaus> oh right
39 2017-08-09 21:06:09 <ptolemaus> inputs are utfo anyway
40 2017-08-09 21:06:22 <dermoth> it doesn'T matter it it's the same address or different, the resulting TX will be the same size
41 2017-08-09 21:06:22 <dermoth> what you may want is to use the key type that comes with the smallest txin size
42 2017-08-09 21:07:23 <dermoth> (which I'd have to check which is...)
43 2017-08-09 21:07:26 <ptolemaus> what might one be?
44 2017-08-09 21:07:45 <ptolemaus> just one so I can search it and check what exists
45 2017-08-09 21:09:24 <dermoth> I believe P2SH is what you want
46 2017-08-09 21:10:28 <dermoth> when Segwit is activated, P2SH-P2WPKH will be even better (and clients doesn't have to support Segwit to sent to those addresses)
47 2017-08-09 21:10:43 <ptolemaus> P2SH is used on inputs?
48 2017-08-09 21:13:28 <dermoth> https://en.bitcoin.it/wiki/Transaction#Input
49 2017-08-09 21:13:28 <dermoth> p2sh means you send to a script hash, then txin provides the script and its signature
50 2017-08-09 21:18:33 <dermoth> oh... no bot spamming for every url here :)
51 2017-08-09 21:33:13 <ptolemaus> dermoth, thank you