1 2013-03-15 00:01:40 <peawormsworth> I would like to know if it is possible to remove the wallet.dat passphrase encryption provided from bitcoin-qt.
2 2013-03-15 00:01:49 <peawormsworth> ...from outside of bitcoin-qt
3 2013-03-15 00:02:01 <peawormsworth> or if there is a way within bitcoin-qt to remove the passphrase.
4 2013-03-15 00:02:20 <peawormsworth> I have tried this: "openssl enc -d -aes256 -in wallet.dat -out wallet.dat.decrypted"
5 2013-03-15 00:02:34 <peawormsworth> but I got this: "bad magic number"
6 2013-03-15 00:03:05 <pjorrit_> the file itself is not encrypted just some of the contents are i belvie
7 2013-03-15 00:03:08 <pjorrit_> believe*
8 2013-03-15 00:03:13 <andytoshi> peawormsworth: nope, sorry
9 2013-03-15 00:03:18 <andytoshi> pjorrit_ is correct
10 2013-03-15 00:03:32 <andytoshi> the pubkeys and balances are in the clear, so that you don't need to type your passphrase so much
11 2013-03-15 00:03:49 <sipa> there are no balances stored in a wallet.dat file
12 2013-03-15 00:04:13 <sipa> but there are transactions, and which outputs are spent
13 2013-03-15 00:04:29 <andytoshi> sipa: where are accounts kept track of then?
14 2013-03-15 00:04:30 <peawormsworth> ok... but having portions of the wallet.dat encrypted... wont this make it impossible for use outside of bitcoin-qt? like in armory?
15 2013-03-15 00:04:43 <sipa> andytoshi: computed
16 2013-03-15 00:04:45 <andytoshi> peawormsworth: no, it's open-source
17 2013-03-15 00:05:33 <gavinandresen> peawormsworth: yes, it is a very bad idea to use the same keys in two different applications. We make it hard for you to do that.
18 2013-03-15 00:06:12 <gavinandresen> ??? or maybe it would be more accurate to say we don't make it easy, we don't really go out of our way to make it hard.
19 2013-03-15 00:06:38 <peawormsworth> ok thanks for the info.
20 2013-03-15 00:15:49 <ProfMac> Can anyone see the web page at http://ns2.vima.austin.tx.us/
21 2013-03-15 00:18:21 <andytoshi> nope
22 2013-03-15 00:20:16 <andytoshi> programmers: http://xkcd.com/1185/
23 2013-03-15 00:35:40 <yebyen> rdponticelli: no, arm client though
24 2013-03-15 00:40:24 <yebyen> rdponticelli: i'm going to try and transfer it to a faster host with more memory that's not ARM, if it still fails then I guess I will have narrowed it down
25 2013-03-15 00:40:49 <yebyen> if it succeeds narrowed it down too I guess
26 2013-03-15 00:40:59 <yebyen> or if I can download the blockchain with no wallet
27 2013-03-15 00:41:25 <rdponticelli> Ok, try
28 2013-03-15 00:41:51 <yebyen> it's only testnet coins that are targeted at one block every 10 seconds
29 2013-03-15 00:41:55 <yebyen> with low low difficulty
30 2013-03-15 00:42:26 <yebyen> took me less than a few days to gen 500k coins
31 2013-03-15 00:42:40 <rdponticelli> Do keypoolrefill work?
32 2013-03-15 00:42:46 <yebyen> what's that?
33 2013-03-15 00:42:52 <yebyen> I can try it
34 2013-03-15 00:43:14 <rdponticelli> Looks like it failed when the bitcoinminer asked for a new address
35 2013-03-15 00:43:30 <sipa> yebyen: is your wallet encrypted?
36 2013-03-15 00:43:49 <yebyen> no, not unless you can accidentally encrypt your wallet by 51%'ing your network long enough
37 2013-03-15 00:43:54 <yebyen> or 92%'ing
38 2013-03-15 00:43:58 <sipa> doubtfully
39 2013-03-15 00:44:03 <rdponticelli> And the failure was on the wallet, trying to create a new key
40 2013-03-15 00:44:30 <yebyen> and I tried dumping the block chain several times, but I genned solo on this chain, so I don't want to just toss it
41 2013-03-15 00:45:04 <yebyen> but if there's a longer chain that doesn't include those blocks, maybe I don't have a choice
42 2013-03-15 00:45:29 <sipa> only explanation, code-wise, is that CDB::Write failed
43 2013-03-15 00:45:34 <sipa> so some BDB problem with the wallet
44 2013-03-15 00:45:39 <sipa> you may want to look at db.log
45 2013-03-15 00:45:50 <yebyen> unfortunately I did not save that
46 2013-03-15 00:46:24 <yebyen> that would have been a good idea
47 2013-03-15 00:46:58 <yebyen> I thought memory, because this machine only seems to have ~700mb of memory
48 2013-03-15 00:47:13 <yebyen> and it rides pretty close to full before setgenerate true
49 2013-03-15 00:47:24 <yebyen> but I added 1gb swap and no help
50 2013-03-15 00:48:16 <phantomcircuit> yebyen, if you can out of memory the process would have been killed
51 2013-03-15 00:48:31 <phantomcircuit> linux only disallows memory allocation for ridiculous amounts
52 2013-03-15 00:48:35 <yebyen> it sure died, but not with "Killed: out of memory"
53 2013-03-15 00:48:41 <phantomcircuit> unless you change the specific setting
54 2013-03-15 00:48:51 <phantomcircuit> which i doubt you did
55 2013-03-15 00:48:54 <yebyen> this is pretty much stock android
56 2013-03-15 00:48:58 <yebyen> i haven't even compiled the kernel
57 2013-03-15 00:49:01 <yebyen> eos4
58 2013-03-15 00:51:57 <yebyen> debian in chroot
59 2013-03-15 00:55:18 <gribble> Error: "bc;blocks" is not a valid command.
60 2013-03-15 00:55:18 <MKCoin> ;;bc;blocks
61 2013-03-15 00:55:56 <MKCoin> Well rather than guess I'll wait for someone to use the right command
62 2013-03-15 00:56:27 <epylar> don't everyone talk at once.
63 2013-03-15 00:56:55 <iwilcox> Needs to be a comma, that last ';'
64 2013-03-15 00:58:29 <BTC_Bear> ;;blocks
65 2013-03-15 00:58:30 <gribble> 225916
66 2013-03-15 00:58:32 <MKCoin> ahh
67 2013-03-15 00:59:55 <VoteGoat> how many addresses could be realistically handled in one wallet?
68 2013-03-15 01:00:46 <VoteGoat> I am making a service which would need potentially hundreds of thousands of bitcoin addresses and am figuring out the best way to do it
69 2013-03-15 02:22:44 <keystroke> how is 0.8.1 coming along?
70 2013-03-15 02:41:34 <RoboTeddy> have we determined precisely how to produce blocks that don't put <=0.7 over the lock limit?
71 2013-03-15 02:43:05 <RoboTeddy> and if so, can we in practice consistently construct 1MB blocks that won't freak <=0.7 out?
72 2013-03-15 02:52:57 <andytoshi> does anyone here have a mac on which they can compile something for me?
73 2013-03-15 02:53:19 <andytoshi> (not bitcoin related, just something a prof would like to use)
74 2013-03-15 02:53:25 <RoboTeddy> andytoshi: sure if it's easy
75 2013-03-15 02:53:30 <RoboTeddy> andytoshi: message me out of channel
76 2013-03-15 04:08:13 <cads> hah, sipa, I actually do have a BTC dev question.
77 2013-03-15 04:09:13 <cads> What would one use to give lambdabot her own BTC data feed?
78 2013-03-15 04:10:12 <cads> I also want to give her a wallet with a BTC or so, just so she can feel special and maybe someday buy something nice for herself with it.
79 2013-03-15 04:12:22 <cads> (for those unfamiliar with lamdabot, it is a fairly extensible IRC bot written in haskell.)
80 2013-03-15 04:13:24 <cads> (it can do a few unusual things for a IRC bot, including compiling and running arbitrary code given to her by channel members)
81 2013-03-15 04:14:42 <cads> This question fits under the idea of programming bitcoin agents. I have only seen theoretical work on this so far.
82 2013-03-15 04:15:04 <cads> But perhaps you guys know of an existing project?
83 2013-03-15 04:15:25 <jrmithdobbs> welcome to 1991 or something
84 2013-03-15 04:15:44 <jrmithdobbs> yes, that's been done over and over, and is one of the reason tcl is so popular for dumb irc bots
85 2013-03-15 04:16:57 <cads> jrmithdobbs: ah, shoot, I was vague. I meant to ask about projects with the goal of giving a bot the ability to autonomously spend BTC
86 2013-03-15 04:17:28 <jrmithdobbs> so, you want to know how to speak json in <language>?
87 2013-03-15 04:19:26 <jgarzik> cads: Old idea :) http://garzikrants.blogspot.com/2013/01/storj-and-bitcoin-autonomous-agents.html
88 2013-03-15 04:19:42 <cads> This is the theoretical work I've sees: https://en.bitcoin.it/wiki/Agents . I am not sure whether the ideas of automated agents here are being implemented.
89 2013-03-15 04:19:56 <jgarzik> cads: You need to (a) speak JSON or (b) speak bitcoin binary data structures
90 2013-03-15 04:20:06 <cads> that's trivial
91 2013-03-15 04:20:11 <jgarzik> cads: if (a), you need bitcoind running alongside your bot
92 2013-03-15 04:20:29 <jrmithdobbs> a is pretty straight forward and simple.
93 2013-03-15 04:20:33 <jgarzik> cads: if (b), you need to do a _lot_ of coding. Start now, and check back in in 6 months.
94 2013-03-15 04:20:44 <cads> yeah, a) sounds the best.
95 2013-03-15 04:21:00 <jgarzik> cads: StorJ (my link) is the inspiration for the /Agents wiki page.
96 2013-03-15 04:22:22 <jgarzik> cads: gmaxwell, petertodd and I like to poke at the bot subject
97 2013-03-15 04:22:29 <jgarzik> cads: another related link, https://bitcointalk.org/index.php?topic=146307.0
98 2013-03-15 04:22:47 <cads> jgarzik: yep, I am reading that now
99 2013-03-15 04:23:12 <cads> I read the agents article by itself a few months ago and since the idea has sunk in
100 2013-03-15 04:23:20 <cads> it's a very provocative idea
101 2013-03-15 04:23:34 <jgarzik> cads: agents article is pretty crappy, IMNSHO, but anyway :)
102 2013-03-15 04:23:54 <cads> The amount of coding required for an agent to interact with ISPs and some job market is of course _very_ intimidating
103 2013-03-15 04:24:00 <jgarzik> cads: Also read https://en.bitcoin.it/wiki/Contracts
104 2013-03-15 04:24:24 <jgarzik> cads: well you write the high level profit-seeking modules, testing modules, and pay humans to fill in the blanks
105 2013-03-15 04:24:36 <cads> yes, contracts are rather impressive as well
106 2013-03-15 04:24:37 <jgarzik> cads: StorJ article explains the economic incentives required
107 2013-03-15 04:24:56 <cads> both as they could be applied to bots, and for actual human/human interactions
108 2013-03-15 04:24:58 <jgarzik> cads: "[...]instead it forms agreements that make it unprofitable to cheat."
109 2013-03-15 04:25:06 <jgarzik> cads: correct
110 2013-03-15 04:25:25 <CodeShark> you don't need (a) and you only need to do a lot of coding if you're not making use of an existing JSON <-> bitcoin binary datastructures library
111 2013-03-15 04:25:42 <jgarzik> He's in Haskell
112 2013-03-15 04:25:43 <jgarzik> ;p
113 2013-03-15 04:25:48 <CodeShark> oh, hmmm
114 2013-03-15 04:26:00 <CodeShark> well, it would be nice to have a library in haskell for this :)
115 2013-03-15 04:26:27 <cads> jgarzik: we'd essentially ensure something that could be called a zero trust equilibrium
116 2013-03-15 04:27:44 <jgarzik> cads: well, like nature or markets themselves, always seeking equilibrium but never attaining it. Services will be profitable and grow; they will be unprofitable and wither.
117 2013-03-15 04:28:25 <jgarzik> cads: another idea discussed was a network of semi-trusted bots, that cooperate to create an off-chain micropayments service
118 2013-03-15 04:28:36 <jgarzik> provable to themselves, and to their users, that there is no cheating
119 2013-03-15 04:28:44 <cads> (in game theory an equilibrium is a set of player strategies where each player has no (or almost no) incentive to deviate from their chosen strategy)
120 2013-03-15 04:28:53 <warren> discussed where?
121 2013-03-15 04:29:00 <randy-waterhouse> we have they are called exchange operators
122 2013-03-15 04:29:01 <jgarzik> IRC
123 2013-03-15 04:29:41 <cads> jgarzik: I like the micropayments idea
124 2013-03-15 04:31:10 <cads> At first humans can rent sizeable chunks of compute resources. They could then rent out to agent 'tenants'.
125 2013-03-15 04:31:14 <warren> Conceivably a trusted bot network with its own chain could fully automate a BTC/alt pair exchange complete with escrow.
126 2013-03-15 04:31:44 <cads> It's not like the agents will have a choice but to trust the human, and it's very likely that the human would be trust worthy, because of their likely vested interest in BTC and Agents.
127 2013-03-15 04:32:29 <cads> I may be describing what randy-waterhouse just mentioned :)
128 2013-03-15 04:34:10 <jgarzik> warren: yep
129 2013-03-15 04:34:16 <cads> I think it may be hard to satoshi this into existence in any well polished form
130 2013-03-15 04:34:29 <jgarzik> cads: indeed, that's the rub
131 2013-03-15 04:34:46 <jgarzik> cads: hard to initially trust a bot, and build a network of human workers
132 2013-03-15 04:35:21 <cads> I would be satisfied to create a lambdabot/otherbot that securely carries a wallet but can't spend it.
133 2013-03-15 04:35:40 <jgarzik> cads: bitcoin is fundamentally private key management
134 2013-03-15 04:35:44 <cads> Then others could decide how they might want to code the bot to spend that money temptingly stored inside it.
135 2013-03-15 04:35:53 <jgarzik> cads: understand that, and you understand how to work the problem
136 2013-03-15 04:36:05 <jgarzik> cads: yep