[KSC] KASHMIRCOIN - MANDATORY UPDATE! - - - "BURIED" POW - cWallet - 50% POS

[chronicsky]

Hello! has been so many day, i missed alot , my laptop was broke , so i had uninstalled every wallet and had backed it up
now it's good and i don't prefer my wallet on other PC's
So good to hear and see people working so hard for this coin
I will like to help too please
Can you please tell me what to do , i have back up of my wallet(latest ver i think)
What next?

[1715503556]

1715503556

[maki]

Hello! has been so many day, i missed alot , my laptop was broke , so i had uninstalled every wallet and had backed it up
now it's good and i don't prefer my wallet on other PC's
So good to hear and see people working so hard for this coin
I will like to help too please
Can you please tell me what to do , i have back up of my wallet(latest ver i think)
What next?

Anyone who wants to attempt the rollback can start with this thread.
https://bitcointalk.org/index.php?topic=550728.msg10305204#msg10305204

If you setup the 0.8 client early, do not download any blocks beyond 70k for now.  On Feb 5, I will start mining the old blockchain, and will try to keep new nodes from connecting.   The chain I will be mining will need more 0.8 nodes than version 1.x nodes. Eventually the "old" chain will be long enough to overtake the "new" chain and we will be in the clear, but it will take probably a month at least.  So keeping old 0.8 wallets online will be very helpful.

Your new KSC wallet must not sync past block 75000 for now.

For Windows users, your Kashmircoin folder can be found by typing the Windows Key+R, then enter %appdata%
Find the Kashmircoin directory.

Put a text file there called Kashircoin.conf that contains these lines:

addnode=<will give this to you on Feb 5.>
maxconnections=1

---

Later I will collect a list of 0.8 client addresses and you can update the Kashmircoin.conf file with more 0.8 nodes.

[bitsheva]

Hello! has been so many day, i missed alot , my laptop was broke , so i had uninstalled every wallet and had backed it up
now it's good and i don't prefer my wallet on other PC's
So good to hear and see people working so hard for this coin
I will like to help too please
Can you please tell me what to do , i have back up of my wallet(latest ver i think)
What next?

Anyone who wants to attempt the rollback can start with this thread.
https://bitcointalk.org/index.php?topic=550728.msg10305204#msg10305204

If you setup the 0.8 client early, do not download any blocks beyond 70k for now.  On Feb 5, I will start mining the old blockchain, and will try to keep new nodes from connecting.   The chain I will be mining will need more 0.8 nodes than version 1.x nodes. Eventually the "old" chain will be long enough to overtake the "new" chain and we will be in the clear, but it will take probably a month at least.  So keeping old 0.8 wallets online will be very helpful.

Your new KSC wallet must not sync past block 75000 for now.

For Windows users, your Kashmircoin folder can be found by typing the Windows Key+R, then enter %appdata%
Find the Kashmircoin directory.

Put a text file there called Kashircoin.conf that contains these lines:

addnode=<will give this to you on Feb 5.>
maxconnections=1

---

Later I will collect a list of 0.8 client addresses and you can update the Kashmircoin.conf file with more 0.8 nodes.

But i bought some coins on Swisscex after block 75000, even after 90000. If we switch to 0.8.6 back i will lose a lot of money. Also in this case KSC will be just a useless shit scrypt coin without POS or other features, even without this pink wallet. Can someone just fix 1.1?

[chronicsky]

I still can't get the "new" client to run.

The older 0.8.6.2 client still runs.

If it were up to a vote, I say lets roll back.  That, or we end up with nothing.

Here's a plan. If you have a better one, go ahead and chime in.

