All of my unpaid (and paid) balances were wiped clean upon transition, even though I'm not sticking multiple miners on the same address anymore.  Is this the same for everyone?

I migrated the database and have a backup of the state it was when I shut down.  I will make you whole if you provide me your pub key.

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 planned pre-fork, then only 2.5% of the solo miners will lose a block and with the orphan rate you would have to assume that only 1.25% of solo miners will lose.

On the other hand the fork gives these solo miners a chance to win more over the longer term rather than having it all go to early adopters who know how to spawn up VPS cloud mining.

Quote from: bytemaster on November 10, 2013, 02:24:23 pm

Quote from: RejectKid on November 10, 2013, 02:19:04 pm

Quote from: bitbully on November 10, 2013, 02:17:08 pm

Hard forking like this is pretty messed up considering it gives a huge advantage to the initial miners, like magnitudes worth. This is wrong. If anything the fork should be a brand new blockchain.

early bird gets worm

At the rate we were going 50% of the money supply would have been mined out in the first 2 weeks...  not only is this bad for late comers, it was bad for Invictus because our mining strategy was based upon a longer mining window.  Perhaps that is selfish, but Invictus is ultimately the one providing backing to ProtoShares.     THe chain was operating outside of spec, this is a bug fix.

Ah gotcha.  well thats alright with me.  I'm just excited to be part of a new "type" of coin all the different altcoins have some potential but ultimately I dont see them being better than the original of that "type" of coin.  so the introduction of SHA512 to the mix is cool to me, and then can't wait for the bitshare...merger, changeover, w/e you wanna call it.  I think thats supposed to be in Jan of 2014?

BitShares will come as soon as we can, but we are not going to rush it because there is too much on the line.   Keyhotee ID launches Jan 01.  BitShares beta will probably be closer to march unless I can get some good devs to join the team!  The point of ProtoShares was to bootstram the community and give everyone an interest in the success of BitShares

Hard forking like this is pretty messed up considering it gives a huge advantage to the initial miners, like magnitudes worth. This is wrong. If anything the fork should be a brand new blockchain.

Actually, this fork is designed to slow the block production rate to give late comers more opportunity and to prevent early miners from running away with it all with 30 second blocks!

Quote from: bytemaster on November 10, 2013, 02:02:45 pm

I am moving the pool to 192.241.150.158 as part of this transition... so I can clone/scale as necessary.   

The pool machine was being overloaded anyway, please take some time to update your miner scripts to point at the new pool location.

the current script only needed (for example)

POOL_MINER.EXE the-iland.net Pdr84TXMcFSLPL2LezDQtrREfnXmBHGFkj

so will it be  this \/\/ now?

POOL_MINER.EXE 192.241.150.158 Pdr84TXMcFSLPL2LezDQtrREfnXmBHGFkj

Yes

I am moving the pool to 192.241.150.158 as part of this transition... so I can clone/scale as necessary.   

The pool machine was being overloaded anyway, please take some time to update your miner scripts to point at the new pool location.

unable to connect....
why?
help me ~~~~~

You could read the past couple of posts.... and know exactly why.