[PULL] private key and wallet export/import - page 8.

Ryland R. Taylor-Almanza

legendary

Activity: 882

Merit: 1001

Quote from: SgtSpike on July 08, 2011, 06:32:15 PM

Quote from: molecular on July 08, 2011, 06:07:16 PM

Quote from: samr7 on July 08, 2011, 05:01:20 PM

Quote from: SgtSpike on July 08, 2011, 12:58:37 PM

This SHOULD be included in the default client. Reason being, it is incredibly useful for people who know how to use it, and not all of us know how to use linux or feel like spending hours on Windows attempting to compile the source with all of the dependencies.

Discluding a feature like this from anyone who doesn't know how to compile c code would be a terrible thing.

+1 more. This is a very important feature, whether it's exposed to end users or not.

Actually, I might have changed my mind (partly)

Exporting of a key has a problem, doesn't it: the key is still in the source wallet. There's no way to remove it, is there? Even if there is, it's easy to screw up and people will wonder where their money went.

The importing of a privkey is the part that is important for users (bitbill, import key generated with external tool like vanitygen) and this part, luckyly, poses no problems (that I can see), does it?

So how about splitting this and putting importprivkey in default, but not dumpprivkey?

I still disagree. I'd like to be able to export private keys from wallets, but really don't want to have to try to compile bitcoin again. That was a complete PITA.

SgtSpike, are you on windows? Do you have a binary with this patch that you can provide? I've been looking for one for a while.

SgtSpike

legendary

Activity: 1400

Merit: 1005

Quote from: molecular on July 08, 2011, 06:07:16 PM

Quote from: samr7 on July 08, 2011, 05:01:20 PM

Quote from: SgtSpike on July 08, 2011, 12:58:37 PM

This SHOULD be included in the default client. Reason being, it is incredibly useful for people who know how to use it, and not all of us know how to use linux or feel like spending hours on Windows attempting to compile the source with all of the dependencies.

Discluding a feature like this from anyone who doesn't know how to compile c code would be a terrible thing.

+1 more. This is a very important feature, whether it's exposed to end users or not.

Actually, I might have changed my mind (partly)

Exporting of a key has a problem, doesn't it: the key is still in the source wallet. There's no way to remove it, is there? Even if there is, it's easy to screw up and people will wonder where their money went.

The importing of a privkey is the part that is important for users (bitbill, import key generated with external tool like vanitygen) and this part, luckyly, poses no problems (that I can see), does it?

So how about splitting this and putting importprivkey in default, but not dumpprivkey?

I still disagree. I'd like to be able to export private keys from wallets, but really don't want to have to try to compile bitcoin again. That was a complete PITA.

molecular

donator

Activity: 2772

Merit: 1019

Quote from: samr7 on July 08, 2011, 05:01:20 PM

Quote from: SgtSpike on July 08, 2011, 12:58:37 PM

This SHOULD be included in the default client. Reason being, it is incredibly useful for people who know how to use it, and not all of us know how to use linux or feel like spending hours on Windows attempting to compile the source with all of the dependencies.

Discluding a feature like this from anyone who doesn't know how to compile c code would be a terrible thing.

+1 more. This is a very important feature, whether it's exposed to end users or not.

Actually, I might have changed my mind (partly)

Exporting of a key has a problem, doesn't it: the key is still in the source wallet. There's no way to remove it, is there? Even if there is, it's easy to screw up and people will wonder where their money went.

The importing of a privkey is the part that is important for users (bitbill, import key generated with external tool like vanitygen) and this part, luckyly, poses no problems (that I can see), does it?

So how about splitting this and putting importprivkey in default, but not dumpprivkey?

samr7

full member

Activity: 140

Merit: 430

Firstbits: 1samr7

Quote from: SgtSpike on July 08, 2011, 12:58:37 PM

This SHOULD be included in the default client. Reason being, it is incredibly useful for people who know how to use it, and not all of us know how to use linux or feel like spending hours on Windows attempting to compile the source with all of the dependencies.

Discluding a feature like this from anyone who doesn't know how to compile c code would be a terrible thing.

+1 more. This is a very important feature, whether it's exposed to end users or not.

bmgjet

member

Activity: 98

Merit: 10

Any one going to compile it into a windows client. Dont want to have to turn my mining PC off to mess around trying to compile it myself.

molecular

donator

Activity: 2772

Merit: 1019

Quote from: SgtSpike on July 08, 2011, 12:58:37 PM

Quote from: ?? on ??

Quote from: Hans0 on July 08, 2011, 12:29:00 PM

