Okay, it finally found some connections and is updating.
I thought the minimum fee was reduced to .0005 bitcoins? I tried sending some bitcoin and recieved the error message that it requires a transaction fee of .01 due to the complexity, size, or use of recently recieved funds.
0.3.23 will lower the fee. I am sending >.01 BTC, so the size should be okay. I am just sending from one address to another, so the complexity should be okay. The funds have over 1000 confirmations, so they are not recently recieved (BTW, how recent is recent?, and am I correct that the recentness is measured by confirmations?). What am I missing?
You are probably combining a shitload of tiny coins, thus making a large (in kB) transaction. |
|
|
|
Thanks for reviving this old thread.
I've added a "vanityAddress" function in my bash lib:
Cool, except it doesn't work... bash: ibase=16; n=${1^^}; while(n>0) { n%3A ; n/=3A }: bad substitution
|
|
|
|
|
One of the purposes of the fees is to avoid spam on the network. If you made the recipient pay, anyone could drain someone's balance by spamming them with empty transactions, each one taking 0.01 from the victim's balance.
|
|
|
|
Too bad that the faucet is down. Post your Bitcoin address in this thread and maybe some generous forum member will send you a bitcent to play around with...  |
|
|
|
I want to see the answers to this because I am so confused about the wallet! I just encrypted my wallet.dat, I think, using truecrypt. That is, I encrypted a BACKUP of wallet.dat. But the original wallet.dat is sitting there on my drive unencrypted and seemingly vulnerable as hell! I still don't get how to have a long-term, deep storage wallet and another spending money wallet.
Any help with this stuff would be most appreciated. Might even get a tip!
Bitcoin will eventually encrypt wallet.dat, but it does not yet do that. To have a secure "savings account" wallet, I would suggest installing Bitcoin inside a VirtualBox VM. That way any viruses on the host computer can't access the wallet. You only need to boot up the VM when you want to spend coins, you can receive them while Bitcoin isn't running, and check the balance on blockexplorer.com. |
|
|
|
Can we kick you instead
+1  |
|
|
|
I have also successfully sent money to Mt. Gox this week. I just checked and I now also have an X at the end of my number. I hope the transfer I sent yesterday (without X) goes through...
UPDATE: The money made it to Mt. Gox without problems. |
|
|
|
For the last several days I've been trying to connect to "the network" with the standard bitcoin client (0.3.20.1), but it's stuck at 0 connections, 125364 blocks.
I saw that there was a version 0.3.22 released, but I didn't think I had to upgrade to stay connected.
How can I help my poor client connect? I've got a few coins floating around in transactions my client hasn't downloaded yet, and would like to send them somewhere else!
Upgrading to the latest version may help since the IRC bootstrapping mechanism was changed. The other standard advice is to (a) forward port 8333 in your router and/or (b) add some fallback nodes. |
|
|
|
That would work but it requires you to teach every browser how to handle the bitcoin: protocol.
No. URI handlers are registered in the operating system. |
|
|
|
Argh! Stop it with the unnecessary slashes already! Double slashes introduce a server name, there are no server addresses in bitcoin! The Bitcoin URI scheme already exists, and is documented on the Wiki: https://en.bitcoin.it/wiki/URI_Scheme |
|
|
|
I have had anywhere from 1-9 connections for the last 3 days and 900,000 blocks on the lower right corner of my client. Using Mac OS X.
Welcome, visitor from the future. What's it like in the year 2026?  |
|
|
|
Has anyone successfully moved any money to or from Mt.Gox using SEPA in the last 7 days? I did, and I still had the number without the X. But I just checked and now I also have it with the X. So it seems they've changed it (probably for some good reason). I have also successfully sent money to Mt. Gox this week. I just checked and I now also have an X at the end of my number. I hope the transfer I sent yesterday (without X) goes through... |
|
|
|
What I mean is, if I say that my Bitcoin address is 13FsW67CtKn97TfjVqG8bDqTRA3b7Xjgxg , can you be sure that you see what I actually wrote? Maybe an evil forum admin changed the address to his own, so instead of giving me money, you give it to the forum authorities...
This is what PGP signing was invented for. |
|
|
|
Wait. This is the target for finding a full block? I thought the getwork function returned a easier problem.
bitcoind returns the current network difficulty. You need pool software to get difficulty 1. |
|
|
|
As per the above story: 18,838.31000000 + 0.01000001 ----------------- 18,838.32000001 |
|
|
|
|
Show Posts
