Interpretation: "please keep me updated with the progress you are making"

If you want to download another copy of the blockchain through the Bitcoin network (which can be from another local bitcoin of yours), you can use https://github.com/jgarzik/pynode. It is a Python standalone Bitcoin node with limited functions. It has a script, mkbootstrap.py, which will also generate the torrent file.

I don't think that's an "idea"; that's just a statement that there is no web wallet service exclusively for Namecoin. You can send your Namecoins to several different places for holding, such as exchanges, if you feel the need to trust anonymous Internet entities with your money.

Proxy test.

This picture should load instantly, it's two colors and 243 bytes:


This is a bigger image, 353kB:


Same image, hosted on imgur.com:


This image loads in about 0.2 ms, is 1.4kB, but generated by php.


This image requires over a second, it gets data from a third-party web site:

You can send a PM to a mod if this is the fear, I'm sure they'll ban the account if you ask nicely, or if that doesn't work, extremely rudely.

I've not had this problem, since I have yet to even use the newest version to store my zero bitcoins, but there are some questions that may clarify to others what you are experiencing:

1. Is the latency you are describing the amount of time for an RPC getwork request to receive a response? Is it on the local network, using any proxies or pool software etc? Do other RPC commands have a similar unexplained delay?

2. You reply "SSD latency" which would be completely different than #1. If your whole SSD drive becomes less responsive while Bitcoin is thrashing it (like during block download), it may be because of flash memory garbage cleanup running in the background inside the drive. This can be improved by both ensuring TRIM support is enabled on an AHCI-supporting hard drive controller in both BIOS and your OS, and by leaving lots of free space on the drive, even unpartitioned space, so that flash memory doesn't need to be immediately cleared for reuse. Writing data to flash memory is fast, but the technology of erasing deleted data from flash memory cells for reuse is slow.

For what purpose are you making getwork requests if you aren't mining?

OCLvanitygen is fast because the addresses stay in the GPU (only a match is returned). It is also fast because a typical GPU has 1000 processing units. It would probably be even faster if you removed the final check to see if the generated address matches a pattern.

I imagine it wouldn't be much of a stretch after you get oclvanitygen compiling to remove the pattern-checking code in CL and return all addresses; how fast the C wrapper could deal with such a stream of data would then be the issue. The generated addresses would not be secure and random though; the private keys would be *VERY* related to each other - oclvanitygen just increments from an initial random value. To generate good addresses for actual use (not just some impossiburu hacking project), you need a true random source with a fast data stream - the ECDSA will not be the speed limiting factor.

Once you have Bitcoin Core installed and it is done downloading (and you have taken precautions such as encrypting and backing up the wallet), you can simply send bitcoins from Multibit or any other wallet to a new receiving address as a normal network payment.

The most likely scenario is that your return to the forum with a different account name didn't undo the previous IP ban you already earned.

If you are on an ISP with dynamically-assigned and changing IP addresses, there is an impossibly remote chance that another user on the ISP earned the ban. If you are accessing through Tor or a proxy, the exit IP was likely previously abused and must stay IP banned.

I just ignored some german speaker on the linked discussion, it seems to be working fine. If such a problem exists, it is likely due to certain user's web browser configuration.

I can recommend a good secure alternative to the above: an OS that has never been touched by another Bitcoiner.

https://bitcointalk.org/index.php?topic=361092.0 has paper wallet generator software that will run on almost any Linux live CD, and some instructions about using one of the smaller and more secure distros.

A paper wallet or offline/cold storage address is only needed if you have too many bitcoins to lose though.


If you are just getting started and have patience, I would recommend you get familiar with Bitcoin "core"; very few people have ever lost bitcoins with a strongly encrypted and backed up Bitcoin-Qt wallet:

1. get the blockchain torrent started now, to download the 10gb bitcoin bootstrap https://bitcoin.org/bin/blockchain/bootstrap.dat.torrent,

2. use the bootstrap torrent and get the wallet software caught up to the current block,

3. encrypt your wallet with an uncrackable password (you can write it down locally; you are protecting your wallet against hackers stealing the wallet file over the Internet),

4. back up your wallet through the menu, save it to two different media; mail a CD to a relative; protect against your house being burglarized or burning down.

5. Do not get infected with trojan horse wallet stealing key logging software. If you must use your Bitcoin wallet computer to browse the web, do not download any unknown software from places that may be aware of your Bitcoin use. Remove Flash, Java, and Acrobat reader; these are unfixable holes into an OS. Use Firefox with the requestpolicy addon, so all third-party content on web sites must be manually allowed by you (or at least use noscript). Keep the OS fully updated. Use a Linux OS.

5. Then you can start using Bitcoin to store your own money.

6. If you need convenience, such as using a web wallet to pay your restaurant bill with your phone, or using an exchange or localbitcoins.com account, only send the minimum amount immediately required to use such a service, and not more than you can afford to lose.

This kind of problem is usually due to the image being located on some overloaded shared hosting provider.

There is a company that is mostly under the radar, that has acquired many domain and web hosting companies and moved their customers to unresponsive crappy overloaded servers that often don't respond for many seconds: http://en.wikipedia.org/wiki/Endurance_International_Group

You get another 14 every two weeks.

"How does search actually work"

If your php can write a bitcoin address, it can make a URI in HTML.

Someone is upset at your use of apostrophe to make plural?

Anything goes on testnet - it is very cheap with the new bitcoin relay rules to spam testnet tx, for better or worse. If you can break testnet with tx spam, then it is a canary-in-the-mine for Bitcoin, so you might watch the way that Bitcoin becomes harder to use under such load and make your own bug reports if you can quantify.

http://we.lovebitco.in/paperwal.py

Has two functions o_b58():with bitcoin address checksum and b58encode():non checksum. You can use it as an import library. Since it makes a bitcoin address, everything library-wise that you need to make a paper wallet is obviously included.

https://bitcointalk.org/index.php?topic=361092.0

If Bitcoin didn't exist, Bitcoin wouldn't exist. It is the single piece of software powering the network, miners run Bitcoin, merchants run Bitcoin, and Multibit connects to someone running Bitcoin.

That is like asking why anyone would prefer hamburgers over mustard.

The reason this is annoying is that besides being re-asked here multiple times, the question is in the FAQ.

If you run it from a command prompt so the window doesn't close when a program exits, you will be able to see what the problem is. The program used to beat down the door waiting for good data (because there was 500MB+ to download off the API server, it had to tolerate web errors), but now it's kind of written so if it doesn't get what it needs from the 5-day history server, it just gives you the error.

Oh, and there's no trade gap bug like I previously mentioned might exist - I forgot that I previously deleted all my SierraChart/data cleaning up the hard drive and misinterpreted when I ran sierrachartfeed again.

Compressed public keys were not introduced until Bitcoin 0.6.0, released March 31 2012, and only addresses created by a new install would be compressed; the keypool would still be uncompressed.

You say "my computer wasn't very powerful". You would not have mined 25 BTC in a few weeks in 2012. This would require spending serious money on many GPU mining rigs specifically set up for Bitcoin. At the minimum 2012 difficulty of 1.4M, even a $300 ATI GPU selected specifically for mining use would make you less than 1BTC a week.