13. when you can't sleep with less than 90dB

At first you were writing shit for MtGox: http://forum.bitcoin.org/index.php?topic=20820.msg260726
But then you are writing shit against it

It depends on the amount
No problem for MtGox $/BTC, but for bitparking BTC/NMC it can be costly indeed

You might take a look at my pywallet fork ( http://github.com/jackjack-jj/pywallet ), which can import/export keys, even hidden ones, with labels
It's highly based on Joric's work http://github.com/joric/pywallet

Anyway the hashes calculated while in a pool wouldn't have been the same while solo mining

5b. when, while in a noiseless place, you think 'there's a weird sound over here'

First post edited

Yes it's up now

ZOMGBBQ breakin news!!

I like this thread
I'll post if I found some

Relance les par mail, c'est pas normal

Could you explain how to compile the git project?
Because Java is not exactly the kind of stuff i'm used to compile

Check how many blocks your client downloaded
If it's 137873, your transaction should have some confirmations

darkwon, is your transaction still 0/unconfirmed?

It seems that sending nearly all your BTC makes forever-0/unconfirmed transactions, this is the third time I see that

OP, is your transaction still 0/unconfirmed?

Hi,
First, sorry for writing in english...
For whatever the reason, if your transaction stays 0/unconfirmed for long and you want to cancel it, you may try my python script
Just ask me if you want, i would tell you how to use it

This is far less efficient than using the new pywallet, see here: https://bitcointalk.org/index.php?topic=35214.0

Hi all
While playing with the bitcoin client, I made some 0/unconfirmed transactions (no confirmation for 2 days)
I didn't find anything simple to recover the bitcoins lost

When I finally found a method to cancel those transactions I made a python script to make that simple

So, are those unconfirmed transactions still a problem?
If so I'll write here how to cancel them


Here it is:
0. I'm assuming that your wallets are in Bitcoin default directory, if not, use -w and -n options at step 6
1. Backup your broken wallet.dat
2. Rename it wallet.old
3. Find the wallet into which you want to add the old adresses (you can run bitcoin to create a brand new one) and rename it  wallet.new
4. Download my pywallet fork: https://github.com/jackjack-jj/pywallet and write down the directory you put it
5. Download my walletco: https://github.com/jackjack-jj/walletco
6. Assuming both wallet.new and wallet.old are in bitcoin default directory(if not, look at walletco options), run this: /path/to/walletco.py -p /pywallet/directory/ -W wallet.old -N wallet.new
7. Rename wallet.new to wallet.dat (or use my bitcoin fork to chose the walletfile)

In the next release, walletco will auto backup both wallets

Feel free to make pull requests and tell me if it fixed your wallet

Rescanning the blockchain didn't solve the problem for me (forever unconfirmed transactions too)
I made a little python script, you may try it, it worked for me: https://github.com/jackjack-jj/walletco

Check on blockexplorer what block contains your payment