[ANN][WAS][WeAreSatoshi] | X11 | Hybrid PoS/PoW | Trading on C-Cex.com

[AmericanComputerNerd]

535,710   is what the explorer says...    both of my clients stopped syncing earlier today. I have tried many restarts and re-syncs.   I cant get but block number 1 to sync.....  

It appears that the v1 chain was attacked earlier this morning.  MrData has published new source which adds checkpoints to resolve the issue.  Binaries are not yet available for this fix.

More to come...

New Win32 binaries have been distributed to resolve this issue.  Unfortunately, the block chain may need to be deleted and re-downloaded to solve the freeze-up...  Try the binary first, if that fails to sync then clear your block chain and re-download.

I apologize for the inconvenience this has caused anyone.  Please let me know if a new v1 Mac is needed, or not.  Is anyone still using a Mac QT for v1?

Follow the download links on the OP or http://www.was.club/.

[AmericanComputerNerd]

In some positive news, thanks to Karimdr2 we have a v2 Mac QT.  Thank you!

Mac v2 QT - https://github.com/WeAreSatoshi/WeAreSatoshi-Binaries/blob/master/WeAreSatoshi-2.0.0.0-OSX-QT.dmg?raw=true

[hashy]

Yeah That did not work....     now  it won't even sync block #1    

{
"version" : 89909,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 0,
"timeoffset" : 0,
"connections" : 11,
"proxy" : "",
"difficulty" : 0.00024414,
"testnet" : false,
"keypoololdest" : 1394319473,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : "Coin Swap to WAS v2 is active now. See http://www.was.club for instructions."
}

[MrData]

Yeah That did not work....     now  it won't even sync block #1      

What peers are you connected to? Do you see any errors in your debug.log?

[hashy]

I dont see any errors..   I will try to flush my peers.dat,  just don't know what else to do.... 
 

[hashy]

I dont see any errors..   I will try to flush my peers.dat,  just don't know what else to do.... 
 

I figured It Out   Forgot to flush the chainstate folder...  it was that or muh peers.dat    it's syncing now 


Thanks for the binarys...  compiling a client on the only linux box i have up is sloooooooow....       Damn Pentium3  lmao   


now to do it all again on the other box...   

[794259332]

need more exchange..

[cuke]

MrData has published new source which adds checkpoints to resolve the issue.

Where is the new source published? Github appears to be 3 days old.

Update: Github is updated. just needed to reload the page.

[cuke]

Built the new v1 source successfully. During the new sync, everything goes well for a few minutes then sync stops and memory usage climbs until eventually the app quits. Restarting just repeats the same. Needed a few restarts to get the full sync. I noticed this yesterday (memory usage) when my coinswap was delayed.

Could this be a sign that the attack is ongoing.

[MrData]

The bad blocks are probably still floating around the network yeah, I don't think anyone is actively trying to mess with it anymore. Just as a test I've resynced v1 a couple of times but I can't get it to crash or anything.

Built the new v1 source successfully. During the new sync, everything goes well for a few minutes then sync stops and memory usage climbs until eventually the app quits. Restarting just repeats the same. Needed a few restarts to get the full sync. I noticed this yesterday (memory usage) when my coinswap was delayed.

Could this be a sign that the attack is ongoing.

[hashy]

The bad blocks are probably still floating around the network yeah, I don't think anyone is actively trying to mess with it anymore. Just as a test I've resynced v1 a couple of times but I can't get it to crash or anything.

Built the new v1 source successfully. During the new sync, everything goes well for a few minutes then sync stops and memory usage climbs until eventually the app quits. Restarting just repeats the same. Needed a few restarts to get the full sync. I noticed this yesterday (memory usage) when my coinswap was delayed.

Could this be a sign that the attack is ongoing.

just so ya know  i had similar issues  but  my clients run on win7 32bit boxes...   so its prolly the lame ram cut off that don't help me   

[karimdr2]

In some positive news, thanks to Karimdr2 we have a v2 Mac QT.  Thank you!

Mac v2 QT - https://github.com/WeAreSatoshi/WeAreSatoshi-Binaries/blob/master/WeAreSatoshi-2.0.0.0-OSX-QT.dmg?raw=true

You're welcome

Donations are welcome too  
WAS: wWs2jXDTZ4BAPpH8TFbVUKXtiUeZPxUdCX

[brian_nguyen]

...

You're welcome

Donations are welcome too  
WAS: wWs2jXDTZ4BAPpH8TFbVUKXtiUeZPxUdCX

What's the donation address about? Sent you some WAS.

[deadreply]

hi
im unable to transfert my WAS v1 to my WAS v2 Wallet
every time the v1 client crash...

always at the same place when i click on send...
Runtime error !!.....

[MrData]

hi
im unable to transfert my WAS v1 to my WAS v2 Wallet
every time the v1 client crash...

always at the same place when i click on send...

If you send me your wallet.dat and the v2 address you want the coins sent to I can do the swap for you.

[karimdr2]

...

You're welcome

Donations are welcome too  
WAS: wWs2jXDTZ4BAPpH8TFbVUKXtiUeZPxUdCX

What's the donation address about? Sent you some WAS.

Hey, thank you.
Just for kidding, what's happened to the 0.40 WAS?  

[brian_nguyen]

...

Hey, thank you.
Just for kidding, what's happened to the 0.40 WAS?  

Man has to keep something for himself - speaking the network transaction keeper.

[brian_nguyen]

Buy order is building up on RT... slowly but steady

[MrBrew]

The bad blocks are probably still floating around the network yeah, I don't think anyone is actively trying to mess with it anymore. Just as a test I've resynced v1 a couple of times but I can't get it to crash or anything.

Built the new v1 source successfully. During the new sync, everything goes well for a few minutes then sync stops and memory usage climbs until eventually the app quits. Restarting just repeats the same. Needed a few restarts to get the full sync. I noticed this yesterday (memory usage) when my coinswap was delayed.

Could this be a sign that the attack is ongoing.

I got around 2000 WAS during the attack I won't try to redeem them.

I was getting blocks with 300 WAS during the attack.  I upgraded to the latest client and getting 0 WAS again.

[MrData]

The bad blocks are probably still floating around the network yeah, I don't think anyone is actively trying to mess with it anymore. Just as a test I've resynced v1 a couple of times but I can't get it to crash or anything.

Built the new v1 source successfully. During the new sync, everything goes well for a few minutes then sync stops and memory usage climbs until eventually the app quits. Restarting just repeats the same. Needed a few restarts to get the full sync. I noticed this yesterday (memory usage) when my coinswap was delayed.

Could this be a sign that the attack is ongoing.

I got around 2000 WAS during the attack I won't try to redeem them.

I was getting blocks with 300 WAS during the attack.  I upgraded to the latest client and getting 0 WAS again.

Did they actually make it into the blockchain? The v1 client even pre-patch should have rejected any >0 reward blocks (assuming it was running 0.8.99.9), especially when it was back on the right side of the hardfork.