Hello, new member to your pool and am quite a fan so far. I dedicate my GPU to your Doge mining and one of my ASIC's to your SHA-256 multi mining. My question is this: Will you consider merged mining for NMC, DVC, & IXC when mining for bitcoins in your pool? For example: Multipool switches to BTC since that is currently most profitable at the time. You could enable all the merged mining coins to be mined alongside BTC when you're mining BTC. Also, the dedicated BTC miners on your pool would always have a chance at mining merged coin blocks if they aren't doing the multicoin mining. I understand that this is a little more work for a pool operator since stratum, but it is very possible. It may be something to consider. I'll tip you in Šoge if you do end up doing it. (Remind me in case I forget ) Yes there are plans for merged mining starting in January.
|
|
|
So whats going with doge pool? blocks are getting confirmed but no payout in them, everything ok flound?
Just a stuck script, all is well now.
|
|
|
Flound, your PXC pool pays half the reward to miners for over a month. When the last hard fork took place on the 16-Nov-2013 (block #154000), block reward increased from 25 to 50 PXC. You calculate it at 25 PXC still. The miners receive half their profit.
Well, shit.. No wonder nobody is mining PXC here. You're actually the first person to point this out. The problem's been fixed but I only have payout records going back 7 days now.. I will think about how I can compensate people.
|
|
|
Question, I must have something configured wrong. When pointing to the multiport 8888, all my USB block erupters go into a WAIT state and stay there if it's mining BTC. At least it worked fine while mining ZET and FRC. But when the pool switches to BTC, my block erupters stop hashing and bfgminer shows each one in a WAIT state. And another weird thing happens at this point, the CPU fan on my computer will crank up and get noisy.
My settings are as follows:
bfgminer.exe -o stratum+tcp://pool1.us.multipool.us:8888 -u xxx -p xxx -G -S all --icarus-options 115200:1:1 --icarus-timing 3.0=100 --api-listen --api-allow W:127.0.0.1
Thanks
It's due to the BTC port being a p2pool node. block erupters and P2pool don't play nice with each other because the erupters use an internal stratum proxy that has a known issue connecting to P2pool.
|
|
|
I don't think diamond is in right place (chain?).. block numbers not matching with where it should be.. might want to have a look. Others sites say blocks are at over 200k.. multipool says 157k.. oh never mind.. it looks like its still updating it jumped 4k in a few minutes.. guess its not synced yet.. funny you would open it before synced? Not sure what is going on...lol..
dmd was forked for a bit and a few blocks were orphaned. We're now back on the main chain.
|
|
|
Please add multipool.us to your pool list. Thanks.
|
|
|
Any word on the pool instability issues? The silence is deafening.
M
Do you mean the issues from the other day? They were resolved by upgrading the database. Our provider has also been stable since Sunday.
|
|
|
DOGE is now available on port 3352.
|
|
|
Is there another exchange that deals with the alt coins that we mine besides cryptsy?
Wouldn't mind getting away from them if there is a better one.
There aren't any exchanges with the same number of altcoins and the same volume that cryptsy has. That said, there are several others: vircurex.com coinex.pw bter.com coins-e.com coinedup.com btc-e.com
|
|
|
owch. [sarcasm] Using my elite knowledge of thermonuclearwargames I was able to extract the hidden data here https://www.multipool.us/stats.php?curr=ltc [/sarcasm] Avg. Time To Find Block 33 Hours 53 Minutes Time Since Last Block 42 Hours 47 Minutes ohw... ehmm... yes.. I see.. just no luck then.. I wouldn't mine anything other than the main scrypt port. Otherwise you're basically solo mining, and you don't have much power there for solo mining. M I think I now know what you mean... LTC stats: "Time Since Last Block 63 Hours 23 Minutes" We had really good luck on LTC for a while, finding about a block a day. This is the first dry spell in a while. In other news, Multipool has added DOGE on port 3352.
|
|
|
We're discussing moving the BTC port to a regular stratum instance but if we do that we're going to need a lot of support from miners to get the hashrate up to 30+TH so that we can average a block every 24H or so.
Thanks for the info flound. I was hoping to mine multi in SHA though. I was watching one of the "12 days of Bitcoin" reports and one of the anchors asked why use bitcoin. One of the answers was "it's a community". I've enjoyed Multipool for scrypt and would like to direct all my business to Multipool. To keep it "in the community" of Multipool. That's why I turn on my donation mining - I'd like to see Multipool stick around and I'm willing to do my part to see that happen. I also like the website, very tidy, pretty intuitive and easy to use. Overall has made my crypto experience a good one. While on the subject of ASICs and this pool, am I missing something? Should I keep looking for a solution to slow acceptance of work or will I find something different if I try mining SHA on Multipool again? We'll still be multimining. I'm just talking about whether the BTC port will point at p2pool or to our own stratum instance.
|
|
|
Hey gang trying to sort out what is going wrong for me. I was mining LTC but decided to switch to multipool. All I did was change the pool settings in my cgminer.conf file to multipool. It connects but my speed is less than half what I was getting in litecoinpool across my 4 cards. Anything I should be looking to change? Not sure why it would drop like that.
Post a screenshot of your miner and a copy of your config, or email me with them and we can try to help. Or join the #multipool channel on freenode IRC, there are a lot of tweakers in there most of the time nowadays.
|
|
|
Hey gang trying to sort out what is going wrong for me. I was mining LTC but decided to switch to multipool. All I did was change the pool settings in my cgminer.conf file to multipool. It connects but my speed is less than half what I was getting in litecoinpool across my 4 cards. Anything I should be looking to change? Not sure why it would drop like that.
The stated hashrate on the multipool website swings wildly all over the place. It seems to have a hard time showing anything close to real time hash rate. As long as the average hashrate is about normal, and your payout is about normal, I wouldn't be concerned. M This should be mostly fixed.. It had to do with me changing a db query and not updating the hashrate calculation to match it. Hashrates should be a bit more stable now (or at least after we've been on a coin for 10+ minutes)
|
|
|
I'd love to support this effort, but bfgminer and cgminer both accept work reeeallly slowly. I'm only a couple of months into mining, and the learning curve is pretty steep. I've been all over the forums and the mention of p2pool and asics/block erupters not getting along is the only reason I have come across that might explain this behavior. Btcguild mines quite consistently with my setup, switching to Multipool slows it all down. I've been forced to use Tompool, which also mines quite consistently. I love multipool for scrypt work though, very smooth.
I have 10 sapphire block erupters, and am using Minepeon with bfgminer.
If I could overcome this hurdle I'd switch over in a minute.
As far as I can tell the blades are very similar to the sapphires, using similar chips, is that true?
We're discussing moving the BTC port to a regular stratum instance but if we do that we're going to need a lot of support from miners to get the hashrate up to 30+TH so that we can average a block every 24H or so.
|
|
|
Does this exchange have an API?
|
|
|
Everything should be back to normal now (pool-wise) and I've resolved the performance issue that was making the site run slowly.
|
|
|
I am getting a lot user banned messages, causing cgminer to failover to a different pool. Is there something I need to change? I have two workers, each coming from a separate but stable IP (not static but hasn't changed in months).
the only way to get banned is by submitting lots of invalid shares or continually trying to authenticate using a worker name that doesn't exist. [2013-12-10 23:33:34] pool 3 JSON stratum auth failed: [ -2, "Worker temporarily banned. Try back in 60 seconds.", null ] [2013-12-10 23:34:34] pool 3 JSON stratum auth failed: [ -2, "Worker temporarily banned. Try back in 60 seconds.", null ] [2013-12-10 23:35:35] pool 3 JSON stratum auth failed: [ -2, "Worker temporarily banned. Try back in 60 seconds.", null ] This is what I'm seeing. It's the same worker name across many rigs. Some seem to encounter the problem, others do not. But all have the same workername/pw as they get it from the same script Ideas? I'll check the logs and let you know.
|
|
|
hello, I have same problem with WDC payout, requested half an hour ago and still stucked
Same exact issue here. Auto threshold didn't work and manual is stuck at requested Hot wallet ran dry overnight, payouts should have gone out a couple hours ago. Sorry for the delay.
|
|
|
I am getting a lot user banned messages, causing cgminer to failover to a different pool. Is there something I need to change? I have two workers, each coming from a separate but stable IP (not static but hasn't changed in months).
the only way to get banned is by submitting lots of invalid shares or continually trying to authenticate using a worker name that doesn't exist.
|
|
|
|