I am not sure this a suitable to be on by default. This will cause a great amount of lost bitcoins because unsophisticated users are careless.

+1

This is fine living in a separate branch.

Being able to recompile a branch is a nice
barrier of entry for the tech. clueless.

This SHOULD be included in the default client. Reason being, it is incredibly useful for people who know how to use it, and not all of us know how to use linux or feel like spending hours on Windows attempting to compile the source with all of the dependencies.

Discluding a feature like this from anyone who doesn't know how to compile c code would be a terrible thing.

+1

I'm actively using this feature and I would love to give out qr-codes (sealed) of privkeys to friends. Actually I gave one to a friend, but he's not supposed to open it before 6/17/2012. So I'd really love to have the feature in default client by that time Wink

Otherwise I'd have to compile bitcoin for windows, which I really would like to avoid.

Most "normal" users don't even know they can use RPC commands. I think compiling a branch is too high a barrier.

This is also needed for bitbills, btw, which is a pretty cool project as I think.

SgtSpike

legendary

Activity: 1400

Merit: 1005

Quote from: ?? on ??

Quote from: Hans0 on July 08, 2011, 12:29:00 PM

I am not sure this a suitable to be on by default. This will cause a great amount of lost bitcoins because unsophisticated users are careless.

+1

This is fine living in a separate branch.

Being able to recompile a branch is a nice
barrier of entry for the tech. clueless.

This SHOULD be included in the default client. Reason being, it is incredibly useful for people who know how to use it, and not all of us know how to use linux or feel like spending hours on Windows attempting to compile the source with all of the dependencies.

Discluding a feature like this from anyone who doesn't know how to compile c code would be a terrible thing.

Hans0

member

Activity: 91

Merit: 10

I am not sure this a suitable to be on by default. This will cause a great amount of lost bitcoins because unsophisticated users are careless.

rabit

member

Activity: 62

Merit: 10

Can i also remove a key from the wallet with this patch?

If not how many BTCs would it cost to motivate someone to add this feature?

Dynotor

newbie

Activity: 17

Merit: 0

Quote from: Pieter Wuille on July 04, 2011, 08:20:13 AM

Quote from: Dynotor on July 03, 2011, 12:07:17 PM

Can anyone help a git and github newbie like me figure out how to get a diff from the pull request? Just pointing me towards relevant documentation would be fine... I'm just having trouble finding it. I'm using linux.

Code:

git clone git://github.com/bitcoin/bitcoin
cd bitcoin
git remote add sipa git://github.com/sipa/bitcoin
git fetch --all
git diff master..sipa/showwallet

Thanks so much, Pieter!!!!!

Quote from: krepta3000 on July 04, 2011, 07:33:19 PM

So, uhm, I'm not a developer, and I've never used GIT. I'm downloading GIT for windows, msysgit, and I'm going to install it. Will this enable me to somehow get a version of bitcoin running that will let me do dumpwallet, and import wallet?

Krepta3000, before you bother trying to get git to work on windows, you might just make sure you can compile from the source first. I haven't tried to do so for windows for bitcoin before, but based on my experience with other open source projects the tool chain requirements for compiling under windows usually is much harder to satisfy than for Linux. My experience has shown me that using a VM running Linux (using virtualization software like VBox if you don't have a linux box handy) is usually a much easier route.

But... since I don't have experience with bitcoin in this area, I'll defer to anyone else with more direct experience...

krepta3000

member

Activity: 92

Merit: 10

So, uhm, I'm not a developer, and I've never used GIT. I'm downloading GIT for windows, msysgit, and I'm going to install it. Will this enable me to somehow get a version of bitcoin running that will let me do dumpwallet, and import wallet?

Pieter Wuille

legendary

Activity: 1072

Merit: 1181

Quote from: Dynotor on July 03, 2011, 12:07:17 PM

Can anyone help a git and github newbie like me figure out how to get a diff from the pull request? Just pointing me towards relevant documentation would be fine... I'm just having trouble finding it. I'm using linux.

Code:

git clone git://github.com/bitcoin/bitcoin
cd bitcoin
git remote add sipa git://github.com/sipa/bitcoin
git fetch --all
git diff master..sipa/showwallet

Dynotor

newbie

Activity: 17

Merit: 0

Can anyone help a git and github newbie like me figure out how to get a diff from the pull request? Just pointing me towards relevant documentation would be fine... I'm just having trouble finding it. I'm using linux.

krepta3000

member

Activity: 92

Merit: 10

Quote from: EricJ2190 on July 01, 2011, 02:02:45 AM

