[ANN] H2O Coin |Yahoo!Finance & more| DGW + Scrypt-N - *DONATED 17.5BTC*

[Jake_Shake]

We're alive, this coin is alive, the community is alive.

H2Ocoin promotes life, so of course we're alive.

I hope the community is doing well. I want to thank everyone sticking in there! Value took a nice little jump today - hang in there with your coins everyone!

[Black Tongue]

Hey guys, we're alive even though I wish we were moving faster.  

The current obstacle is that after TWC's and the dev's departures, we are left without a dev. Brainstorming is done, the rebuild plan is set but we need a dev who would be able to patch things up. We're looking actively but we're not finding. We have Ghost in the team (he did the linux wallet) but he doesn't have much time unfortunately and would only be able to supervise, and Winevirus who was the dev is MIA and we can't contact him. Therefore, we are currently in the process of hiring a new dev. If anybody knows one, feel free to contact me, a reward will be given.

The current situation is a little frustrating because everything is set (the team has agreed about how to rebuild the coin) but we're only missing a dev to make things happen. And that's why I'm currently quiet because I don't want to make any announcement which would then only be wind.

By the way, don't forget to claim your bonus after the mining marathon, PM me with :
 - the total number of coins mined during the seven days
 - the total number of mining days
 - your average hashrate
 - and a screenshot.

Thanks for the support.

[@ThisWeeksCoin]

I'm going to talk to a developer. He's going to help with the wallet.

Got some free time now.

[gatt13]

I'm going to talk to a developer. He's going to help with the wallet.

Got some free time now.

Welcome back 

[n3lz0n]

nice...

[richiela]

Anyone seeing a fork of the network?

http://cryptexplorer.com/block/7b36c5218d3e16c3a8537bb41a60b674ccb93763d7ef12fa4d11b44898b2f116

Hash7b36c5218d3e16c3a8537bb41a60b674ccb93763d7ef12fa4d11b44898b2f116
Previous Block3e712e5bd4e0b068d64ffadd842a4edd20241db2259b5592a19c75e49351997f
Height 92804


Our wallet:
h2ocoin getblockhash 92804
802da677e3b72da352af34679ff4a85ffef027975755f3e992355dad0459b3fd

the last good match we have with the BCE is
getblockhash 92780 1b4726cd4d7e7387fe1e4802017520a3cbdc3ea5352e91a8e88028ff02088946


Anyone else seeing this?

[Black Tongue]

Anyone seeing a fork of the network?

http://cryptexplorer.com/block/7b36c5218d3e16c3a8537bb41a60b674ccb93763d7ef12fa4d11b44898b2f116

Hash7b36c5218d3e16c3a8537bb41a60b674ccb93763d7ef12fa4d11b44898b2f116
Previous Block3e712e5bd4e0b068d64ffadd842a4edd20241db2259b5592a19c75e49351997f
Height 92804


Our wallet:
h2ocoin getblockhash 92804
802da677e3b72da352af34679ff4a85ffef027975755f3e992355dad0459b3fd

the last good match we have with the BCE is
getblockhash 92780 1b4726cd4d7e7387fe1e4802017520a3cbdc3ea5352e91a8e88028ff02088946


Anyone else seeing this?

I'm investigating your claim at the moment with the help of Ghost. I'll update the situation later.
Thanks for finding this possible issue.

I'm going to talk to a developer. He's going to help with the wallet.

Got some free time now.

Thanks a lot !
I've looked everywhere I could but I don't have the connects to find one...

[Black Tongue]

Supporters,

A bug with solo mining has been detected today. The problem is the following :
 - input address is null
 - output address are generated randomly
 - transaction id has a suffix at the end, for example "-000" which prevent them to be visible in the blockchain.
 - transactions in transactions history have a question mark

This is not a fork as pools are operating nicely and we recommend you to stop soloing if you're doing it a the moment and switch to pool mining until the issue is resolved. First hint of what could cause that would be a dysfunctional node in the network.

Some supporters have unfortunately lost some coins because of that. If it's your case, I engage myself to personally refund you the lost amount.

Anyone seeing a fork of the network?

http://cryptexplorer.com/block/7b36c5218d3e16c3a8537bb41a60b674ccb93763d7ef12fa4d11b44898b2f116

Hash7b36c5218d3e16c3a8537bb41a60b674ccb93763d7ef12fa4d11b44898b2f116
Previous Block3e712e5bd4e0b068d64ffadd842a4edd20241db2259b5592a19c75e49351997f
Height 92804


Our wallet:
h2ocoin getblockhash 92804
802da677e3b72da352af34679ff4a85ffef027975755f3e992355dad0459b3fd

the last good match we have with the BCE is
getblockhash 92780 1b4726cd4d7e7387fe1e4802017520a3cbdc3ea5352e91a8e88028ff02088946


