I've started buying ad space.
www.cryptoarticles.com - http://www.alexa.com/siteinfo/cryptoarticles.com
www.rainbow-btcfaucet.tk - http://www.alexa.com/siteinfo/http://rainbow-btcfaucet.tk
More coming tomorrow.
Topic: [ANN] H2O Coin |Yahoo!Finance & more| DGW + Scrypt-N - *DONATED 17.5BTC* - page 36. (Read 247159 times)
April 01, 2014, 05:33:11 PM
April 01, 2014, 04:26:30 PM
Alright, from now on, just so we can level things out as soon as we can, if you have a problem with H2O coin, please report it
http://ghostbackwards.com/error.html
Thanks,
-tsohG
http://ghostbackwards.com/error.html
Thanks,
-tsohG
April 01, 2014, 04:18:25 PM
thanks Ghost. that did it. now at 4572 of 4573, and still out of sync. but it's more up to date. lol
That's the current block 
You're now ready to fly!
April 01, 2014, 04:15:37 PM
thanks Ghost. that did it. now at 4572 of 4573, and still out of sync. but it's more up to date. lol
April 01, 2014, 04:08:02 PM
The only thing that was affected by the bug were windows wallets. If you are hosting a pool on a windows server well then that is just silly. Regardless if you had applied the newest patch as direct you would have been all set.
I NEWER use windows, only linux. And I always compile my daemons from source code.
So, your bug is much wider than you think.
Your pool is the only one that is "having a problem". Though I don't even believe it is. All I ask is if you do have an issue, hop on over to IRC and let the community work with you to fix it. I've never even heard of your pool until you said you were closing it down, I've been in IRC more or less all day since launch. If there is a problem, don't sit back and play the victim card. Be proactive, work with us to get to the solution so we can all get back to mining.
April 01, 2014, 03:56:53 PM
anyone else stuck on block 3365? I just downloaded the wallet for linux, and this is as far as it got. #3365
Stan-O make sure you apply this patch, there are a few instances where restarting your linux wallet will sync it, however this will ensure you are connected to the right nodes to stay connected http://ghostbackwards.com/H2Ocoin_LAST.zip
April 01, 2014, 03:54:54 PM
anyone else stuck on block 3365? I just downloaded the wallet for linux, and this is as far as it got. #3365
April 01, 2014, 03:50:45 PM
Due to very unstable coin and oft-recurring forks H2OCoin was disabled on DwarfPool.
Today we had 3(!!!) different forks on 4 servers, every with many connections!
There are no forks.
As a pool owner, you're responsible for your people. You should know that there were issues with the wallet. You should update your blockchain, with the one everyone else is using.
They are forks! Servers with different forks were connected with a lot of nodes.
I know what is responsible, therefore my pool has very good reputation. And we have always found solutions, also in very hard time (problems with blitz, 365coin first-day-many-forks)
I made some tests, just deleted all files except of wallet.dat, in config nodes added nodes only from first post or deleted all nodes (used fixed implemented in code).
And the same server got different forks from these first-post-nodes/fixed-nodes everytime!
Finally, as I got right fork, I have stopped the experiment to make payout in the right fork.
And yes, I have compiled with the last checkpoints. And no, my servers do not use other my servers as nodes.
1gh and dwarfpool are both great pools.
I believe in their reputation,especially compared to the innocent dev and the funny coin.
The first (or maybe second, not sure about that) launch of this coin failed.
And now it forked. Well, a nice IPO coin.
April 01, 2014, 03:49:51 PM
The only thing that was affected by the bug were windows wallets. If you are hosting a pool on a windows server well then that is just silly. Regardless if you had applied the newest patch as direct you would have been all set.
I NEWER use windows, only linux. And I always compile my daemons from source code.
So, your bug is much wider than you think.
You're the only pool which had the problem.
What's your point? If you want to advertise your pool, do it.
Stop attacking people instead.
None under linux / MAC didn't report any issue.
If you followed the topic, you'd know that there's a fix about that.
Don't blame others if you didn't know what happened and wasted your miner's time.
Why didn't any other pool say about the issue?
Anyway. If you want to continue it, please use PMs.
@ThisWeeksCoin
April 01, 2014, 03:49:24 PM
Due to very unstable coin and oft-recurring forks H2OCoin was disabled on DwarfPool.
Today we had 3(!!!) different forks on 4 servers, every with many connections!
There are no forks.
As a pool owner, you're responsible for your people. You should know that there were issues with the wallet. You should update your blockchain, with the one everyone else is using.
They are forks! Servers with different forks were connected with a lot of nodes.
I know what is responsible, therefore my pool has very good reputation. And we have always found solutions, also in very hard time (problems with blitz, 365coin first-day-many-forks)
I made some tests, just deleted all files except of wallet.dat, in config nodes added nodes only from first post or deleted all nodes (used fixed implemented in code).
And the same server got different forks from these first-post-nodes/fixed-nodes everytime!
Finally, as I got right fork, I have stopped the experiment to make payout in the right fork.
And yes, I have compiled with the last checkpoints. And no, my servers do not use other my servers as nodes.
1gh and dwarfpool are both great pools.
I believe in their reputation,especially compared to the innocent dev and the funny coin.
The first (or maybe second, not sure about that) launch of this coin failed.
And now it forked. Well, a nice IPO coin.
April 01, 2014, 03:43:41 PM
The only thing that was affected by the bug were windows wallets. If you are hosting a pool on a windows server well then that is just silly. Regardless if you had applied the newest patch as direct you would have been all set.
I NEWER use windows, only linux. And I always compile my daemons from source code.
So, your bug is much wider than you think.
April 01, 2014, 03:33:40 PM
i love this coin, it will go to moon, dont put your pool pls, thanks if you think like this. just look the volume polinex, just 2.4M volume today.
if you think like this. just look the volume polinex, just 2.4M volume today.I am not envious and never was
my only wish to work with honest and reliable people
Good luck!
It's not like the devs threw up their hands and said screw it. This problem has never happened before in any other coin so any fixes had to be done on their own. As for honest and reliable, the problem was acknowledged and the newest fix seemed to fix the problem for good. Hopefully a new wallet with the patch will be packaged in the next day or so and it will be smooth sailing from there. Patience is a virtue.
Also, no other pools seemed to have any of the issues you are facing, if you wanted to come into IRC, I would have loved to help you personally. Instead you chose to public denounce H2Ocoin. hashkings has had 0 issues with their pool and has been running since day one. The only thing that was affected by the bug were windows wallets. If you are hosting a pool on a windows server well then that is just silly. Regardless if you had applied the newest patch as direct you would have been all set.
I hope you all the best in your mining pool operations. Good day.
April 01, 2014, 03:17:52 PM
Hopefully I've isolated the issue and this is the last patch that you need to download. http://ghostbackwards.com/H2Ocoin_LAST.zip
Just curious...what was the issue?
If the fix works, then the problem was with a few of the nodes.
I added the latest patch early this AM. Wallet synced. I came home and wallet was still synced, much to my surprise. I closed the wallet and restarted it and it still synced. I used the last patch which contained the new .conf. Since then everything has been operating normally. The question now is, if it was a node, what node was causing the issue and why?
April 01, 2014, 01:43:21 PM
Just to say that I have a previous experience mining Fuguecoin at Dwarfpool and everything was fine.
thank you!!
I get every day appreciative emails and messages from satisfied members.
my dev is very professional! sure, there are small things that every pool has, but we improve our work constantly, how I said, the most important things are trust and confidence of our miners!
April 01, 2014, 01:32:46 PM
Just to say that I have a previous experience mining Fuguecoin at Dwarfpool and everything was fine.
April 01, 2014, 01:31:31 PM
i love this coin, it will go to moon, dont put your pool pls, thanks if you think like this. just look the volume polinex, just 2.4M volume today.
if you think like this. just look the volume polinex, just 2.4M volume today.I am not envious and never was
my only wish to work with honest and reliable people
Good luck!
April 01, 2014, 01:27:26 PM
i love this coin, it will go to moon, dont put your pool pls, thanks if you think like this. just look the volume polinex, just 2.4M volume today.
if you think like this. just look the volume polinex, just 2.4M volume today. April 01, 2014, 01:10:13 PM
Please, if you have the same problem, check ANN OP. I've updated the nodes we had there. Those seems to be working well!
I know, I'm not putting a blame on you. You just could come and inform me via PM and inform your guys that there's a issue.
We'd fix it in 5 minutes.
Instead of that, you came and said that youve disabled H2O in your pool ;p
but I'm putting a blame on you!
first, we've lost three evenings with your damn launch! however we solved to to finish it because of only one thing, I liked it, how you managed your problems with people here..
second, our users are not much interested in your coin, especially because of your great "support" for pools. you did not even aswer my private request to add our pool to your list! are there any problem with our pool? but you answer right now as well as my dev points to your bug.. that's funny, I found this is not very fair "support", do you find so??
YOU have to solve it if anyone suspect such bug ON YOUR PRODUCT, and not scold that the other is a lier!!
YOU are responsible for ALL miner who mine YOUR COIN
and precisely because we attach the greatest importance to safety and convenience for our users and as pool owners, we are very responsible for our people, for these reasonsWE decide not to support your coin on OUR pool any more, I just find it waste of time.
that's our decision and nobody has anything to say, what we had to do! I guess, your devs cannot guarantee futher, that there are no more such bugs..
April 01, 2014, 12:00:01 PM
HashKings has a 1% fee
Why do we charge a fee? We use a portion of that fee to offer you REWARDS and BONUSES for mining with us, but more importantly we will use a more then50% of that fee to help charities through donations for clean water!.
For a quick guide to setting up your miner and configuring your .bat visit our Getting Started Page
HashKings PPLNS Pool to mine your H2oCoin!
We Need Your Hash!
1% Pool Fee goes towards Charity.
PPLNS payout system
DDoS Protected
Dedicated Servers
IRC chat help #hashkings
Point your miner to: stratum+tcp://h2o.hashkings.com:3333
We Fully Support H2o Coin and can say they are trying their best to fix any issues that might arise
Our Pool is open and welcoming new members!
We just got done with our 1st round of giveaways check our website to claim your rewards!
http://h2o.hashkings.com
April 01, 2014, 11:25:01 AM
Due to very unstable coin and oft-recurring forks H2OCoin was disabled on DwarfPool.
Today we had 3(!!!) different forks on 4 servers, every with many connections!
There are no forks.
As a pool owner, you're responsible for your people. You should know that there were issues with the wallet. You should update your blockchain, with the one everyone else is using.
They are forks! Servers with different forks were connected with a lot of nodes.
I know what is responsible, therefore my pool has very good reputation. And we have always found solutions, also in very hard time (problems with blitz, 365coin first-day-many-forks)
I made some tests, just deleted all files except of wallet.dat, in config nodes added nodes only from first post or deleted all nodes (used fixed are implemented in code).
And the same server got different forks from these first-post-nodes/fixed-nodes everytime!
Finally, as I got right fork, I have stopped the experiment to make payout in the right fork.
And yes, I have compiled with the last checkpoints. And no, my servers do not use other my servers as nodes.
Please, if you have the same problem, check ANN OP. I've updated the nodes we had there. Those seems to be working well!
I know, I'm not putting a blame on you. You just could come and inform me via PM and inform your guys that there's a issue.
We'd fix it in 5 minutes.
Instead of that, you came and said that youve disabled H2O in your pool ;p
Jump to: