1 2017-08-22 10:12:48 <nazarewk> what is the way to go to retrieve all txids from wallet?
 2 2017-08-22 10:12:55 <nazarewk> (so i can separately gettransaction on them)
 3 2017-08-22 11:43:29 <ossifrage> nazarewk, more then what you get from listtransactions?
 4 2017-08-22 11:45:01 <ossifrage> I guess listtransactions doesn't include old transactions, only the UTXO components
 5 2017-08-22 11:57:35 <wumpus> listtransactions (at least in bitcoin core) gives you all transactions, new and historical
 6 2017-08-22 11:57:45 <wumpus> if you just want the utxo components, use listunspent
 7 2017-08-22 12:01:23 <nazarewk> well... listtransactions is extremely slow on large volume
 8 2017-08-22 12:11:37 <ossifrage> listtransactions does not seem to give you historical txns on 0.14.2 just 'active' txns
 9 2017-08-22 12:13:44 <ossifrage> I moved all my coins to a new address and all my old mining transactions are not shown on listtransactions
10 2017-08-22 13:01:56 <wumpus> possibly there's a bug then, I don't know
11 2017-08-22 13:02:42 <wumpus> depends on what steps exactly you followed, did you import any keys into the wallet?
12 2017-08-22 14:24:24 <ossifrage> What was the reasoning behind limiting the difficulty increase to 4x?
13 2017-08-22 14:27:18 <cdecker> ossifrage, foot-gunning?
14 2017-08-22 14:28:59 <ossifrage> cdecker, yes I would rather not shot myself in the foot. I would imagine people thinking, "a 4x increase that will never happen..."
15 2017-08-22 14:32:38 <esotericnonsense> in the pre-asic days it could avoid an attack whereby someone turns a shitton of machines on for one diff adjustment period and ramps difficulty by a factor of 100 or something silly
16 2017-08-22 14:33:09 <esotericnonsense> (it would be far more costly for them to achieve a similar ramp with the 4x rule as they'd have to mine for multiple periods with diff increasing each time)
17 2017-08-22 14:35:04 <ossifrage> esotericnonsense, ah yes, I remember that happening with some of the early bitcoin-clone-alts
18 2017-08-22 18:41:32 <cluelessperson> Hey guys, I'm reading the documentation for bitcoin private keys, and it describes that most keys are 256, and valid between 0x1 to 0xFFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFE BAAE DCE6 AF48 A03B BFD2 5E8C D036 4140
19 2017-08-22 18:41:59 <arubi> yep
20 2017-08-22 18:42:11 <arubi> well, what do you mean by most are 256?
21 2017-08-22 18:42:49 <cluelessperson> bits,  but then it says
22 2017-08-22 18:42:54 <cluelessperson> Newer wallets may use BIP 32 seeds for their private keys, which can be as long as 512 bits.
23 2017-08-22 18:43:16 <arubi> right, you usually use bip39 to derive a bip32 seed
24 2017-08-22 18:43:17 <cluelessperson> is that meaing you can use 512 bit bitcoin private keys?  or simply that bip32 may generate bitcoin keys (256 bit) FROM those BIP32 massive keys?
25 2017-08-22 18:43:29 <arubi> so that output is 64 bytes for the seed
26 2017-08-22 18:43:47 <arubi> core uses 32 bytes as the bip32 seed.  (actually it uses a valid private key)
27 2017-08-22 18:44:15 <arubi> ah no, those 64 bytes are hashed then you get 32 bytes private key and 32 bytes chain code
28 2017-08-22 18:44:20 <cluelessperson> arubi: That doesn't tell me what this documentation means.
29 2017-08-22 18:44:25 <arubi> private keys are always in that range
30 2017-08-22 18:44:30 <cluelessperson> Ah.
31 2017-08-22 18:44:56 <arubi> bip32 keys are extended private or public keys
32 2017-08-22 18:45:01 <cluelessperson> So, I think it means, "Master Keys" may be larger, as they wind up generating/deriving/hashing to validly ranged bitcoin private keys.
33 2017-08-22 18:45:08 <arubi> so both the private \ public bytes /and/ a 32 byte chain code
34 2017-08-22 18:45:39 <cluelessperson> arubi: What do you mean by chain code?
35 2017-08-22 18:45:54 <arubi> it's just another value used to derive the next level and index
36 2017-08-22 18:46:10 <arubi> (in the bip32 path)
37 2017-08-22 18:46:31 <arubi> cluelessperson, disregard bip32 and secp256k1 with its private key range
38 2017-08-22 18:46:36 <arubi> they're unrelated
39 2017-08-22 18:47:25 <arubi> these 512 bits seeds aren't private keys, just some output usually from kdf function of bip39
40 2017-08-22 18:47:29 <arubi> s/function//
41 2017-08-22 18:47:47 <cluelessperson> arubi: got it, the technical writing on the bitcoin wiki is just confusing to bring it up
42 2017-08-22 18:48:13 <arubi> yea seems so
43 2017-08-22 18:54:38 <meshcollider> arubi: the 512 bit output from the seed in BIP32 is split into two 256 bit halves, one of which is the private key and the other is the chain code
44 2017-08-22 18:55:09 <arubi> right, hmac-sha512'ed and split left and right
45 2017-08-22 18:55:25 <meshcollider> Yep
46 2017-08-22 18:56:00 <arubi> https://github.com/fivepiece/btc-bash-ng/blob/master/bitcoin/bips/bip32.sh :)
47 2017-08-22 19:01:08 <cluelessperson> what is chain code
48 2017-08-22 19:03:49 <meshcollider> It's just a 256 bit value used to generate children
49 2017-08-22 19:03:59 <meshcollider> It's all in BIP 32
50 2017-08-22 19:08:03 <arubi> yep that's pretty much it.  chain code is one input to a hash function used to generate the next level's chain code
51 2017-08-22 19:09:51 <arubi> well and key, but bip32 is better at explaining that part
52 2017-08-22 21:24:13 <kanzure> hmm i don't like this, https://lists.linuxfoundation.org/robots.txt   i would prefer it to have: Allow: /pipermail/* instead of: Allow: /pipermail/
53 2017-08-22 21:58:38 <cluelessperson> Could someone help me understand what this means?
54 2017-08-22 21:58:40 <cluelessperson> https://en.bitcoin.it/wiki/Wallet_import_format
55 2017-08-22 21:58:45 <cluelessperson> https://en.bitcoin.it/wiki/List_of_address_prefixes
56 2017-08-22 21:59:05 <cluelessperson> Specifically, when I decode the base58 WIF,  I get bytes
57 2017-08-22 21:59:41 <cluelessperson> Is there a trick to determining,   compressed(true/false),net from the WIF ?  or should I be trying to work out some logic table myself?
58 2017-08-22 22:00:02 <cluelessperson> " Drop the first byte (it should be 0x80)"  yeah, 0x80 is mainnet
59 2017-08-22 22:00:25 <cluelessperson> "If the private key corresponded to a compressed public key, also drop the last byte (it should be 0x01). If it corresponded to a compressed public key, the WIF string will have started with K or L instead of 5 (or c instead of 9 on testnet)"
60 2017-08-22 22:00:30 <cluelessperson> Jesus
61 2017-08-22 22:00:48 <cluelessperson> so, the last byte will only be 0x01 if it's compressed?
62 2017-08-22 22:01:01 <cluelessperson> or should I rely on the leading symbol to determine compression?
63 2017-08-22 23:14:40 <ginseng> HD wallets were introduced in core v.0.13.0. Were pre-0.13.0 wallets deterministic in any way or were they just 100 randomly generated keys?
64 2017-08-22 23:24:32 <esotericnonsense> ginseng: latter
65 2017-08-22 23:24:48 <esotericnonsense> i think there was a flag to set the size, you could pregenerate more if you wanted
66 2017-08-22 23:25:27 <Emcy> is it interesting that my .15rc node is uploading a lot less data than 14.2 did
67 2017-08-22 23:25:33 <Emcy> like less than half
68 2017-08-22 23:26:20 <Emcy> it was 37gb per day with 14.2, now its 16gb yesterday and 17gb today
69 2017-08-22 23:26:43 <Emcy> banning btc1 wouldnt have that much effect
70 2017-08-22 23:27:20 <Emcy> would it? Unless btc1 was attacking satoshi nodes to waste bandwidth? idk
71 2017-08-22 23:33:31 <ginseng> esotericnonsense: ty