Anyone else seeing this?

I discussed and investigated with Ghost about it and it doesn't seem to be a fork.
Block height on our wallet was right (93231 as I speak), same as the blockchain's.

Could you explain why you thought of a fork ? I'm not knowledgeable enough myself so maybe there are hints I didn't see.

[owlhooter]

Supporters,

A bug with solo mining has been detected today. The problem is the following :
 - input address is null
 - output address are generated randomly
 - transaction id has a suffix at the end, for example "-000" which prevent them to be visible in the blockchain.
 - transactions in transactions history have a question mark

This is not a fork as pools are operating nicely and we recommend you to stop soloing if you're doing it a the moment and switch to pool mining until the issue is resolved. First hint of what could cause that would be a dysfunctional node in the network.

Some supporters have unfortunately lost some coins because of that. If it's your case, I engage myself to personally refund you the lost amount.

Anyone seeing a fork of the network?

http://cryptexplorer.com/block/7b36c5218d3e16c3a8537bb41a60b674ccb93763d7ef12fa4d11b44898b2f116

Hash7b36c5218d3e16c3a8537bb41a60b674ccb93763d7ef12fa4d11b44898b2f116
Previous Block3e712e5bd4e0b068d64ffadd842a4edd20241db2259b5592a19c75e49351997f
Height 92804


Our wallet:
h2ocoin getblockhash 92804
802da677e3b72da352af34679ff4a85ffef027975755f3e992355dad0459b3fd

the last good match we have with the BCE is
getblockhash 92780 1b4726cd4d7e7387fe1e4802017520a3cbdc3ea5352e91a8e88028ff02088946


Anyone else seeing this?

I discussed and investigated with Ghost about it and it doesn't seem to be a fork.
Block height on our wallet was right (93231 as I speak), same as the blockchain's.

Could you explain why you thought of a fork ? I'm not knowledgeable enough myself so maybe there are hints I didn't see.

There was the 32 bit client issue which was fixed within the first few days of launch that I noticed I had not updated my 64 bit build on my pool after that was fixed and it ended up on a fork until I rebuilt.  Not sure when Bittrex built their wallet, but hopefully it was after that fix.  But I do wonder if the 32 bit flaw in DGW when it was launched could possibly still cause a fork as the block hash could be close and still possibly have a match.  Maybe a fix with the newest DGW code for H2O would be in order?

[Black Tongue]

Anyone seeing a fork of the network?

http://cryptexplorer.com/block/7b36c5218d3e16c3a8537bb41a60b674ccb93763d7ef12fa4d11b44898b2f116

Hash7b36c5218d3e16c3a8537bb41a60b674ccb93763d7ef12fa4d11b44898b2f116
Previous Block3e712e5bd4e0b068d64ffadd842a4edd20241db2259b5592a19c75e49351997f
Height 92804


Our wallet:
h2ocoin getblockhash 92804
802da677e3b72da352af34679ff4a85ffef027975755f3e992355dad0459b3fd

the last good match we have with the BCE is
getblockhash 92780 1b4726cd4d7e7387fe1e4802017520a3cbdc3ea5352e91a8e88028ff02088946


Anyone else seeing this?

After some more inquiries, looks like you were right : this morning drewdrew (part of the team) who I talked to during the last hour found the blockchain being very slow. He didn't think of a problem until a few supporters reported the solo-mining bug. With the help of owlhooter we found the problem :

WHAT HAPPENED
 - there has been a temp fork this morning but the blockchain resynced well in later blocks.
 - the submitted blocks from solo miners were most likely to a pool with an outdated wallet and caused their blocks to disappear therefore their coins too. We hope that by fixing the issue, they will get them back.
 - we asked bittrex to stop the trade in order to fix the blockchain issue.

WHAT TO DO
 - do not make any transactions with H2O until we fix the issue, just in case ;
 - check your block height (hover the little tick on the bottom right of your wallet) and compare it to the one of the network here : http://cryptexplorer.com/chain/H2Ocoin ;
 - mine on pools until issue is solved because only solo miners were affected by the issue ;

WHAT WE'LL DO
 - owlhooter will help us from now on as our dev.
We hope his presence will not be temporary but he seems to be interested and found our project to be "ambitious"  
 - he will put a hard fork in the blockchain issue by implementing DarkGravityWave3 at a future block (not determined yet) in order to fix the issue because H2O is currently using the 1st version. It will be tested on the testnet to be sure then released.
 - if ok, we'll ask the solo miners, pools and everybody to upgrade their wallet (and backing their wallet.dat before doing so  )
 - none of your coins will be lost because the fork will be on a future block.

[gatt13]

- owlhooter will help us from now on as our dev.
We hope his presence will not be temporary but he seems to be interested and found our project to be "ambitious"  

