I'm not aware of any utilities currently available that will allow you to present a private key and receive a public key in response..
Pywallet |
|
|
|
Sorry, by "compile" I meant "restore the private keys to a format usable by a Bitcoin client", i.e. make private keys usable. I will try to avoid using technical terms I don't understand.
I am still trying to figure out the best way to go about a recovery step-by-step. Is pywallet able by itself to find the deleted wallet/keys or would I have to run a separate utility beforehand?
Pywallet does tends to be practical: you run it (no separate utility, and no depency for recovery mode I believe), it finds the keys, then it create a usable wallet.dat
OP might give it a try
Which is why I recommended it. And I put "compile" in quotes because this was the term the OP used, apparently in reference to creating a new wallet.dat file based on the output read from an old one ("compile them into a wallet.dat using pywallet"). I knew that creating a new wallet.dat using the data read using pywallet hasn't traditionally been possible, but since I knew you were working on it recently, I didn't want to rule out a new feature categorically, however unlikely. I'm not unfamiliar with Python, pywallet, berkeleydb, or the wallet.dat format. It's possible now I know it works on Linux but I don't remember anyone testing it on windows |
|
|
|
|
The wiki explains everything
Also, writing a space before your command doesn't keep it in bash history
|
|
|
|
Note that pywallet cannot "compile" wallet.dat files (unless it's recently added this functionality).
I'm not sure what you mean by 'compile', but Pywallet can import csv files full of private keys for a few weeks More on topic, it can also read the partitions to find deleted keys/wallets, for more than a year OP might give it a try |
|
|
|
Patience is a virtue.
RTFM too |
|
|
|
off-topic, blockchain.info really should have forums, these days this forum is just full of these types of threads
+1 |
|
|
|
|
Pretty much anything that transforms your passphrase into 256 bits
sha256, first half of sha512, last half of sha512, sha1+sha1, ridemd256, etc
|
|
|
|
|
En fait celui qui mine un bloc fait ce qu'il veut
Si c'est un pool, il peut garder les frais ou les partager
Si c'est un mineur solo il n'a pas de raison de ne pas les prendre
Mais il ne faut pas oublier que coinbase+frais n'est que le maximum qu'un mineur peut tirer d'un block, rien n'empêche de se payer moins
|
|
|
|
Again...?
I meant "do they change". So, I can take that as a yes? They did this once (or twice), that's not that often This is why I use Terracoins. Confirmations are way faster which makes things much easier. When you are done just switch terracoind with bitcoind.
But you must buy them |
|
|
|
|
Are there some fallback nodes?
|
|
|
|
|
Yes I think a screenshot is better because I don't see what you're getting
What browser are you using? Is it old?
|
|
|
|
Now I just need to figure out how to actually store the hex in c++.
I'd say vector<char> You can also use strings I believe... But pay attention to '\x00', it may end strings unexpectedly. I am no specialist with string + binary + c++ though, so wait until someone confirms and always try and learn before trusting your code |
|
|
|
The public key, and further more all the hexadecimal data must not be used as strings, they are binary data For example the string "0123afz" is "3031323361667a" in hexadecimal (see ascii), aka "\x30\x31\x32\x33\x61\x66\x7a" Doing it wrongDoing it rightps: look at "Original bytes" too and notice how "045086..." as a string corresponds to "303435303836..." in binary |
|
|
|
|
So Hex is not checked but pywallet says "Hexadecimal private keys must be 64 or 66 characters long (specified one is 34 characters long)" ?
|
|
|
|
Which pywallet do you use? Mine or Joric's one? Assuming mine: What do you mean by black screen? This?  If so, you need to go to 127.0.0.1:8989 on your browser Instructions are there: pywallet.tk |
|
|
|
There is a mention of resetting TestNet. Does they change the root or something?
Again...? |
|
|
|
How is the guide comming? :3
Ditto double ditto Here it is: 1) read bitcoin wiki2) install compiler 3) start notepad 4) have a ball 5) compile newcoin Very, very far from being enough  |
|
|
|
|
How can you know whether a coin is lost or kept for the long term?
|
|
|
|
|
Yeah, the real problem is when the tx is broadcasted to the network
In this case, kjj's suggestion is the only thing to do
|
|
|
|
|
Show Posts
