The pool is 125BTC behind in payments and it keeps getting worse.
And it reports 4PH/s... payouts get further and further behind, yet people continue to mine on the pool. Unreal. |
|
|
|
I've made a little program in python to check my stats without reloading the page, you can download it here: https://github.com/yqons/solo-mining-statsCheck your solo mining stats on solo.ckpool.org, and check every 10 minute if you have found the jackpot aka block To run: Enter you address inside addr.txt file (on the first line)
pip install datetime requests dateutil.relativedelta colorama
python check.py  Tips: 1GrC12hbtMNPiYumftZ4B3Y1MVyCuZrKeM Sorry for the English btw Checked out your code... it'll ping jackpot every 10 minutes if you happen to have more than 20 BTC in your address. Might want to consider another way to notify people if they've actually hit the block, since just checking the balance of an address is no indicator that the user found a block. |
|
|
|
roy7 - take a look at what OgNasty and Nonnakip have done with their NastyPoP implementation. You can see my long-running thread about it here: https://bitcointalk.org/index.php?topic=891298.0. Windpath - coincadence.com is not showing block 351173. Are you still adding blocks that come from orphaned/dead shares to the site manually? OgNasty/Nonnakip - same thing on the NastyPoP distribution window standings page at nastyfans.org/miners. 351173 is missing. |
|
|
|
Antminer U2 won't work with scrypt - only sha256d. You're trying to mine the wrong algorithm  stratum+tcp://us-west.multipool.us:9999 is the one you want. |
|
|
|
I'm in the process of setting up my first miningrig. Hardware is done, software and accounts are almost done. As some howto's state, i'd like to set the mining pools of multiple coins to deposit my share directly to a coin exchange, as this enables an autosell option.
I've registered at BTC-e, VirCurEx and Cryptsy. However, when i generate an address, every exchange seems to say direct mining to the exchange is not supported. Could someone clairify this for me? Some direct quotes are provided underneath:
BTC-E:
"We do not support generated transactions from pools like Eligius, P2Pool etc."
VirCurEx:
"Usage of addresses
DO NOT use Vircurex addresses for mining purposes. We cannot credit coins generated (instead of being sent)."
Cryptsy:
"Notice: Do NOT mine directly directly to your Cryptsy deposit address."
They mean they cannot accept newly generated coins directly. For example, when you mine on p2pool, the coinbase transaction that generates the new coins from the block reward pays your address directly with a portion of those new 25 BTC. Most exchanges don't like this - their APIs can't handle it. Other pools (like kano, BTC Guild, etc) wait until the coins have confirmed and pay you then. These types of payments are something the exchanges can accept. Basically: If you are getting newly generated coins directly as part of the block reward for your coin, exchanges will not work. |
|
|
|
Good luck finding a USB miner that will not only satisfy these power requirements, but also be open source hardware and software. Even if you do find such a device, (I'm thinking the Antminer U2 would at least satisfy some of your needs, but I suggest you check out https://bitcointalk.org/index.php?topic=464496.0) you're going to make next to nothing running such a miner. Right now, a U2 clocked to run 1.8GH/s will earn you 0.0001282 BTC a week. You really don't meet requirement #4 until you solve a block. With that U2 miner, and today's difficulty, you're looking at ~4 thousand years until you contribute to the security of the blockchain by solving a block. Mine for fun, if you wish. However, If you want to contribute to the security of the network-- run a full node. Not necessarily true... Your argument would imply that the only miners out there that are contributing are those who actually provide a valid block solution. If that's the criteria for contribution of a miner, then even though I've been mining for over a year, my single contribution was April 26, 2014 and block 297777. Of course, I run my own full client since I run my own p2pool node, so I fit into your definition of contributing that way. My counterpoint would be that every miner who is actively connected either to a pool or running solo is contributing. Without miners trying to solve that elusive hash, the entire system would die out. |
|
|
|
|
Please provide more information like what mining software you're using, what coin you're trying to mine, are you mining solo or to a pool, linux version, driver version, etc.
Just telling us you think you card should hash faster doesn't give us anything to go on. I'd say you're probably not using the card at all, but rather are CPU mining...
|
|
|
|
Holy smoke - seems it was one of my old S3's that found that last block! Outstanding  Glad you decided to point them here, then |
|
|
|
Based on your requirements you've limited yourself to USB miners, since you stated there can be no external power source dedicated to the miner. Further, since you're reliant upon no external active power supply, your miner must be powered completely by the USB port. This means you're limited to 2.5V and 1.8A at maximum power. Unfortunately, your MBP will only push 500mA at 5V, further limiting you to a total power output of 2.5W. Good luck finding a USB miner that will not only satisfy these power requirements, but also be open source hardware and software. Even if you do find such a device, (I'm thinking the Antminer U2 would at least satisfy some of your needs, but I suggest you check out https://bitcointalk.org/index.php?topic=464496.0) you're going to make next to nothing running such a miner. Right now, a U2 clocked to run 1.8GH/s will earn you 0.0001282 BTC a week. |
|
|
|
tnx a lot
how to Repair this Problem ?
i use normal application software mining (for example cpuminer) , why ?
Try putting "listen=1" in your bitcoin.conf |
|
|
|
When it starts taking you longer to find a share than it does for the pool to find a block you perceive your mining to be "wasted" because blocks will be found for which you receive no payment. I've not been active in the bitcoin community for a long time now, just randomly popped in the thread to see what's up, and I see this is still a topic of conversation. It's important to note (as you did) it is simply perception/variance, and people don't actually lose any income. If you can only find 1 share every 2 blocks, that share will pay enough that the income per block is still the correct average. This was a common point of confusion and misinformation a year ago. I suspect it will persist forever. Welcome back... haven't seen you for a while . You're right, not a whole lot has changed. There's still excitement when we find blocks, disappointment when we don't and the rest of the time is spent discussing the same topics: variance and its effect on miners, how to address the problem of variance with "small" miners, if anyone has a solution to the scaling problem... Pool hash rate has gone up to 4PH/s and down as low as 800TH/s. Share difficulty has run the gamut as well. Windpath has done some really nice work and his site has become the de-facto goto for p2pool-related stats. |
|
|
|
importprivkey "your_private_key" "Some_Descriptive_Label_Optional_Here" true
You will need to do it for each of the private keys you exported from your MB wallets. I have tons of private key i can't do it separately . Then write a script for it. The keys are all exported to a file called multibit.key. Parse that file for each key and pass it to bitcoin-cli using the same command I shared above (except put "false" instead of true so you don't rescan every key). |
|
|
|
  Http is oky (in chrome browser by default not show http:// ) port is oky user is oky pass is oky ...... is okyyyy --------------------------------- if incorect http protocol or port or user or password never see this page text. oky ? me error : {"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null} please Solve this ERROR code From rpcprotocol.h: It happens when the client cannot parse the RPC request being sent to it. |
|
|
|
|
Another week in the books. P2Pool itself was close to 100% luck, and the NastyPoP payouts were almost exactly expected earnings. My NastyP2P miner had a lucky streak and made more than expectations. Here are the numbers:
3/27 - 4/3
NastyPoP - 0.03301631BTC
NastyP2P - 0.05550941BTC
Expected - 0.0332BTC
Luck - 97.55%
OP updated
|
|
|
|
Notice a pattern? My measly 6.9TH/s (6xS5) is now a small miner. Top is shares, and bottom is pool hashrate, over a 14 hour period. I'm sure people can pick this apart, debate luck and statistics, etc... I just thought a good screenshot, somewhat makes a point. http://s25.postimg.org/iikptg4i7/SNAG_1426.pngI guess I'm confused by what point you're trying to make. If you're trying to compare shares found to hash rate, the only noticeable spike in your hash rate graph happens for a couple hour period. There is plenty of other time where the hash rate is relatively constant that you're not finding shares. We all recognize that as the pool's hash rate goes up, so to does the difficulty of getting a share onto the chain, which statistically means you find fewer. However, it also statistically means the pool itself finds blocks more often. Let's say you've got your 6.9TH/s and the share difficulty is 6.5M. Statistically you expect to find a share about every 1.1 hours or so. Assuming each red spike represents one share, you found 9 shares in 12 hours, so you're a bit lower than expectations. Also, you can clearly see the distribution of found shares is nowhere near the "one an hour" expectations, but rather is clumped together. This is exactly what I've been saying for months now - p2pool just can't scale properly with the increased hash rate, the more the hash rate - the worse the problem. I only point a few old S3's at p2pool now, & then only when the hash is below 2PH - any more than that & it's wasted. It's such a shame, really Remember last year (August) when share difficulty topped 10M for the first time? Remember when it topped 20M a few times shortly thereafter? That's what squeezes the smaller miners out. Seeing a statistic that says it'll take you a day or more to find a share... and then hoping your share actually gets accepted and not orphaned. Basically, as long as your expected time to share is less than the pool's expected time to block you're OK. When it starts taking you longer to find a share than it does for the pool to find a block you perceive your mining to be "wasted" because blocks will be found for which you receive no payment. |
|
|
|
ensure that your miners are submitting stale shares. Yes, bfgminer, for example, has the option "--submit-stale". The standard firmware on Ants for example discards them... Even though they may be valid solutions for a block. Why does "The standard firmware on Ants for example discards" stale shares? Um, because Bitmain's fork of cgminer is terrible. That's why kano and ck wrote their own binaries for a bunch of different Antminer models. |
|
|
|
|
Yes there is a very nicely detailed explanation of shifts earlier in this thread. To simplify it for you a shift is a less granular look at your contributed hash rate than tracking every submitted share. Makes it easier on the pool to track shifts instead of shares.
Renting for profit is tough to pull off. Phil got lucky. He got hashing power at a very nice rate and the pool found more blocks than expected. You can also get burned playing this game. For example, a few months ago I rented a large amount of hash. Unfortunately the pool on which I was mining suffered some horrific luck and I lost a lot of coin.
|
|
|
|
Trust no-one ... use P2Pool. Easy. Wow, thank you for bringing P2Pool to my attention. I'd never heard of it before, but it's an ingenious idea. What do you mean: Just remember to setup a good p2pool mining setup as good as the best ones on p2pool.
Otherwise the other miners on p2pool with a better setup are taking some of your BTC ... ? Kano means that you need to setup your node and ensure it has decent hardware... Is connected to other widely connected nodes... Is ideally on the same network as your mining hardware... You want to ensure that you get as few dead/orphan shares as possible and that you have a low DOA rate. The better connected you are the better your chances of being successful in submitting viable shares and reaping the full rewards when a block is found. Also ensure that your miners are submitting stale shares. The standard firmware on Ants for example discards them... Even though they may be valid solutions for a block. |
|
|
|
Must be getting old I forgot that I posted that. LOL What's with the picture ? They'll cut through a tree and still slice a tomato! https://youtu.be/QUarASqrVnY |
|
|
|
|
Show Posts
