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

maki

sr. member

Activity: 298

Merit: 250

Quote from: chronicsky on February 03, 2015, 03:38:00 AM

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://bitcointalksearch.org/topic/m.10305204

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=
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.

chronicsky

legendary

Activity: 2828

Merit: 1222

Just looking for peace

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?

maki

sr. member

Activity: 298

Merit: 250

Should we attempt a rollback on February 5, after 18:00 UTC?

That should give anyone smarter a few days to get the new blockchain MOVING. (Not just synched up, but actually moving blocks).

If I don't see anyone posting an effort to fix the new block chain, I'll put up some old clients and we can try it.

crocko

hero member

Activity: 826

Merit: 1000

'All that glitters is not gold'

I found a solution for the lack of an exchange for KSC!
Just discussed on the Hashtalk forum (https://hashtalk.org) to add KSC to https://fastxpy.com/
This provide services like https://shapeshift.io/ : you can exchange your coins for another altcoin, even on small quantities.
You can try to talk with the ShapeShift too in order to add KSC.

In the mean time please tell me which version is working or is the "official one: 1.1 or 0.8.6.2 ??

bitsheva

newbie

Activity: 35

Merit: 0

try to sync the last (1.1) client, mine is working now

crocko

hero member

Activity: 826

Merit: 1000

'All that glitters is not gold'

ready for the 0.8.6.2 clients !

maki

sr. member

Activity: 298

Merit: 250

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 )
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
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.

raimch89

legendary

Activity: 1169

Merit: 1000

dead

crocko

hero member

Activity: 826

Merit: 1000

'All that glitters is not gold'

any progress ?

maki

sr. member

Activity: 298

Merit: 250

Quote from: almightyruler on January 21, 2015, 01:31:01 AM

Quote from: maki on January 20, 2015, 10:33:10 PM

Quote from: almightyruler on January 20, 2015, 08:01:19 PM

I compiled from source. What's V1 and V2? Are you referring to different client versions, or an inadvertent network fork?

The 0.8 client is the old chain. Pre-fork.

What I have been calling v1 client is the last 1.0x client (post fork) I can find for Windows. I obtained it here, https://github.com/kashmircoin/kashmircoin/tree/master/release
I'm finding the V1.0 wallet to be very unstable on Windows.

Does your wallet have any connections?

I downloaded the source from https://github.com/kashmircoin/kashmircoin/ . I'm not going to try to guess which one that is.

As per my above message it has found peers, but we seem to be banning each other because we disagree about block 82000.

I haven't read 60 pages of this thread. Was block 82000 an issue back in August 2014?

What I know about the magic in block 82000 I find in the OP:

- Digishield will be activated at block 82000.
- After block 82100 miners will get 0,003 KSC for every mined block.
So there is plenty of room for disagreement at block 82000 over block reward and difficulty.

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: maki on January 20, 2015, 10:33:10 PM

Quote from: almightyruler on January 20, 2015, 08:01:19 PM

I compiled from source. What's V1 and V2? Are you referring to different client versions, or an inadvertent network fork?

The 0.8 client is the old chain. Pre-fork.

What I have been calling v1 client is the last 1.0x client (post fork) I can find for Windows. I obtained it here, https://github.com/kashmircoin/kashmircoin/tree/master/release
I'm finding the V1.0 wallet to be very unstable on Windows.

Does your wallet have any connections?

I downloaded the source from https://github.com/kashmircoin/kashmircoin/ . I'm not going to try to guess which one that is.

As per my above message it has found peers, but we seem to be banning each other because we disagree about block 82000.

I haven't read 60 pages of this thread. Was block 82000 an issue back in August 2014?

maki

sr. member

Activity: 298

Merit: 250

Quote from: almightyruler on January 20, 2015, 08:01:19 PM

I compiled from source. What's V1 and V2? Are you referring to different client versions, or an inadvertent network fork?

The 0.8 client is the old chain. Pre-fork.

What I have been calling v1 client is the last 1.0x client (post fork) I can find for Windows. I obtained it here, https://github.com/kashmircoin/kashmircoin/tree/master/release
I'm finding the V1.0 wallet to be very unstable on Windows.

Does your wallet have any connections?

almightyruler

legendary

Activity: 2268

Merit: 1092

