|
I'd like to mention once again, that 'merged mining' isn't stealing of someone's hashrate for mining some alternative weird-currency; merged mining is something like testing submitted shares twice - first time against bitcoin target, then against namecoin target. And people which aren't interested in NMC will earn still the same amount of bitcoins.
|
|
|
|
Would it be possible with a further increase in the NMC limit? Just so we can keep it to 1 payment a day? Having a ton of different payments come in during a day is confusing. I realize that you aren't a bank but plz  Currently that threshold limit is 100NMC. Still not high enough? :-) |
|
|
|
Since merged mining began on site I've found my system has become unstable when mining btc. Is seems fine on my backup site for mining.
Of course there was big problems with connectivity due to DDoS attacks. Not sure if you counted it. There was also few issues with backends two weeks back when pool started with merged mining, but then I disconnected problematic pools and thanks to recent update of backends, merged mining does not affect mining at all; now it's definitely not an issue. Thanks to my pool monitoring I can tell that now is pool in excellent condition. Recently you said the whole network is used though for merged mining could this be causing issues for those of us that aren't interested in namecoins? If it is why not offer an opt out from merged mining for those of us that don't wish to mine namecoins?
Merged mining, when done properly, cannot affect "non-namecoin" users. And I'm absolutely sure that merged mining is working great. Technically merged mining is only small patch for bitcoin backend, nothing what you can 'opt out'. If you're not interested in namecoin, it won't affect you at all and you even don't need to know that your hashrate is 'used for merged mining'. However if you claim your namecoin address, you'll get bunch of coins on top of your bitcoin income. |
|
|
|
0.4 btc per 24 hours on deepbit with near 0% 24-hour luck and 0.27 btc plus uncounted amount of NMC here...
so basically either the pool is super unlucky atm or mm is not as harmless as is was promised to be. we'll see in a few more days just to exclude the possibility of extreme unluck...
What's your stale ratio? And yes, there were two 6+ hours in last 24 hours, so you're right. It's just a "luck". Btw what's "uncounted amount"? or mm is not as harmless as it was promised to be No, MM is definitely not an issue :-) |
|
|
|
read the thread
Can you point me to some post, please? I searched thread, but cannot find any explanation. I'm also wondering why eligius need to know where I have a nmc wallet and which client I'm using. |
|
|
|
Nothing you need to do. It is handled for you. Ntime rolling allows the miner to re-use a getwork request by incrementing the timestamp locally for a rolling period of time. This reduces the amount of communication necessary between the pool and miner.
NTime is great improvement of network layer, however current (latest) phoenix still doesn't support it. AFAIk only poclbm and maybe cgminer is using NTime rolling; jedi95 promised NTime rolling for next phoenix release. |
|
|
|
If you clicked this tab, you know what to do. <<< it looked to me quite rude, but is better than nothing.
I agree. Simple link somewhere (at least to weusecoins.com) would be much better than this. |
|
|
|
Most likely all the machines behind DDoS had the domain name IP locally cached and with most router/computer configurations if you are actively using some addresse it takes very long time to flush the local cache. In fact it might never happen if you constantly query something from that domain.
Saying that the attack didn't go over to btcguild and because of that they are to blame is funny. For people who has problem with reading: But *everytime* when I changed DNS records to new IP or even when I created yet another DNS record (do you remember my post about new DNS api3.bitcoin.cz last week?), attack followed those changes in DNS or posts on forum almost immediately So your post about caching of DNS is teoretically correct, however in real life it work differently. |
|
|
|
Are you saying we're going to make more NMC per Mhash from now on?
Yes, much more. Until now only weakest backends were merged mining. All backends were doing merged mining only for short period on the beginning, before I realized that it's crashing under high load. But now is 100% of pool power on NMC. Momchil is my hero. |
|
|
|
|
Maybe you noticed short restart of backends. I pulled all backends to merged mining, so you should see much higher namecoin rewards since now. Many thanks to m0mchil who helped me with combining "merged mining patch" together with previous pool optimizations.
|
|
|
|
Whitelisting actually sounds like a smart idea.
Could that potentially be the solution to the problem?
No, not itself. I provided whitelist to ddos mitigation company, so it helped a little, but you still need huge pipe and hell fast routers. |
|
|
|
|
One day and five hours. Longest. Round. Ever. :-)
|
|
|
|
I just hope you stay alive
Me too  |
|
|
|
|
Yes, longest round on my pool ever, but we're up again :-).
|
|
|
|
I analyzed the problem and found out, that the database is the bottleneck.
Huh, reminds me my times back in January :-). Good luck with update. |
|
|
|
All others namecoins also not received?
I didn't process all payments yet; I was waiting untill all blocks mature, which happen before few hours. I'll pay out also namecoins, of course. |
|
|
|
|
(registering to the thread)
|
|
|
|
Which is right?
btcguild went down around one hour later after my change of IPs *back* to my servers and was under an attack also today. So I really don't expect that attacker didn't notice that IP changed back agian. |
|
|
|
Anyone who supports Slush's attack on BTCG is wrong.....
Actually this wasn't an attack, just a test. I didn't want to hurt btcguild and I was ready to switch DNS back asap in case of any troubles. Btw I don't expect that all people understand what I did with DNS. Because not all people can empathise to the situation when you're facing attack and you want to understand at least something... |
|
|
|
DNS propogation is not instant, it can take hours in some cases for the new ip's to propagate to all the DNS servers in the world
But *everytime* when I changed DNS records to new IP or even when I created yet another DNS record (do you remember my post about new DNS api3.bitcoin.cz last week?), attack followed those changes in DNS or posts on forum almost immediately. Thanks to that I know attacker is here between us, following what's going and targeting attack to new places instantly (in matter of minutes).
Don't forget that this wasn't first attack to pool and this pattern was here every time. So yes, this *prove* that attacker didn't follow IP changes intentionally. |
|
|
|
|
Show Posts
