Quote from: wngdng77 on November 10, 2013, 03:46:16 pm

Quote from: bytemaster on November 10, 2013, 03:18:54 pm

Quote from: wngdng77 on November 10, 2013, 03:16:31 pm

Quote from: bytemaster on November 10, 2013, 03:13:16 pm

Quote from: bytemaster on November 10, 2013, 03:11:28 pm

ANYONE WITH A CLEARED BALANCE SEND ME A PM WITH YOUR PTSADDRESS AND I WILL BE ABLE TO RECOVER YOUR FUNDS

I have a backup of the balances as of the shutdown of the last pool.... and I have the ability to verify that you do not scam me.

Also send me your last known balance output so I can compare.

address: PvZG3MhXga8pD59RUkG91RHgcP4x9Tn5UH
1st wipeout balance: unknown (about 1.3PTS)
2nd wipeout balance: 0.549732
3rd wipeout balance: 0.0366488

Payment sent, please confirm.

Another 2 wipeout just happened (both are 0.0732976PTS): one of the address is PvZG3MhXga8pD59RUkG91RHgcP4x9Tn5UH .
Don't bother paying me, I hope you fix it soon.

Are you using my IP address to track balance? 'Cos I just switch off my VPN, then the wipeout happened.

Quote from: bytemaster on November 10, 2013, 03:08:28 pm

Quote from: darkyoung on November 10, 2013, 03:03:11 pm

Quote from: Winslow Strong on November 10, 2013, 03:00:32 pm

Quote from: darkyoung on November 10, 2013, 02:56:17 pm

I've added 100+ nodes with same address, is that OK?

I wouldn't.  Myself and at least one other had balances wiped out when doing that.  For me there was a crash that occurred which may have been a cause.

It's hard to deploy different address for every nodes.

Code: [Select]

 
  valid: 4745  invalid: 1469  balance: 6.48684  paid: 155.5  pps: 0.0366488  address: Pm8WVX1EmKNfW5X7gNMJjsEtv8juYM5kMB  hpm: 6.95413
  valid: 4758  invalid: 1487  balance: 6.96327  paid: 155.5  pps: 0.0366488  address: Pm8WVX1EmKNfW5X7gNMJjsEtv8juYM5kMB  hpm: 6.97553
  valid: 4758  invalid: 1489  balance: 6.96327  paid: 155.5  pps: 0.0366488  address: Pm8WVX1EmKNfW5X7gNMJjsEtv8juYM5kMB  hpm: 7.00936
  valid: 4761  invalid: 1496  balance: 7.07322  paid: 155.5  pps: 0.0366488  address: Pm8WVX1EmKNfW5X7gNMJjsEtv8juYM5kMB  hpm: 6.97668
  valid: 0  invalid: 0  balance: 0  paid: 0  pps: 0.0366488  address: Pm8WVX1EmKNfW5X7gNMJjsEtv8juYM5kMB  hpm: 7.00857
  valid: 3  invalid: 3  balance: 0.109946  paid: 0  pps: 0.0366488  address: Pm8WVX1EmKNfW5X7gNMJjsEtv8juYM5kMB  hpm: 6.96984
sending 0120b750e69366bef5e1da4984dc92c5625fa9e142ddd440205dc1de44c27e91

The stats been wiped after I added batch of nodes.

Darn it... I don't know what is causing that because it didn't wipe my stats when I moved my client.

All nodes up running now, the stats continued from that wiped out, I don't get that 7.07322 balance in my wallet.

Quote from: Winslow Strong on November 10, 2013, 03:00:32 pm

Quote from: darkyoung on November 10, 2013, 02:56:17 pm

I've added 100+ nodes with same address, is that OK?

I wouldn't.  Myself and at least one other had balances wiped out when doing that.  For me there was a crash that occurred which may have been a cause.

It's hard to deploy different address for every nodes.

Code: [Select]

 
  valid: 4745  invalid: 1469  balance: 6.48684  paid: 155.5  pps: 0.0366488  address: Pm8WVX1EmKNfW5X7gNMJjsEtv8juYM5kMB  hpm: 6.95413
  valid: 4758  invalid: 1487  balance: 6.96327  paid: 155.5  pps: 0.0366488  address: Pm8WVX1EmKNfW5X7gNMJjsEtv8juYM5kMB  hpm: 6.97553
  valid: 4758  invalid: 1489  balance: 6.96327  paid: 155.5  pps: 0.0366488  address: Pm8WVX1EmKNfW5X7gNMJjsEtv8juYM5kMB  hpm: 7.00936
  valid: 4761  invalid: 1496  balance: 7.07322  paid: 155.5  pps: 0.0366488  address: Pm8WVX1EmKNfW5X7gNMJjsEtv8juYM5kMB  hpm: 6.97668
  valid: 0  invalid: 0  balance: 0  paid: 0  pps: 0.0366488  address: Pm8WVX1EmKNfW5X7gNMJjsEtv8juYM5kMB  hpm: 7.00857
  valid: 3  invalid: 3  balance: 0.109946  paid: 0  pps: 0.0366488  address: Pm8WVX1EmKNfW5X7gNMJjsEtv8juYM5kMB  hpm: 6.96984
sending 0120b750e69366bef5e1da4984dc92c5625fa9e142ddd440205dc1de44c27e91

The stats been wiped after I added batch of nodes.

Quote from: bytemaster on November 10, 2013, 02:40:54 pm

Quote from: Proto on November 10, 2013, 02:36:52 pm

Very risky move. If you look at how protocol changes in other altcoins have been handled, where has always been a grace period of at least a couple of days. This gives all miners the time needed to update to a newer version.

What is going to happen if you don't get the majority of miners to adopt the new protocol in time?

That said, I've updated my miners (300+ cores) to the new protocol version. Lets hope that we get through this smooth.

I have a pool with 3000 miners that has migrated and the other major pool has too.   

Solo mining already takes a week so only 10% of the solo miners will be effected because the rest would not have found anything anyway.  If the difficulty adjusted as it should then these solo miners also wouldn't have gotten anything.  I think it will be smooth as these things go.

That is not how this works. All solo miners with the old version of the miner can be seen together as one entity with a certain hash rate. It doesn't matter that some people are not getting any blocks, some will. And its not only miners who have to upgrade, also people who just use the software to make transactions.

This could be ugly:

The old miners will just make an 4x adjustment. They accept any blocks whether it be the ones generates with lower diff (4x increase) or higher diff (32x increase max).

The new miners reject blocks with lower diff (the ones with 4x adjustment), because these blocks don't match the new requirement. However they will produce blocks much slower than the old version of the miner, so many people using an older version of the software will make invalid transactions!

Thus: Any payments made with an older version of the client could get lost and someone falling for that could easily be scammed.