A rollback would look like this:
1 back up your version 1 wallet.
2 dump your version 1 private keys. (dumpprivkey <your ksc address> )
3 uninstall kashmircoin 1
4. install kashmircoin 0.8.6.2. It is available at https://mega.co.nz/#!yBNS0bxa!XjEAyAX5Q876M1hUr39uAFHe8FusdGZIH2Z9FbJ0oJI
5 import your private keys    (importprivkey <your ksc private key>
6  take your wallet offline for the moment so you don't down load the bad blockchain. You can download the first 80k blocks, but no more than that!
7 I will cut the blockchain back to about block 82000.

8 When there's a few of you ready, lets pick a date, put our 0.8.6.2 clients online and sync up.
    I will give you an connect= address for your kashmircoin.conf. You should limit connections to 1 (maxconnections=1) at first, just to prevent any version 1 clients on the network from connecting and causing issues.
9. We'll let it run for a ways until our chain exceeds the new chain.
10. If i am the only miner, I will put 75% of the mined coins into a compensation fund. Perhaps SwissCex can work with us and we'll try to make some people whole who lost coins on the new fork.  We will need to make this part up as we go along. If I'm not the only miner, then there's not much I can do, but at least the blockchain will be moving.

As it always have been , the mega.co lonks never work for me , could you give me a mirror link

[athur0s]

Version 1.1 is working fine and blocks are comming in. So why do you want to make a rollback, that brings only new problems...

[IMJim]

I agree, a rollback would SUCK!  After everything this coin has gone through, it's best to just let it die if the current version cannot be fixed.  I don't know what the hell the point was with KSC the past few months, but it has caused everyone to lose any little faith they had left in this project.  Personally I see these devs and the people that took this over as just plain assholes........why the fuck string us on for months with so many updates just to up and disappear again?! 

Wasted our fucking time, money and resources.........all these updates got me involved in this shit again and I too more than doubled my holdings during this time........and now I am supposed to let that go, eat the time and money I put into this and roll back 3 months to an even crappier KSC.......no thanks!

As far as I'm concerned this project can rest in peace, along with the assholes that have strung us along this entire time!

[crocko]

My wallet version 1.1 stuck at 124943
No progress since couple hours ago ...

[crocko]

sync successful (v. 1.1)

[chronicsky]

sync successful (v. 1.1)

Hi! i missed alot , isn't V1.1 the latest one ?
Why is then are we going for 0.8

[crocko]

sync successful (v. 1.1)

Hi! i missed alot , isn't V1.1 the latest one ?
Why is then are we going for 0.8

The 0.8 client is the old chain. Pre-fork.
Somebody proposed that we shall return to the old chain, but it seems that the actual v1.1 it's OK.
Now let's focus to add KSC to an exchange or at least to ShapeShift.io

[chronicsky]

sync successful (v. 1.1)

Hi! i missed alot , isn't V1.1 the latest one ?
Why is then are we going for 0.8

The 0.8 client is the old chain. Pre-fork.
Somebody proposed that we shall return to the old chain, but it seems that the actual v1.1 it's OK.
Now let's focus to add KSC to an exchange or at least to ShapeShift.io

It would be best to get the swisscex wallet first , Since they kept the coin even when it was down
What is shapeshift?

[bitsheva]

sync successful (v. 1.1)

Hi! i missed alot , isn't V1.1 the latest one ?
Why is then are we going for 0.8

The 0.8 client is the old chain. Pre-fork.
Somebody proposed that we shall return to the old chain, but it seems that the actual v1.1 it's OK.
Now let's focus to add KSC to an exchange or at least to ShapeShift.io

It would be best to get the swisscex wallet first , Since they kept the coin even when it was down
What is shapeshift?

1.1 is almost OK, but if you're staking, your wallet can lose connections after several hours and start mining "solo" (self-forking). The wallet just goes fork itself 
It's not a serious problem for the whole blockchain, but it's annoying if you want to stake 24/7. We need someone to fix it ASAP. It is the only 1.1 bug i know. Or i am wrong?

[bitsheva]

sync successful (v. 1.1)

Hi! i missed alot , isn't V1.1 the latest one ?
Why is then are we going for 0.8

The 0.8 client is the old chain. Pre-fork.
Somebody proposed that we shall return to the old chain, but it seems that the actual v1.1 it's OK.
Now let's focus to add KSC to an exchange or at least to ShapeShift.io

I like ShapeShift.io, it looks very promising. How can we get listed there?

[crocko]

Wallet version 1.1 stuck at 124946
Again no progress since couple hours ago, no sync ...
Can a dev fix v.1.1 ?

[chronicsky]

Wallet version 1.1 stuck at 124946
Again no progress since couple hours ago, no sync ...
Can a dev fix v.1.1 ?

There are no dev's here
I will check my oold messages to see if i can get in touch with old Dev and see if any one of us capable here can take over

[maki]

Ok. If there's no support for a rollback I proposed, lets call it off.

[crocko]

I agree with a rollback!

[crocko]

Hello !
Any sing of life ?
Which version of the wallet you still use ? The 1.1 or the old ?

[almightyruler]

Where's the source of 1.1? https://github.com/kashmircoin/kashmircoin only mentions 1.0.5

[crocko]

Wallet version 1.1 still stuck at 124946