1 2017-06-05 10:37:07 <mem0x> I'm having trouble using the obfuscate key to decode a chainstate value from bitcoind's leveldb
 2 2017-06-05 10:37:21 <mem0x> for example, the obfuscate key is 087600e1bfcc4020f5 in my db, and one of the chainstate c records is: 770861bef54026db8e98b4f1f00913a33addec04c17d337b8254fabf875cd5b83c82892af68c7023a286e0c1b00ed102f089b6
 3 2017-06-05 10:37:26 <mem0x> no matter how I xor these two I can't see the protocol version 01, any ideas what I'm doing wrong?
 4 2017-06-05 10:49:13 <mem0x> oh, I just got it, somehow I should skip the first byte from the obfuscation key
 5 2017-06-05 11:11:51 <wumpus> mem0x: the 0x08 is not part of the obfusction key, but the the size in serialization framing of a vector
 6 2017-06-05 11:36:11 <mem0x> wumpus: I see, thanks
 7 2017-06-05 13:54:12 <yellowsphere> hi, i want to be developer of the bitcoin, does the bitcoin has projects based on swift language?
 8 2017-06-05 14:38:19 <rdbell> yellowsphere: https://github.com/voisine/breadwallet
 9 2017-06-05 14:38:48 <rdbell> yellowsphere: I'm sure if you searched Github you'd find a lot of bitcoin related projects using swift
10 2017-06-05 14:38:49 <yellowsphere> rdbell: thank you
11 2017-06-05 15:38:13 <tachys> Can anyone point me to a tool which can give me a dump of the UTXO set (ideally each UTXO's value, and whether it is is P2SH or P2PKH)?
12 2017-06-05 17:06:50 <cdecker> tachys: rusty russell's bitcoin-iterate can do that :-)
13 2017-06-05 17:17:09 <Diablo-D3> who names their kid rusty russell?
14 2017-06-05 17:42:14 <Iriez> A pretty cool parent. I like the name.
15 2017-06-05 17:48:05 <abpa> His actual name is Paul
16 2017-06-05 18:49:12 <Diablo-D3> who names their kid muad'dib?!
17 2017-06-05 18:54:38 <arubi> Muad'dibs
18 2017-06-05 18:54:41 <arubi> 's name is also Paul
19 2017-06-05 19:10:46 <Diablo-D3> arubi: at least someone got it
20 2017-06-05 19:10:56 <Diablo-D3> I feel like my humor is underappreciated
21 2017-06-05 19:50:11 <Iriez> People who consume the spice, obviously.
22 2017-06-05 23:03:42 <coin_trader> annoying behavior, am i doing something wrong?... when running the same HD wallet on 2 servers, if you affect serverA with getnewaddress and extend the HD keypath - the other mirror wallet on serverB does not realize this, and even when coins get sent & balance is properly updated & kept in sync on serverB, it will still return an old address as "new" when you next call
23 2017-06-05 23:03:42 <coin_trader> getnewaddress since serverB is walking the same keypath steps as A...