|
FWIW, here are our shares and payouts while we were on the pool. This is with about 270-290TH and BAN always reported within 5% of our hashrate.
+-------------+--------------------+
| sum(shares) | sum(btc) |
+-------------+--------------------+
| 19440313760 | 15.39314937 |
+-------------+--------------------+
At the standard PPS rate (without the claimed bonus) we should have made about 17.8 BTC. With the bonus we should have made ~20 BTC.
So we are currently owed about 2.4 BTC at the standard PPS rate ignoring the bonus.
Let me know when you get things worked out and we'll be back.
|
|
|
|
Seems like payouts are still around 15% short, not including the bonus.. Will these be fixed soon?
You just have bad luck with Bitcoin pools, don't you? Maybe you should just make your own Bitcoin pool. You've got a pretty big user base as it is, I bet you could do it. It's not really an issue of luck and yes I just might do that. All jokes and jabs aside, it would more than likely solve a lot of the problems you run in to since you would control the backend etc. Yes, the issue is at only 250-300TH we'd have an unacceptable amount of variance. |
|
|
|
Seems like payouts are still around 15% short, not including the bonus.. Will these be fixed soon?
You just have bad luck with Bitcoin pools, don't you? Maybe you should just make your own Bitcoin pool. You've got a pretty big user base as it is, I bet you could do it. It's not really an issue of luck and yes I just might do that. |
|
|
|
|
Seems like payouts are still around 15% short, not including the bonus.. Will these be fixed soon?
|
|
|
|
|
I own/operate Multipool.us. If someone from GAW miners can give me your username(s) on the pool, I can verify your hashrate. Or, you can set up a "handle" via the account page and it will appear rather than your User ID under the top hashrates for each coin (assuming you are within the top 15, which should be easily within your capabilities.)
For the record, I have not been contacted (to my knowledge) by anyone at GAW miners about setting up an account, IP whitelisting what would most likely be a massive number of workers, etc.
|
|
|
|
Is merge-mining on DOGE already implemeted? Thanks.
No, it's not available for anyone yet, it's only on testnet right now. We're doing everything we can to have it ready by the time the new client release comes out in a few weeks. |
|
|
|
So is it confirmed that the tainted code was only in recent builds? If so, how long ago did it happen?
According to LiteSaber, the tainted code was in the most recent binaries which were linked from another site (minersforwindows.com) |
|
|
|
|
I have the domain now. I will be downing the site until the new binaries are available with an explanation of what happened.
|
|
|
|
Sorry guys, just saw messages someone sent me on IRC.
I've gone ahead and removed the download links from sgminerwindows right away.
Previously I compiled all versions myself and these were 100% clean i guarantee. But the last update was done away from my computer (on a family vacation) using pre-compiled binaries from minersforwindows.com because I was getting heaps of messages from people to update with the latest beta version.
Stupid move on my part it seems. That'll teach me for being lazy and not just installing what i needed to compile onto my laptop.
In the spirit of keeping the site going (in the right hands) If there is a known trustworthy person here that would like to take over the website from this point on, I will happily give you the website's files and push the domain to you free of charge (you will need a namesilo.com account).
It's already ranking #1 in google for many sgminer terms so I would rather not see the site go to waste. But I just do not have the time to keep it updated.
Also, if you don't believe me. Go and check out minersforwindows.com and scan their versions. They do many more versions that i never added to my site thankfully. They also do other mining software.
Sent you a PM, I'm willing to take this over. |
|
|
|
How's that saying go, damn if you do; damned if you don't. It appears that the larger p2pool gets the worse it is for smaller miners....quite the dilemma since it needs to keep getting bigger to stay relevant.
It would be great if someone could take p2pool over and make it perform better and address the issues. I would move Multipool's ~250TH back to BTC p2pool in a heartbeat if it could handle the load. |
|
|
|
The guy who built these binaries is: http://www.reddit.com/user/LiteSaberAccording to his post history he also runs VertSquad.com and CoinHuntr.com. It's also possible the site could have been compromised by someone else who uploaded the trojaned binaries. |
|
|
|
|
Multipool has removed the link to this site as well. Pretty sad that something that was originally legit is now being used to scam people.
|
|
|
|
|
Can we get an update from devs? Is this coin being fixed or is it done?
|
|
|
|
|
Karma would be a great choice, I agree.
|
|
|
|
|
The explorer seems to have issues displaying transactions. This is a problem for me as I continually get email from users who think their transactions are not in the blockchain when in fact they are.
Can whoever is in charge of the block explorer look into this please?
|
|
|
|
|
Multipool's Karma port (3376) is running X11 fine, we found the first few blocks after 255k.
|
|
|
|
|
After upgrading, my wallets were in sync with the block explorer and then forked again overnight. Now when I delete the blockchain and resync they do not match the explorer.
There are obviously several forks on the new chain.
Please add a checkpoint ASAP.
|
|
|
|
just advertise your pool in your sig, like every other adv
Yep!  Just because a pool is advertised in someone's sig doesn't mean they support a particular coin. In my case, should I list all 50 coins I support in my sig? That would get obnoxious fast. |
|
|
|
Multipool updated last night, resynced and was synced to the same block as the explorer. Now we're 400 blocks behind and the client will not sync past that.
Please advise.
The solution is to delete blocks (everything in the folder except wallet.dat and execoin.conf) and resync (using list of nodes - for example or if without it will get a list from seeders). Please update ASAP Your DNS seed is obviously still advertising nodes on the wrong fork. You need to add a checkpoint to the code so that nodes will only connect to the proper fork. |
|
|
|
|
Show Posts
