|
My pool is back up. Those DDoSes are so boring to maintain :/
|
|
|
|
BTCguild is having intermittent connection issues as well. Is everyone under attack?
Yes, looks like it is an attack to all major pools. Personally I don't understand this effort. Except that is fed up some people like me, because reconfiguring pool is stupid and boring job, it has no long term effect on Bitcoin economy. |
|
|
|
There is still one balancer restart ongoing, but it will be up in less than one minute. So don't panic for few connection errors  (it's enough that I'm panicking  |
|
|
|
It was large scale DDoS, but pool is back up. IP has been changed, please check that your miners connected correctly. I made one small mistake with fixing website, so it will be up in one hour as well. Edit: As a hotfix, http://api.bitcoin.cz works as website access, too. However SSL certificate is invalid because of different domain, of course. |
|
|
|
Pool is under attack, I'm working on it. Sorry for downtime  . |
|
|
|
As it happens the news of slush doing the merged mining only came after everyone started wondering just WTF was going on, on the pools that had announced they were doing the merged mining when they suddenly found that there was an extremely large numbers of blocks being mined that could not be accounted for. People then started asking just what pool was up to no good scheming up all the blocks with massive hash power only then was it revealed that unlike the others who gave people a choice to mine NMC merged Slush had taken it upon himself to do it in secret hiding the fact it was happening so no one could mine them other than was already there at the time.
Bullshits. If you followed namecoin movement (forum, irc) then you definitely had to found my interest in merged mining. I was in contact with namecoin developers and fans. It wasn't *so* big secret at all. But it was everything so new for me, so I didn't want to make public announcement until I was sure it will work somehow. And even after merged mining started, there were some problems and I turned off MM for more than a day. That was a real reason why "official" announcement come so late. Please stop finding conspiracy theories. Also "hidden merged mining" is not possible. Fact that pool is using merged mining can be found in every pool's BTC block. |
|
|
|
|
I think that other than intraday charts are using some extra information from datafile which is missing (as this binary format is unknown for me).
|
|
|
|
Slush, I like the new "Key Features" on the homepage. Just a few grammatical suggestions similar to the ones I've made before to help the section read better. Take whatever you'd like from here. Words I have changed or added are in red. Comments are in code.
Thank you a lot! :-) I know that my grammar is crazy, but sometimes I need to update website texts . I'll add those fixes soon. |
|
|
|
|
I'm sorry for 3minute outage on api2.bitcoin.cz and website, it is again working now.
|
|
|
|
Although I'm physically located in Prague, I'm thinking and living in UTC . |
|
|
|
Any word on when the pool will start processing rewards? I had some unexpected stuff today (not Bitcoin related), so I didn't work on this today, my bad. But I know people are waiting on it, I'll finish rewarding system tomorrow. |
|
|
|
Not saying this IS what slush will do just pointing out a moderately fair distribution isn't that difficult. Would be nice to get some clarification from slush though.
Yes, I'll use similar method for already mined namecoins. I'll definitely look in history how much user mined for pool since merged mining started. |
|
|
|
Edit: Nevermind. THe confirmation link uses the namecoin address as the confirmation number, but the cancel link has the confirmation number in the url. Should probably fix this
Oh, what a stupid bug. Will fix it soon. Thanks! Edit: Fixed bad confirmation link in email. |
|
|
|
And slush i'm still getting errors..
I'm playing with this one backend, actually those "retrying" was probably one restart. |
|
|
|
Although there were some rumors on IRC and forum already, I'd like to officially announce support Merged mining for Namecoins on my pool! If you don't know what merged mining or Namecoin is, please read short introduction. Generally it means higher income for the mining for free; you even don't need to update your miners. Everything you really need is to login to pool profile and fill correct Namecoin address to claim your interest in Namecoin. I was playing with Namecoins for many weeks, trying to bring bleeding edge features for pool members. I had to solve some scaling issues, because adding new untested features to high availability application is always a risk. Heavy testing of all stuff is also a reason why I didn't finished GUI and accounting system on time, but I'm working on intensively and it will be in production very soon (probably tomorrow, after some sleep). For the beginning I expect simple proportional rewarding scheme, but there will be two huge benefits for users mining Namecoin on my pool: a) Pool already mined over 10000 Namecoins (and it is going up in very fast rate, see NMC stats. I'll start giving away those coins to pool's Namecoin miners after few days using their proportional hashpower. First namecoin miners actively mining on pool may expect really big namecoin rewards. b) I'll be giving mined namecoins only to users who claimed their interest in Namecoin by setting up namecoin wallet on their profile. But pool is already mining for Namecoins with all his power. This effectively leads to situation that if only 1/4 of pool users setup their namecoin account (which is ratio I'm +/- expecting), they'll earn 4x more than is corresponding to their hashpower). Happy mining! |
|
|
|
I just updated website. List of Namecoin blocks mined by pool is here. |
|
|
|
My issue is: That hashrate has no point in being there.
Wait - what? You're jealous that I'm mining namecoins for my users? If people want merged mining they go where it is offered.
Or they just don't need to do anything because they know that will earn namecoins for mining on my pool. Unofficial testing is just a convenient way of risk reduction (for you).
It is "unofficial" because there were silly problems before and I didn't finish GUI yet. Sorry, but it looks like you never developed something what must be together 24/7 up and on bleeding edge (which MM definitely is). The thing was announced way in advance so there was plenty of time to test on testnet.
Haha, the best thing on this sentence is that I have prepared merged mining weeks ago. But it started crashing on production network. Yes, sometimes things are crazy. Stealing may not be the right term, but we (the people mining at official merged pools) would get more nmc if it weren't for you, even if you pay out the earning to your miners.
I don't know what to say to this, except - sorry, world isn't fair. It's the same as I can say "damn, I might earn much more if deepbit never come". |
|
|
|
Not the same thing.
I didn't tell it is the same, of course. My way is officially supported by namecoin developers :-P. It still requires the messy bitcoind patches, and you need to integrate it with your pool software. :p
Looks like everybody prefers another solution. It's nice thing on bitcoin than everybody can do whatever he wants . |
|
|
|
That doesn't support anything but proxy, and is in fact the exact code my merged-mine-manager is based on.
1. ask proxy for actual aux using getaux method 2. use this aux in getworkaux(aux) for asking directly bitcoind for new work (no proxy call here) 3. filter out shares with lower difficulty than min(bitcoin difficulty, namecoin difficulty), send the rest to proxy. It still make almost no load to proxy 4. If your pool detect that namecoin or proxy crashed, use latest aux for all getwork requests, so you don't need proxy. 5. If you receive share during proxy outage, call getworkaux('submit', <datastring>) directly to bitcoind to submit a block 6. Profit! (And without any custom code) |
|
|
|
Doesn't anyone think that slushs "testing" implementation is also cheating?
lol, why do you think I'm "cheating"? Even if thier miner get payed afterwards, nobody will notice if a fraction of the nmc not get payed out, and most importantly he is stealing from the official merged mining pools by increasing the overall hashrate.
Well, my pool is also "official merged mining pool", I just didn't finished GUI&other stuff. Don't forget that I have already big load on pool, so releasing such bleeding edge software is much harder than for 20GHash pools... So the way I put it: Slush gtfo of our merge  Of course I can cheat! Any pool operator can cheat. I can not publish some merged mined blocks for namecoin and nobody will notice, as any other merged mining pool can do. So why do you have problem with me? I think that I already prove that I'm not a scammer, by running pool for the longest time ever. |
|
|
|
|
Show Posts
