|
Problem: it's still breaking up the signature itself. Never mind, fixed. Try again.
|
|
|
|
|
Thanks for figuring out the problem! I was about to post it myself.
I'll have to edit my auto-response to include line breaks for long lines.
|
|
|
|
|
I just noticed something: If you're paying $0.15/kWh or less for electricity, mining with a very high-end CPU, such as a Phenom 2 X6, is actually marginally profitable at the moment. This even with the recent drop in value and fast rise in difficulty, which implies that it was more-than-marginally profitable a week ago. (This only applies if you already own the CPU, of course.)
|
|
|
|
Here's the idea: - Post your public key fingerprint here.
- Offer some solid evidence that you own that key. (You can decide what constitutes solid evidence. Or, more accurately, your audience can.)
- We all collect and sign one another's keys, provided we're convinced of their identity.
For example, I just posted the following message in another thread. -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I am the real Ian Maxwell with public key fingerprint BFBC8D95. My key is only self-signed, but you can verify it by doing the following:
- - - Send an email to ian.maxwell@gmail.com with subject line "BFBC8D95" and body text "bitcoin".
- - - I will respond with a signed message referencing this one.
If you do verify my identity, I ask that you sign my public key afterward.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
iQIVAwUBTdfdNnO2hWa/vI2VAQJ29BAA5sIRG6i+yrZ9XSGejecHD8bKORebLLfR
4iynImjzs2ecYU6g0E5K3gLZlOnVZmnpRlhaTHgsKl/by55XA7uJq9ITXuurrRQN
2J+J280zbmA+QtbE8ulENfRbmPkPfEmwJEZedLg70rsdHFbt54bUFnlB2pViflRA
wDFBB+o8jB4sc1mRPtxpRfGDMARaGBzXV+xI/NYTUfzpvmfhNeErfPzCqeLttnTo
QCI9y1+vBHnzsyFKi9DMwrMi0C1fy82RVzG0s0/VLqZa4oDcJbJXm/IucAYW64Kz
QbT/3eJ/d7PWhwcWTCefDA96/zT3HT+TyNMdrMoumRcpB6MKT3Sv41xMXsgP1nb4
u/CGZ6NR+lwbPV4GMLahMIM5W41XWD67LlHetPKXlHSjO0VAUmvYiF22nSErQMj1
B6Dq0RQ/8bpqK/WLXOBP/pEMQSC1ZquqDKs72DT8tQkYQmNiMOoC4A+7CcqNyFxz
JFW70Bjmq1fABKLfVs7Au4gu2AJFOofv5u751hMIS2+aumaaRvsxU8f3VGBweaRh
SZFiBk52SGJWVkooYqUSgZXZTphdgmUg3PUSswLrHtJtwuF7H0IkMfStzeejkSys
XFPUZ3YCQc7/Kw3yxSDpLAn2Y4DNSvbcwZFjZN+ZahGMmuli09zORw869Lp7PQ5j
RVTFPiPiUQE=
=o3wJ
-----END PGP SIGNATURE-----
Note: although I'm revealing my offline identity, this is not required! You can use a pseudonymous key if you like, as long as you can prove it's yours. Signing a message with it may be enough. |
|
|
|
If people doubt you're who you say you are, this is what you can do about it: -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I am the real Ian Maxwell with public key fingerprint BFBC8D95. My key is only self-signed, but you can verify it by doing the following:
- - - Send an email to ian.maxwell@gmail.com with subject line "BFBC8D95" and body text "bitcoin".
- - - I will respond with a signed message referencing this one.
If you do verify my identity, I ask that you sign my public key afterward.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
iQIVAwUBTdfdNnO2hWa/vI2VAQJ29BAA5sIRG6i+yrZ9XSGejecHD8bKORebLLfR
4iynImjzs2ecYU6g0E5K3gLZlOnVZmnpRlhaTHgsKl/by55XA7uJq9ITXuurrRQN
2J+J280zbmA+QtbE8ulENfRbmPkPfEmwJEZedLg70rsdHFbt54bUFnlB2pViflRA
wDFBB+o8jB4sc1mRPtxpRfGDMARaGBzXV+xI/NYTUfzpvmfhNeErfPzCqeLttnTo
QCI9y1+vBHnzsyFKi9DMwrMi0C1fy82RVzG0s0/VLqZa4oDcJbJXm/IucAYW64Kz
QbT/3eJ/d7PWhwcWTCefDA96/zT3HT+TyNMdrMoumRcpB6MKT3Sv41xMXsgP1nb4
u/CGZ6NR+lwbPV4GMLahMIM5W41XWD67LlHetPKXlHSjO0VAUmvYiF22nSErQMj1
B6Dq0RQ/8bpqK/WLXOBP/pEMQSC1ZquqDKs72DT8tQkYQmNiMOoC4A+7CcqNyFxz
JFW70Bjmq1fABKLfVs7Au4gu2AJFOofv5u751hMIS2+aumaaRvsxU8f3VGBweaRh
SZFiBk52SGJWVkooYqUSgZXZTphdgmUg3PUSswLrHtJtwuF7H0IkMfStzeejkSys
XFPUZ3YCQc7/Kw3yxSDpLAn2Y4DNSvbcwZFjZN+ZahGMmuli09zORw869Lp7PQ5j
RVTFPiPiUQE=
=o3wJ
-----END PGP SIGNATURE-----
|
|
|
|
|
Fortunately it's easy for him to show otherwise, provided that he has a well-known public key.
|
|
|
|
|
I've pointed one GPU core at your pool. What kind of hashrate do you have so far? I'd like to have an idea of the variance I'm looking at.
|
|
|
|
Please can you tell step by step.
I have already registered with a name & password in slush pool. I also created workers there & gave bitcoin address & mining & getting coins.
Now according to the method you saying, where & what changes i have to do exactly. If you give step by step, it will be useful. Coz, programming is headache to me.
In bitcoin.conf
what rpc user, password, ip or url , address have to make it work?
You've misunderstood. This is a suggested protocol for future mining pools. It's not something you can do with existing pools. |
|
|
|
|
Yes, there is a maximum possible difficulty as things stand now. It's exactly 26,959,535,291,011,309,493,156,476,344,723,991,336,010,898,738,574,164,086,137,773,096,960.
I would like to live in the world where this is a problem.
Edited to add: Raising the difficulty doesn't mean specifically that the target has more leading zeros, only that the target is a smaller number. If the difficulty increases by something small like 5%, no more leading zeros will probably be required.
|
|
|
|
|
I think we were talking about the time to get to difficulty 1 from "difficulty" 1/maxtarget.
Answer: 112 retargets, or 225792 blocks, or 11289600 bitcoins generated.
I guess I can see the reason for a maxtarget. Though I do kind of wish the convention were to call the minimum difficulty "4.295 Ghash/block" rather than "1".
|
|
|
|
|
So if someone wanted to serve their own bitcoins, would they have to run separate client and server software? Or would the client software still be able to work independently?
|
|
|
|
Well, it's not exactly a calculator, but maybe this is useful. All the numbers scale nicely: that is, if you want to look at the 1M-10M difficulty range just multiply all the magic numbers by 10, or if you want to look at exchange rates in the 10-100 range just divide them all by 10. Break-even magic numbers by difficulty and exchange rate (assumes 50 BTC/block)
EXCHANGE RATE
1.00 2.00 3.00 4.00 5.00 6.00 7.00 8.00 9.00 10.00
+---------------------------------------------------------------------
D 100000 | 2000 1000 667 500 400 333 286 250 222 200
I 200000 | 4000 2000 1333 1000 800 667 571 500 444 400
F 300000 | 6000 3000 2000 1500 1200 1000 857 750 667 600
F 400000 | 8000 4000 2667 2000 1600 1333 1143 1000 889 800
I 500000 | 10000 5000 3333 2500 2000 1667 1429 1250 1111 1000
C 600000 | 12000 6000 4000 3000 2400 2000 1714 1500 1333 1200
U 700000 | 14000 7000 4667 3500 2800 2333 2000 1750 1556 1400
L 800000 | 16000 8000 5333 4000 3200 2667 2286 2000 1778 1600
T 900000 | 18000 9000 6000 4500 3600 3000 2571 2250 2000 1800
Y 1000000 | 20000 10000 6667 5000 4000 3333 2857 2500 2222 2000
|
|
|
|
|
@Dusty: When you're mining, you're trying to find a 256-bit hash that is less than or equal to a certain value, the 'target'. The maximum target is hardcoded into the client as 0x00000000ffff0000000000000000000000000000000000000000000000000000, and the difficulty is actually maxTarget / currentTarget.
A 'share' is a hash that is less than or equal to maxTarget. It's not actually useful to the pool, except as proof that you're really working. They're also useful for calculations: at difficulty 244139.48158254, you should find that the pool generates blocks at an average rate of one per 244139.48158254 shares submitted.
|
|
|
|
|
Ah.... sorry.
They didn't really answer the question, though.
|
|
|
|
|
A problem with ฿ is that eventually we'll need our own Unicode character anyway, because Unicode is "semantic" in that symbols have a fixed meaning. This is okay for $ because it always means "dollar", it's just what sort of dollar that changes. Bitcoins are not our own local variant of bhat.
That said, I'm calling ฿ the best stopgap solution, and using it for now.
Should it go on the left or the right?
|
|
|
|
|
Or more accurately, why isn't the maximum target 2^256 - 1? The issue of excessively fast block generation would have resolved itself within less than a second after the first client was run. Or the initial difficulty could have just been set to 1,000,000,000.
The scaled-down shares-per-block difficulty may be easier on the eyes, but its interpretation is kind of opaque. Quoting difficulty in Ghash/block at least means something.
|
|
|
|
The current difficulty value for GBP (based off Britcoin ask rates) 244139 / (£3.85 * 50 BTC) = 1268.25 (shouldn't this be Shares/GBP?).
Absolutely right! A share is just a hash that would be valid at difficulty 1. I've edited the post to use this terminology. |
|
|
|
|
When calculating the electricity cost, don't forget: everything that uses power, that wouldn't use power otherwise, is a mining cost. If my machine weren't mining, it would be sleeping and wouldn't have a window fan pointed at it.
|
|
|
|
I'm in the same boat as OP. Looked into mining 2-3 months ago and decided it wasn't worth my time ATM. Now I'm kicking myself with the 1000% value increase in BTC.
If the exchange rate goes up doesn't that mean you should have just bought outright instead of mining? If you'd spent the money on a $1000 mining rig, you might have produced as much as 700 bitcoins by now. You'd have a pretty tidy profit---but at the time you could have bought about 1400 bitcoins with that money! |
|
|
|
Watching the difficulty go up, I realized I needed a way to quickly recognize when the day comes that mining is no longer profitable. So I worked out the following. Maybe someone else will find it useful. If you are a miner, your your "magic number" is M = (shares * hashes) / (power * cost), where - shares is the (constant) rate of "share" generation per hash, which is about 0.000233 shares/Mhash or 233 shares/Thash;
- hashes is your hashing rate versus time (say 780 Mhash/sec or 2.81 Thash/hr);
- power is your rate of energy consumption for mining (say 450W or 0.450kW); and
- cost is your cost of electricity (say 0.150 USD/kWh).
All of these numbers are relatively fixed, so go ahead and calculate your M now. Be sure you have the units straight---this "number" is actually denominated in shares per <fiat>. In fact, it has a specific meaning: it's the number of difficulty 1 shares you are generating per <fiat> spent on electricity. Using the data above, for example, my magic number is about 9700 shares/USD. The point of this exercise is that your mining is profitable on the margin if and only if M > diff / (xcg * reward), where diff and xcg are the current difficulty and exchange rate and reward is the block reward (50 BTC right now). So when difficulty increases and you're wondering whether to keep mining, or the exchange rate soars and you're wondering whether it's time to fire up the ol' CPU again, you now have an easy way of deciding. Just divide difficulty by exchange rate and reward, and compare it to your magic number. For example, right now we have a cutoff of (244139 shares/block) / (6.63 USD/BTC * 50 BTC/block) ≈ 735 shares/USD. Anyone whose magic number is lower than this shouldn't be mining. Fortunately, mine is still well above it! Unless the exchange rate tanks or the difficulty soars, I should still be in the game for at least a couple of months. |
|
|
|
|
Show Posts
