|
Yes
I heard he eats babies too
|
|
|
|
So let me get this straight. You can create a private key with a passphrase import it into a wallet. Transfer funds to it and then delete the wallet.dat and recover it by repeating the process?
You don't have to import the key to transfer funds to it, and should not do it |
|
|
|
Another new feature: importing transactions Now, offline transactions are far more simple than before (no more command lines or unofficial client)
|
|
|
|
It was something I wanted for me and I believe it can be useful for others I just tested it and it works as expected Here's the situation: - Computer A, with:
- wallet located at /home/a/.bitcoin/wallet.dat
- pywallet downloaded somewhere and running using './pywallet.py --web'
- Computer B, with:
- wallet located at c:\bitcoin\b\wallet.dat
- pywallet downloaded somewhere and running using './pywallet.py --web'
A is offline and makes a transaction, B will broadcast it Instructions:Short method, exporting all tx's:Backup your wallets Close all Bitcoin instances Everything has to be done on A until I said it's on B - Send your transaction
- Go to http://localhost:8989
Under the Dump transactions section:
Type '/home/a/.bitcoin' and 'wallet.dat' in wallet directory and wallet filename
Type the full path of the output file, e.g. on a USB drive
Then click on the Dump button
From now, everything is made on B Long method, exporting only one tx:Backup your wallets Close all Bitcoin instances Everything has to be done on A until I said it's on B - Send your transaction: if you use bitcoind, you already have your txid, if you use GUI, remember the amount you sent
- Go to http://localhost:8989
Under the Dump section, enter '/home/a/.bitcoin' and 'wallet.dat' in wallet directory and wallet filename
Then click on the Dump button - Using Ctrl-F, find either your txid or your amount (beware, there may be more than one transaction with that amount)
{
"tx_id": "ae788fb76a935c5f3127bf5c7d860be4f90bae89782235ab55baf559a917404e",
"tx_k": "0274784e4017a959f5ba55ab35227889ae0bf9e40b867d5cbf27315f5c936ab78f78ae",
"tx_v": "0100000001d9f102cc434df41ef7[...]370656e74000001000000aa3a3f4e0100",
"txin": [
{
...
}
],
"txout": [
{
...
},
{
"scriptPubKey": "76a91425e8b5ed100729c5027a49643219e30a67356a3e88ac",
"value": 10.0
}
]
}, - Copy tx_k and tx_v values on a USB drive
From now, everything is made on B Now, run bitcoin on B and it will broadcast the transaction made by A Feel free to post comments/suggestions/etc |
|
|
|
|
If the guy is honest, yes
So, no
|
|
|
|
But it's not just random jibberish with good variety of low and high caps, numbers, symbols etc, people are gonna use words and phrases that tend to make sense
Yep I will force users to use some special characters |
|
|
|
Are people really gonna be imaginative enough with the phrases for the risk of collision to be negligible?
My program refuses passphrases below 40 characters or 7 words, casascius should do that too... |
|
|
|
What a pain... I'm glad it finally works
I'll add these instructions for other Win7 users, thanks!
would it be legal to package it all up into an archive and set up all the scripts? I think so, good idea |
|
|
|
I have a master's degree in applied economics...
That shows you know nothing about economics. I don't mean to insult but ask me to prove it and I will. I like where this thread is going  |
|
|
|
Je suis nouveau avec Bitcoin, cela fait plus de 24 heures que Bictoin tourne sur ma machine, en ce moment il affiche 21 connexions et 20362 blocks et je n’ai toujours rien encore reçu. C’est normal ?
En dehors du fait qu'il y a actuellement 140000 blocs et que donc tu dois encore attendre un bon moment et avoir tout téléchargé pour être à jour, qu'aurais-tu voulu recevoir? Quelqu'un t'a-t-il déjà payé? Je demande ça parce que comme ta phrase est tournée on dira que tu t'attends à être payé juste pour avoir lancé le programme Autre chose, quand je l’ouvre, j’ai un message d’alerte:
“ warning :, please check that your computer’s date and time are correct. If your clock is wong Bitcoin will not work properly”.
Bizarre, c'est le bon fuseau horaire? |
|
|
|
Here's what I usually use <?php
$a=ouvrirpage("https://mtgox.com/code/data/ticker.php");
$res=json_decode($a, true);
echo $res['ticker']['last'];
function ouvrirpage($site){
$ch = curl_init($site);
curl_setopt($ch, CURLOPT_USERAGENT, "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
$res = curl_exec($ch);
curl_close($ch);
return $res;
}
?> Maybe MtGox needs an useragent header |
|
|
|
On testnet, mainnet addresses are basically "aliases" of their equivalent testnet addresses. Sending to 1KNHQ7513gVwJv5fG4ucsPgkdb5Ub9UzR6 is exactly the same as sending to mytEhA9yrhwC62ZGydszhJu5VagBZj2z7t. The only difference between these two addresses is the version and checksum: the public key hash is the same.
If you copy your wallet.dat from mainnet to testnet, your receiving addresses will all still be there: they will just have been changed to their "testnet" aliases. The associated mainnet versions will still work for transactions on testnet.
On testnet, there are actually 111 valid ways of expressing of every address. These are all the same:
1KNHQ7513gVwJv5fG4ucsPgkdb5Ub9UzR6
ihtPDNHkrxp8MDkHVEwMWxYG6LRMEvGhC
283VNKfaU3RgwnMqJuaFqeEKtbbN1Q5KFY
2XP6MRxsBDtZmDVvLKuaKmW7X6rJiSaZ9Z
2vihLYG9tQMSaee1MkEtotmu9c7FSBxg9a
3L4JKeZSbapKQ5n6PAaDJ23gn7NCD2x9V1
...
I understand that, I don't understand why this behavior is useful or desirable in any way. Couldn't we just say when running i testnet mode you need to use the 111 tagged version of the address. The others will generate an error. It seems to me it would prevent some mistakes sending testnet coins to limbo when we think we are sending mainnet coins. The theymos' post, 3 posts above is rather clear It's for when we'll use a new kind of addresses, e.g. when we'll use addresses version 2, it would be useful to send coins to old addresses... Also, testnet coins sent to bitcoin address are easily retrievable, I made a guide about that |
|
|
|
46736 = index('E') * 58^2 + index('t') * 58 + index('o') = 13*58*58 + 51*58 + 46
Hope that helps!
-Eto
so, "test" would be (51 * 58 * 58 * 58) + (37 * 58 * 58) + (50 * 58) + (51) which would be 10078131. Is this correct? . Yes |
|
|
|
If you want to reach not-too-savvy people I think a guide needs to be written how to get it up and running on Mac since bsddb is broken in (at least) Snow Leopard (I believe Leopard as well, haven't tried Lion). Dumping related commands from my bash history, but I had Macports installed since before. The following should be tested by someone who hasn't installed Macports or pywallet, on a clean install. It's just from memory/history. Mac pywallet installation guide: sudo port install python27 python_select
sudo python_select python27
sudo port select --set python python27
sudo port install py-bsddb
sudo port install py27-twisted
./pywallet.py (yeah python_select might be overkill if the user is never going to install other python versions) Thanks! I forgot I have a Snow Leopard VM...... I'll test that there |
|
|
|
Maybe add a small "backup your wallet just in case" message ?
It was stupid to forget that, thanks Since your utility is for dealing with wallets would it be hard to add a backup and encrypt option?
I think it's better that the user makes it himself, because each of us have a different way to backup. But if many people ask so, I can add it I absolutely don't know how Satochi's client encrypts wallet, and I prefer waiting the official release before looking into that Is this open source? If so were can I look at the code?
As Bitlotto told you, it's in Python and open source: https://github.com/jackjack-jj/pywallet/blob/master/pywallet.pyCommits: https://github.com/jackjack-jj/pywallet/commits/masterPywallet thread: https://bitcointalk.org/index.php?topic=34028.0P.S. For some reason this post says red flag to me, but I'm paranoid so it's probably nothing.
Better safe than sorry  |
|
|
|
Ultimate way to delete your forever unconfirmed transactions - Backup your wallet just in case
- Download Pywallet
- Run './pywallet.py --web'
- Go to http://localhost:8989 in your browser
- Fill the Delete form like this:
- Wallet Directory: /your/wallet/directory
- Wallet Filename: yourwalletfilename
- Key: all
- Type: leave 'Transaction'
- Click the Delete button
- Run 'bitcoin -rescan'
- Done, no more unconfirmed tx's
|
|
|
|
|
New awesome feature: you can now delete addresses and tx's from your wallet!
So:
no more headaches because of 0/unconfirmed transactions: find it, delete it
easier wallet management: YOU chose exactly which addresses you want in which wallet
|
|
|
|
|
Show Posts