I compiled from source. What's V1 and V2? Are you referring to different client versions, or an inadvertent network fork?

maki

sr. member

Activity: 298

Merit: 250

I don't know guys...
V1 has now stopped running here. Now all I get is C++ runtime errors. I've reinstalled it 4 times, but still broken. Uninstalled/reinstalled C++ runtime libraries, spent way too much time trying to resolve it. V1 is just broken for me.

Is anyone else besides almightruler running a V1 client right now? Can you guys connect? What block are you on?

almightyruler

legendary

Activity: 2268

Merit: 1092

My freshly installed client managed to find 70.40.55.192, but banned it at block 82000 for misbehaving (incorrect proof-of-work).

This coincides with what appears to be a hard fork in the code to change the retargeting algorithm, so I guess that means 70.40.55.192 (and possibly other parts of the network) went past block 82000 before running the new client.

I presume this is a known issue discussed in earlier pages, possibly requiring a workaround such as a blockchain archive, so that syncing clients don't try to validate certain blocks and ban the peers which offer them?

maki

sr. member

Activity: 298

Merit: 250

I have the OLD chain prior to the fork, and it is moving. I ran a few hundred blocks last night, so it is available.

But lets try as SwissCex says, and again try to jump start the NEW chain.
I no longer have the new Windows wallet. The devs have removed the new wallet from the OP.
Will someone post the NEW windows wallet for me and I will try one more time to move the new chain. I don't know if Scrypt miners will work past the end of POW, but we can try.

Please also install the New wallet, and let it run. Then go to whatismyip.com, and post your ip address so I can try to get get connections through the connect= parameter in the conf file.

Swisscex

sr. member

Activity: 328

Merit: 250

Quote from: maki on January 17, 2015, 08:45:47 PM

Hello SwissCex,

We are not happy with your decision to destroy Kashmircoins, KSC, that were traded on your market.
The devs poor actions are separate from the community.
Because KSC is rare at just 1000 coins, we ask you to hold off destroying them. We will try to appoint someone who can distribute the coins back to the community, or find a way to reactivate the network, or rollback the fork.

The community is as surprised as you are at the problems, and we need time to resolve it. Please remove the deadline threat of destroying the coins on your market. These coins are the legal property of their owners, purchased on your exchange and you were compensated for that service. These coins must not be destroyed. Put them in storage if you must, but do not destroy them.

come talk to us if you want to take it out of this thread.
https://bitcointalksearch.org/topic/m.10189756

Dear KSC community,

I am here to find a solution for your coins.

We do not destroy any coins on purpose. This is not even possible without a working network.

So any suggestions how we can solve it? Easiest would be if you would start mining again.

Best regards,

Kevin

SWISSCEX

maki

sr. member

Activity: 298

Merit: 250

Mangledblue, IMjim or croko, you guys are senior here. I trust any of you.

Instead of letting SwissCex destroy all of our KSC coins, I would nominate one of you senior, long time Kashmircoin community members to contact SwissCex and ask for the private keys for KSC.

Let them know that we don't want them to destroy the KSC they hold. They should either hold the private keys until things get back, or turn them to you as the community rep.

I would rather risk you stealing the coins, instead of knowing that Swissex has destroyed them all.

Better ideas?

--update
I started this discussion with SwissCex, and asked them to come talk to us.
https://bitcointalksearch.org/topic/m.10191084

maki

sr. member

Activity: 298

Merit: 250

Quote from: ?? on ??

At this time I am against any roll-back...........................

Ok, but the clock is ticking. Just got this email from SwissCex:

------

IMPORTANT: KashmirCoin will be removed.

Dear customer,

We want to inform you that KashmirCoin will be removed from SWISSCEX in 7 days. This coin will be removed in 7 days and afterwards all coins will be lost permanently.

Coin name: KashmirCoin (KSC)
Date of removal: 23.01.2015

This coin is completely inactive and therefore withdrawals are not possible.

-------

I don't know if a rollback will save your coins on SwissCex or not. But is there any other plan on the table, that can be implemented before January 23?

crocko

hero member

Activity: 826

Merit: 1000

'All that glitters is not gold'

I hope some serious dev will finally fix this problem.

Topic: [KSC] KASHMIRCOIN - MANDATORY UPDATE! - - - "BURIED" POW - cWallet - 50% POS - page 10. (Read 123084 times)