Everyone that's showing a lower block count #, are you on a version of the client prior to my Github commits of about an hour ago? I'm trying to determine now whether everyone having problems is or isn't on the client with the updated scrypt-jane library that I pushed to Github within the last hour. If anyone showing the lower block count # did not upgrade, then it isn't connected to the changes. If everyone showing the lower block count # did upgrade, then I'll revert the last 2 commits in the Github repository.

Bitcoin Megastore and eule, did you upgrade in the last hour?

I am running the original client that was put up for download when the coin was announced. I am currently showing 91100 blocks total.

I am running the original client that was put up for download when the coin was announced. I am currently showing 91100 blocks total.

In that case the reorg is coincidental and my Github commits did not break compatibility with the existing blockchain.

At this point, I'm going to say it was a timing coincidence with a failed 51% attack possibly. Someone mining off-network attempting a 51% attack may have panicked when they saw me push the checkpoint at block 90000.

Everyone that's showing a lower block count #, are you on a version of the client prior to my Github commits of about an hour ago? I'm trying to determine now whether everyone having problems is or isn't on the client with the updated scrypt-jane library that I pushed to Github within the last hour. If anyone showing the lower block count # did not upgrade, then it isn't connected to the changes. If everyone showing the lower block count # did upgrade, then I'll revert the last 2 commits in the Github repository.

Bitcoin Megastore and eule, did you upgrade in the last hour?

i have a lower block count and im on the alpha client not the new beta version

and i think its unrelated to your update but YAC it has been very strange in the last 16 hours

In that case the reorg is coincidental and my Github commits did not break compatibility with the existing blockchain.

At this point, I'm going to say it was a timing coincidence with a failed 51% attack possibly. Someone mining off-network attempting a 51% attack may have panicked when they saw me push the checkpoint at block 90000.

On that note, are there any win64 binaries available anywhere for these new client builds?

Someone mining off-network attempting a 51% attack may have panicked when they saw me push the checkpoint at block 90000.

Where does one vote for best alt dev?

𝖄𝖆𝖈: YF3feU4PNLHrjwa1zV63BcCdWVk5z6DAh5 · 𝕭𝖙𝖈: 12F78M4oaNmyGE5C25ZixarG2Nk6UBEqmeɎ: "the altcoin for the everyman, where the sweat on one's brow can be used to cool one's overheating CPU" -- theprofileth

No, I have Win32 custom built by some guy and it is few days old. I think what happened is that some miner upgraded to newest code, which isbroken somewhere.

So far it looks like everyone is actually on the same block # and blockchain that I'm on with the newest code, so most likely something else occurred unrelated to the code changes.

Anyone have a copy of their debug log going back a couple hours so we can get a better look at what happened? I see eule posted the reorg itself but I'd like to get a look at what came before it. I don't have a debug log handy since I wasn't running yacoind continuously while I was preparing the commits to Github.

PoS blocks 91036 and 91037 were staked by someone operating off-network (whether intentionally or unintentionally) and then reintroduced to the network, triggering the reorg and orphaning 75 blocks. Anyone here have really good familiarity with the Novacoin PoS code?

PoS blocks 91036 and 91037 were staked by someone operating off-network (whether intentionally or unintentionally) and then reintroduced to the network, triggering the reorg and orphaning 75 blocks. Anyone here have really good familiarity with the Novacoin PoS code?

Is this may be the reason for my problem?This transaction is still not confirmed, and my wallet always says to stake=0 after -rescan and -reindex. And impossible to find this transaction in yacexplorer.

Staked coins must wait 520 blocks before they can return to balance and be spent. When you generated this proof-of-stake block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, it will change to "not accepted" and not be a valid stake. This may occasionally happen if another node generates a proof-of-stake block within a few seconds of yours.

well, if there's only 36MH on the network, then there's the problem, yac.ltcoin.net is currently reporting is has 37 MH/sec... Actually, this could be problematic as well as the mean hashrate is 72 MH/sec as reported on yacexplorer.tk

well, if there's only 36MH on the network, then there's the problem, yac.ltcoin.net is currently reporting is has 37 MH/sec... Actually, this could be problematic as well as the mean hashrate is 72 MH/sec as reported on yacexplorer.tk

well, if there's only 36MH on the network, then there's the problem, yac.ltcoin.net is currently reporting is has 37 MH/sec... Actually, this could be problematic as well as the mean hashrate is 72 MH/sec as reported on yacexplorer.tk

in my client it was 72MH 5 hours ago and didnt drop untill the last 2 or more hours to 36MH and now its back up so...