Welcome aboard owlhooter!!!  I hope your stay is pleasant and enjoyable    I'm really looking forward to this coin getting back on track and being able to attract further interest from other miners/devs.  This really is a good coin at heart

- he will put a hard fork in the blockchain issue by implementing DarkGravityWave3 at a future block
- none of your coins will be lost because the fork will be on a future block.

This is awesome, love that there will be no coin loss    Thank you for the updates Black Tongue

[pete26]

Glad to hear we have a developer! Let's Go H2O!

[owlhooter]

I'm going to work on getting DGW3 put into place and tested as it seems that could be the cause of the issue this morning.  But if anyone that was experiencing the problem happens to have their debug.log I would love to see it so I can see what was happening.

[Kestrel71]

Glad to hear we have a developer!

+1  

Nice to see you helping out owlhooter.  I am sure the H2O community are very happy to have you aboard and greatful for putting some of your own precious time into this.

[gatt13]

I am no means a coin developer, but I was thinking...  When the change to update wallets to DGW3 is done, could it possibly be looked at reducing total number of coins? (maybe not at DGW3 update but sometime in future update by someone). 
If total number of coins now will be 2 billion to exist (if feel the coin will always remain undervalued/priced as there is just too many) I understand the original intent of 2 billion to be different/unique.. but the core values of the coin is what makes this unique already, a charity coin.  I was thinkng if coins were reduced by a factor of 25, so total # would be 80 mil not 2 billion (this will also help increase value and rarity of the coin).  I know alot of work would need to be put into doing something like this (and I do not have the coding/skills needed to even attempt this).  Figured I'd throw this out there and see what others also think.   
Again thank you owlhooter for taking a look at this coin and helping to improve upon it 

[Black Tongue]

Everybody come claim your bonuses from the Mining Marathon.
- 175K sent to Gatt13 after his 7 days of mining.

I am no means a coin developer, but I was thinking...  When the change to update wallets to DGW3 is done, could it possibly be looked at reducing total number of coins? (maybe not at DGW3 update but sometime in future update by someone). 
If total number of coins now will be 2 billion to exist (if feel the coin will always remain undervalued/priced as there is just too many) I understand the original intent of 2 billion to be different/unique.. but the core values of the coin is what makes this unique already, a charity coin.  I was thinkng if coins were reduced by a factor of 25, so total # would be 80 mil not 2 billion (this will also help increase value and rarity of the coin).  I know alot of work would need to be put into doing something like this (and I do not have the coding/skills needed to even attempt this).  Figured I'd throw this out there and see what others also think.   
Again thank you owlhooter for taking a look at this coin and helping to improve upon it 

The team also find the number of coins a little too much. Cutting the supply is in talks but not for the moment as we're focused on fixing the fork issue.

When it's done, the real rebuild plan will be on 

[pete26]

After the coin has been alive for couple months now, I am not certain how this can be done:
1. Let's say you already have an order to sell on Bitrex for 1,000,000 H2O - how such reduction will happen to the new format proposed by gatt13?
2. Or if you have 1,000,000 H2O in your wallet...

reducing the block reward/ original coins count can be dangerous....

[@ThisWeeksCoin]

I'm going to work on getting DGW3 put into place and tested as it seems that could be the cause of the issue this morning.  But if anyone that was experiencing the problem happens to have their debug.log I would love to see it so I can see what was happening.

Welcome aboard, owlhooter.

[owlhooter]

I am no means a coin developer, but I was thinking...  When the change to update wallets to DGW3 is done, could it possibly be looked at reducing total number of coins? (maybe not at DGW3 update but sometime in future update by someone). 
If total number of coins now will be 2 billion to exist (if feel the coin will always remain undervalued/priced as there is just too many) I understand the original intent of 2 billion to be different/unique.. but the core values of the coin is what makes this unique already, a charity coin.  I was thinkng if coins were reduced by a factor of 25, so total # would be 80 mil not 2 billion (this will also help increase value and rarity of the coin).  I know alot of work would need to be put into doing something like this (and I do not have the coding/skills needed to even attempt this).  Figured I'd throw this out there and see what others also think.   
Again thank you owlhooter for taking a look at this coin and helping to improve upon it 

Wouldn't be able to reduce the coin supply by that much since there are already 220 million + coins out there, only thing that could possibly happen would be reduce reward structure going forward from a future block to reduce the total overall coins, but 2 billion coins isn't necessarily a bad thing if you can get the community behind the coin.  Look at Doge, when their community is doing good the price of Doge isn't too bad considering they have over 81 billion coins in play right now.

But I don't know all the plans going forward, I am here as a support to what is wanted/needed for the coin and will help with development to meet those needs.  The DGW3 fork code is ready at least. 

[Black Tongue]

NEW THREAD : https://bitcointalk.org/index.php?topic=640441.0

Please use the new one from now on to discuss about H2O. Links the new wallets are in the new thread.