The difficulty of a share is 1. It takes ~2^32 hashes on average to find a share.

How many shares per day at 3.2Ghash/s:
2^-32 shares/hash * 3.2*10^9 hash/sec * 86400 sec/day = 64372.0 shares/day

How many BTC per day at difficulty 1379647:
64372 shares/day * (1/1379647) blocks/share * 50.0 BTC/block = 2.3329 BTC/day

(all calculations done with more precision than I've shown.)

I'm starting to think I've already answered every question that can be asked...https://bitcointalk.org/index.php?topic=21541.msg272356#msg272356 (and interesting that the difficulty is the same as it was back in June).

...and you wouldn't need manager approval to eat your Kobe Beef Filet Mignon in a McDonalds?

Notable to mention since it hasn't been yet: consider one of the files that could have been copied to be the password file, a la mtgox hack. I would suggest all users regard their credentials used on the pool as out in the open to hackers, and change the pool account password and workers or make a new account. Additionally make sure that any other assets using the same password, username, email, etc, get burned or at least the password changed. Just a note, I have little worry, because my unique username and password for the pool are long with random generated characters like UA12mj(\)#yB#Cl0Z)Uz{&5pz_, and the email a non-reversible disposable email address, do this everywhere and you are pretty safe.

Pool's going strong, last block found in 10 hours. 2356 Accepted/6 Rejected with no hiccups or waiting for work (yes, you, btcg).

Bitcoin is their competition. Bitcoin is better. Duh.

Funny, that's exactly what I do. Put down that $300 on 13, and you have a 1 in 37 chance of leaving with $10,800. Bet $5 over and over again until you either lose all your money or you get above $10,800, your odds are far higher that you lose all your money. Plus it's a big waste of your time with little entertainment value.

Trixx has registry entries for storing it's values. Manually setting them in the registry to what you want will "unlock" a range in the GUI that wasn't previously available.

Search the registry for ID_OC_MEM_SLIDER, ID_OC_VOLTAGE_SLIDER, and you will see these are set to the saved values in Trixx. Close Trixx, change the OC_MEM_SLIDER reg_dword to 150 decimal, and restart Trixx. You can now use a lower range of settings. Repeat for anything else you want to change.

4 hours. Yesterday. That was using my local network and a decent desktop computer with a SSD to process the incoming blocks, so that is about the minimum time required now. If you have an older laptop on non port-forwarded wi-fi, it is of course going to take longer.

Sending bitcoins is nearly free and instant. Getting the bitcoins to send is the harder part, either buy them on a currency exchange, sell goods or service for bitcoins (like you are doing), or mine them. The forum has lots of posts about all these subjects, or you can start at the http://bitcoin.it wiki.

Bitcoin is it's own currency, not primarily a means of transferring other currencies. Many here have savings in Bitcoins, as it is both speculative and a hedge against government currency inflation. Plus you can buy stuff with them.

Reading between the lines, it is getting an advance RMA using someone else's serial number (likely gleaned from shelf surfing a retail store). When they don't receive back the old Kindle, your credit card will be charged.

Not a good rule. I did a SI shit ton of benchmarking every 10MHz (and 5MHz around the peak) on SDK 2.5 (worksize 256). On a 5770 at 950MHz, the performance peak was at 295MHz RAM; at 800MHz it was around 260MHz. On a 5830 at 1050MHz peak performance was obtained at 375MHz-390MHz RAM; at 800MHz, it was still around 360MHz. There is probably a better formula that involves number of stream processors and memory bus width vs worksize and vector size, but benchmarking your particular configuration is ideal.

Of course this topic is about SDK 2.6, where any memory clock other than ~1000Mhz will hurt your hashrate.

deepceleron's razor applies to mac...here's the result of two minutes of googling:

Find BitCoin.app. Usually, this will be in /Applications.

Open up Terminal.app (find it via Spotlight, or in /Applications/Utilities), and type:

cd <bitcoin's containing folder>/BitCoin.app/Contents/MacOS
./bitcoin -rescan &

And be sure to include the "&", or you can't use your Terminal window for anything else! Though that's up to you - you can always open another.

Just being around 160000 blocks, isn't enough, Bitcoin must have downloaded past the block number where you were sent money (as shown in blockexplorer for your address).

That sounds like a bugfix that was put in 0.6, IIRC. I might have to bust out zee code and see how it works, though it may be a lot longer for me to understand it than for the person who wrote it to tell me.

You need to add a command line option at the command line. On windows, open "command prompt" under accessories.

Here is a typical command line session for 32 bit windows (blue is what you type):

C:\Users\user1>cd \

C:\>cd "Program Files"

C:\Program Files>cd Bitcoin

C:\Program Files\Bitcoin>bitcoin-qt -rescan

Then Bitcoin will start with the wallet splash screen displaying "rescanning..." for a minute or two.

The block count shouldn't be ~16000, more like 166,000 blocks.

ECS was also known as PC-Chips, UMC, etc. They are a bottom tier outfit that has previously put fake cache chips on motherboards, made counterfeit chipsets, and sold motherboard/CPU combos and altered the bios to report a different CPU or cache size (and those are just ones I have had personal experience with). Typical Chinese ethics.

I'm running additional Bitcoin installs, and am having them connect only to my main Bitcoin that is on the net with the bitcoin.conf option:

connect=192.168.1.xx:8333

Bitcoin doesn't seem to be able to determine the current blockchain height/block number though, it looks like it is just using the checkpoint in the code.
After it passes block 140700, the progress bar completely disappears, even though it is still downloading blocks.

How does Bitcoin determine the current block, and why can't it get it from my local node running 0.5.2?

Verified in 0.5.2 and 0.6rc1.

---

Unrelated: It's now four hours for a core 2 quad to process the blockchain off a local connection, and it really starts bogging down around block 120000... I wonder if the biggest part of this isn't the database indexing.

I also realized that we have added 200MB to the blockchain in two months, the blk0001.dat is now about 1GB. At 2GB it may start causing problems for some users, but at 4GB, real big problems, as that is the file size limit for FAT32 systems. Time to start planning for multiple databases for storing the blockchain before this happens.

---

Another line so the above doesn't look like a sig...

This topic is only 10 posts down from yours on the newbie forum, and explains manual blockchain download.

There is no "retrieving" of bitcoins needed. If bitcoins have been sent to your Bitcoin address, they are yours, and the whole network knows they are yours. You can look up your address using search at http://blockexplorer.com and see your balance. However, the Bitcoin client won't let you send money from your balance to someone else until it knows about it, which means it will need to download all blocks up to the one where money was sent to you.

Bumpity. The forum on sourceforge was announced by sirius:

From: <mmalmi@cc...> - 2009-06-13 06:41

The new Bitcoin website/portal is up at bitcoin.sourceforge.net. 
Forums and a wiki are included, so you're welcome to join discussion 
and wiki documentation.

Martti Malmi
Bitcoin Web Developer


then

Satoshi - November 22, 2009, 10:04:28 AM
Welcome to the new Bitcoin forum!

The old forum can still be reached here:
http://bitcoin.sourceforge.net/boards/index.php

So there's about five months of forum posts on sourceforge that went poof at some point before the Internet Archive found it and first spidered it in July 2010.

This is a misconception. PPLNS does not require full-time mining, nor does it punish part-time miners (nor unfairly reward part-time pool hoppers). If you submit a share now, it will pay you a reward of (50/N) BTC for any block that is found during the next N shares on the pool. You can keep on mining or you can quit, it doesn't affect what that submitted work will earn you. If your hashrate's expected reward for 24 hours of mining is 2BTC, your expected reward for 12 hours of mining would be 1BTC, regardless of when or how you part-time mine.

PPLNS does have a lottery-like aspect similar to solo mining, but it is significantly more favorable because you are part of the pool's high hashrate, and your work continues to count even after you quit. If solo mining with an expected 2BTC/day hashrate, you might earn 0 BTC in a month of mining, or you might find three lucky blocks worth 150BTC. If you mine on a PPLNS pool for an hour, you might get 0 reward if the pool is unlucky, or you might share several block finds, and earn significantly more than expected for your work. Proportional has the same situation, miners suffer lower earnings if the pool is unlucky. However even the modest part-time miner will quickly see they are getting their expected earnings over time with PPLNS.

Proportional also has the "OMFG, when are we going to solve this ridiculous long block? I'm gonna quit" factor. PPLNS is much more optimistic, you start submitting work and wait for the block finds to roll in, you aren't overly invested in unlucky blocks, and nobody is punished for starting mining in the middle of a round.

Logic error pointed out.