Quote from: krepta3000 on July 01, 2011, 01:50:08 AM

Hello? Anyone ever look at this thread anymore? I downloaded the tarball for this, extracted it into my bitcoin folder, and ran bitcoin, only to find that these new RPC commands are not included/installed. What do I do? I don't know C++, I'm not a great programmer, I don't know how to make this work. Help? Please?

For now, you need to recompile Bitcoin from its source code to use this. Hopefully this patch will be included in the next release.

But as for your corrupt wallet, I recommend bitcointools. There is a nice guide here: http://forum.bitcoin.org/index.php?topic=11331.0

Darn it, I don't know how to recompile things on windows. It's easy on linux, just type make, and everything is pre-scripted and it just works. On windows I have no clue. As for bitcointools, I tried that already, those hung transactions still are not announcing and being processed, so I want them Gone, deleted, removed. How do I do that with bitcointools? The only way I can see is to dump my wallet as a text file, then import that into a new wallet, not including the hung transactions and whatever it is that is causing the problem. But, I can't do that without "dumpwallet" and the other great RPC commands that I have no ability to use at the moment. Sad

EricJ2190

full member

Activity: 134

Merit: 102

Quote from: krepta3000 on July 01, 2011, 01:50:08 AM

Hello? Anyone ever look at this thread anymore? I downloaded the tarball for this, extracted it into my bitcoin folder, and ran bitcoin, only to find that these new RPC commands are not included/installed. What do I do? I don't know C++, I'm not a great programmer, I don't know how to make this work. Help? Please?

For now, you need to recompile Bitcoin from its source code to use this. Hopefully this patch will be included in the next release.

But as for your corrupt wallet, I recommend bitcointools. There is a nice guide here: http://forum.bitcoin.org/index.php?topic=11331.0

krepta3000

member

Activity: 92

Merit: 10

Hello? Anyone ever look at this thread anymore? I downloaded the tarball for this, extracted it into my bitcoin folder, and ran bitcoin, only to find that these new RPC commands are not included/installed. What do I do? I don't know C++, I'm not a great programmer, I don't know how to make this work. Help? Please?

krepta3000

member

Activity: 92

Merit: 10

I don't understand how to use these RPC commands to dump my screwed up wallet, and import the undamaged portion into a new wallet. In other words, manually construct a wallet that doesn't include the hung transactions. I have looked at the RPC commands my bitcoin client accepts, and these commands you list on this thread are not included. What do I do?

Pieter Wuille

legendary

Activity: 1072

Merit: 1181

Quote from: nelisky on June 28, 2011, 09:30:06 AM

You changed the code to

Code:

vch.insert(vch.end(), vch.begin(), vch.end());

The secret "vchSecret" was never being used.

Sorry, I must have been tired. Thanks for spotting the typo!

nelisky

legendary

Activity: 1540

Merit: 1002

Quote from: puddinpop on June 26, 2011, 03:42:13 PM

There's a crash caused by accessing an array element past the last one in base58.h, in the SecretToASecret function.

Code:

vch.insert(vch.end(), &vchSecret[0], &vchSecret[vchSecret.size()]);

vchSecret.size() is one past the last element, so it crashes here.

Since vchSecret is just a vector anyway, we can use this safer alternative:

Code:

vch.insert(vch.end(), vchSecret.begin(), vchSecret.end());

So the issue I posted above is a simple typo on sipa's commit. Instead of puddinpop's proposed change:

Quote from: puddinpop on June 26, 2011, 03:42:13 PM

Code:

vch.insert(vch.end(), vchSecret.begin(), vchSecret.end());

You changed the code to

Code:

vch.insert(vch.end(), vch.begin(), vch.end());

The secret "vchSecret" was never being used.

nelisky

legendary

Activity: 1540

Merit: 1002

I've cherry picked the two commits sipa mentions on the pull request onto bitcoin HEAD, compiling on a linux x64 machine (xubuntu 11.04) and while it compiles almost cleanly:

Code:

g++ -c -O2 -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -o obj/nogui/rpcdump.o rpcdump.cpp
rpcdump.cpp: In function ‘void GetWalletDump(std::map&)’:
rpcdump.cpp:116:82: warning: converting ‘false’ to pointer type for argument 2 of ‘bool ExtractPubKey(const CScript&, const CKeyStore*, std::vector&)’

But then calling dumpprivkey on *any* address will output

Code:

26zVKbYFG

I didn't debug the code, too tired to do that now, but maybe it's something obvious

Topic: [PULL] private key and wallet export/import - page 8. (Read 39577 times)