Topic: [ANN][SHIFT] The New Web | IPFS/Phantom | ShiftNrg.org Hosted Decentralized! - page 130. (Read 547569 times)

My node got "corrupted or incomplete meta file" notice when i run gshift. I saved my walletkey then deleted the whole gshift folder at appdata. I use windows 7 64bit by the way.

I ran 3.1.0 on --fast and took 26mins to completely resync. Previous chaindata was at 370MB but 297MB only with 3.1.0. Is this normal? I have mined several blocks already after synching.

We have left them a message on Skype and I just put a notice next to the link on the first page.

Thanks again, Jeff!!

Haven't seen Richie online today yet but we're constantly keeping an eye on it.

Meanwhile we're using the downtime to go through possible solutions against the different attack vectors and we're incredibly thankful to everyone who is dedicating their rig(s) over the next days to help us take our mind off one of those vectors.

Looks like mskpool is still running on the old chain and have 3 miners online, anyone heard from them?

It's good to see you back in this thread I am glad everyone is coming together to strengthen the network when it needs some stabilizing. Hopefully after this debacle is settled we can back to focusing on the potential of phantom. In the most recent release being able to create a website and letting it propagate through the network allowing access to your website anywhere through phantom is quite powerful.

123MHs solo to keep things even make sure Bittrex comes back.

Hi guys, I see that you have developed a difficult situation and decided to help you to distribute your 225 mh connected to allocate pools speed.

We'll walk away from this wiser, that's certain.

Sadly it's not up to us which pool people choose, we can only advertise solo mining as much as possible. But we'll keep an eye on it and try anything we can to inform people about a negative hash distribution so they can take the necessary measures.

Glad you got my msg and sorted it out
Unfortunately you are not alone. All of the pools made the same mistake.

Good job anyway support the miners and miners will support you.

Ok, I wanted to let everyone know what I'm doing here.  I don't really know how to retroactively fix the payments in the pool, but luckily there were not very many mature blocks with the 1 SHF reward.

The only blocks with the incorrect reward being credited to miners occurred between 674100 and 674212 which occurred roughly over an hour and a half.

Note that miners are being credited when the blocks mature.  The reward is being calculated at 2 as they mature, so the pending blocks are 2 SHF once they mature, although they seem to be displaying as 1 SHF in the immature block list.  As they mature, they will move to 2.

So here is what I am doing:

First block of 2 SHF - 2016-08-18 06:33:36
First block of matured blocks actually paying out 2 SHF on the pool - 2016-08-18 07:56:14 ( 674215 )

All payments between the last payout before the reward update up until the last payout before the 2 SHF credit was in effect are being manually sent twice what was paid out.

As far as I can tell from looking at the miners online at the time, this should cover the diffrence plus I am just going to take a small loss on it, it was my fault for not having it updated.

Here is what I'll be sending:

0x9fc23ea7a3940a402d24ffdc0af68f9cbfeb0f83      14.528296029
0x8f934e5abd5af7eb46099687d2c4d74813e19b80      3.624578215
0x24485095d2153e4f195753021da433653f82f44a      3.234625182
0xe92ea70da75af0654b4a295ac56f31e542615633      2.340545965
0xcc202d7fb3a8b3345ebeda29fda7cf9c6a37345b      1.454579128
0x53291aa49b812fb6c1ed290fb0f792e7f586e503      6.354655389
0x51cf41e75626650f342fc0218023422324068116      1.460095588
0x3e5391680cb37850ca897209643d1a902717f0c6      2.53234196
0x4f58d07b6b720dd0893312b20128a9e442e007c7      1.795896409
0xcc202d7fb3a8b3345ebeda29fda7cf9c6a37345b      2.78573512
0x53291aa49b812fb6c1ed290fb0f792e7f586e503      5.768105151
0x24485095d2153e4f195753021da433653f82f44a      3.059567829
0x8f934e5abd5af7eb46099687d2c4d74813e19b80      4.426224093
0x3e5391680cb37850ca897209643d1a902717f0c6      2.592521773
0x9fc23ea7a3940a402d24ffdc0af68f9cbfeb0f83      16.725544318
0xe92ea70da75af0654b4a295ac56f31e542615633      1.789284249
0x51cf41e75626650f342fc0218023422324068116      1.334481868


If you feel I'm missing something or you think your address should be listed here, please let me know. 

Take it as a learning experience and that there is a reason people like me become concerned when hashrates become centralized.

51% attacks are a real threat and this time Shift got lucky it wasn't someone who really wanted to cause harm.

They also become a threat anytime a single pool controls 51% of the hash if that pool were to become hacked.  I have expressed concerns in the past about the centralization of the hashrates in shift.

Sorry anyone on shift-pool has still been receiving block rewards for 1 SHF per block.

It was set to auto restart when the change went into effect but it looks like it didn't work.  I will be crediting everyone for blocks mined since the update soon.

The amount of money involved was fairly low, we're talking about a sum of ~2 BTC.

As stated, due to security reasons for us and also a lot of other coins neither we nor the developer responsible want to go into detail on how the exact process went. Please understand that releasing a detailed how-to would not only put us but a lot of other coins at risk.

The person responsible immediately notified Bittrex after noticing the incident and has shown a lot of effort to eradicate the resulting consequences. He joined us on Slack last night and told us he was in direct contact with Richie to arrange sending back the coins mistakenly obtained from this. We have also received various offers in other ways from him to make up for it.

This is no glorification of what has happened or of the person's actions since it could have caused much more harm than it did. But for now we believe this was not a malicious attempt at manipulating our network but an honest mistake since the developer went through a lot of trouble to prove that.

Whether this was a good or bad thing happening is debatable, we definitely hope everyone can see how much work and quick reaction it took from our side to deflect any potential harm to all parties involved. However we learned a lot from it and in a way will move on differently after this.

After all, any blockchain has little inherent value and is only worth the developers building on it and the users supporting it. Thus we have to create an environment that is both viable economically and safe to invest time and money in for everyone.

If you want to join the Slack:
http://www.shiftnrg.org/slack-auto-invitation

Mind if someone can expound on what really happend, how much btc was involved? Didn't the attacker realize that he, in a manner of speaking, killed the reliability and trustworthiness that shift has been working on since the coin was launched. Really hope bittrex will enable trading this coin again.

Well and good. Hope it will be back as soon as possible. Its fun mining shift. I'd been mining and supporting shift although with 1 rig on solo. I might point all if the profitability changes. Hoping for the best.

Trading hasn't been disabled permanently and we are taking every measure to secure the network in the future. This goes from increased block reward to greater marketing to subsidizing nethash in times of need and most importantly to new developments for increased attack resilience on the code level.

Yes.

We are in close communication with Bittrex and are working to meet their demands. We are very confident the market and wallets will come back online soon, we just can't give an exact date as every party needs to be absolutely certain this was a one time incident and all balances are 100% safe from any harm.

Hey Mike, we missed you! Happy to hear you're back.

I agree fully, Bittrex is absolutely the primary exchange when it comes to security.