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

[chronicsky]

UPDATE:

I've put out a request for "DEV-Coder" assistance.
I'll let you know what the response is as SOON as I get a reply back.

I completely trust this person and I need you folks to put your trust into me that I will try to find somebody to assist us and not hurt us.

Right now, we are completely flying under the "radar" so I don't see anybody trying to come in and screw us.

I just need you folks to stand STRONG and let me try to figure out who can really help us.

The LAST thing I want is another LAME ASS "DEV-Coder" to come in and then just completely disappear, like the last 2 DEV's have.

If my request for a DEV-Coder goes un-answered and/or the person declines - I'll let you know and I'll try again - ugh

@chronicsky - get your wallet warmed up - but - as I told this person - YOU decide who gets paid ANY bounty and how much. I personally think that bounties should not be paid until we see some results - and this person will completely understand - more so since we are not even on an exchange right now.


Cross you fingers folks......


Let's hope for a positive result :-D




p.s. - I didn't ask for much - only the basic's - but - My idea of basic's might prove to be a really BIG advancement compared to where we are now.......

Wish us good fortune :-D

Amazing! Good luck to all of us!
Am always ready with my wallet

[1714783842]

1714783842

[1714783842]

1714783842

[1714783842]

1714783842

[chronicsky]

@chronicsky

LOL - I so love your commitment :-D

\o/ WOOT !!!!

Hhahaha

BTW about you asking to trust you on this. You don't really need to ask anything on that. I Trust you

[chronicsky]

Uh- yea - As much as I hate to say-

We are a DEAD coin - going NO where

AND - it's over -


I sent out 5 more requests and ALL request come back as -

DEAD SHIT COIN


Sorry guys - hold your wallet.dat files just in case but nobody wants to help



ugh

We don't want nobody!
We ourselves are enough, ain't we?

[maki]

What are the technical problems, specifically, that KSC is having now?  

I did prefer the simplicity of the original Ksc chain. But still, it seems to be running ok finding blocks with POS.  All we need are some nodes holding KSC in the wallet.

I keep several old chains moving.  I consider them more forgotten than dead.  I've seen dead coins... I mean, when they are dead they are absolutely screwed up technically and nothing but a dedicated dev can bring them back.  66 Coin was like that... after it mined the last 66 coin a month ago, everything crashed. A dev has been working on it try and revive it, but there is an example of a coin that truly was dead without a dev.  Most coins can continue on for years without a dev, so long as they were totally f'ed up to start with.

If anyone wants to just get out, I'll buy them for .02 btc. It'll help me stake more coins to generate more pos blocks.

[almightyruler]

What are the technical problems, specifically, that KSC is having now?  

The problem I had was that I was unable to sync from scratch. My client started banning nodes at the hard fork point, probably because people had not upgraded their client and kept mining on the "old" chain, effectively creating their own private fork. The effective hard fork point of the network is likely beyond block 82000.

Someone needs to decide on the correct "official" chain, and change the hard fork point in the source code to suit, so that new clients can sync. I'm unable to do this since I don't have a consistent blockchain (chicken and egg)

[chronicsky]

So busy week and this is what i see
So is it dead? So much wait and work for nothing?
I don't really care about the market value at this point but i wanted to see it alive again man !
Anything we can do ?

[chronicsky]

There's not much that can be done.....

Nobody wants to help......
I would have liked to see it restored but...... not even sync'ing now......

it feels bad
Can't we work out something together?

[crocko]

Hello folks !

I was busy and didn't I do not know what has happened.
At one point everything was fine, but now I am stuck at block 188210 (I run version 1.1.0.0)
Please don't give up now !
Do you know that the Bitcoin price is inversely related to the dollar ??
Right now the US dollar is on peak but this will not last forever! And the Bitcoin reward per block will be 12.5 BTC very soon !
If you don't have pile of cash to buy BTC or you don't have ASICs (+free electricity !!!), best way to earn something is to convert some crypto to BTC.
Please remember that KSC it is a RARE coin (only 1001 !!) like 42, for example.
And 42Coin worth right now 4 (four!) Bitcoins !! http://coinmarketcap.com/currencies/42-coin/
Be smart and don't give up ! 
Let the KSC blockchain to run again then we must be go to an exchange !

[chronicsky]

@JennySmith , can you get that node back up man ? We can still do it

[maki]

In Kasmircoin.conf  file, put

addnode=70.40.55.248

Then restart the wallet.

[chronicsky]

In Kasmircoin.conf  file, put

addnode=70.40.55.248

Then restart the wallet.

Cool! thanks
Am syncing

[crocko]

In Kasmircoin.conf  file, put

addnode=70.40.55.248

Then restart the wallet.

Hello !

Maybe it's only me, I used the above settings but I can't sync anymore...

My wallet: v1.1.0.0, Widows7 64bit
Block height: 190436

[maki]

this thing is totally, completely dead.

Mulling the experiment of rolling back to the old 0.8 client. there are still 3 or 4 connections up for it.

[chronicsky]

this thing is totally, completely dead.

Mulling the experiment of rolling back to the old 0.8 client. there are still 3 or 4 connections up for it.

This is so sad

[crocko]

this thing is totally, completely dead.

Mulling the experiment of rolling back to the old 0.8 client. there are still 3 or 4 connections up for it.

So what version is the "official" one ?
v1.1 or v1.0.8 ?

[testcoin]

So what version is the "official" one ?
v1.1 or v1.0.8 ?

The last official version released by the dev is v1.1.0.0

this thing is totally, completely dead.

Mulling the experiment of rolling back to the old 0.8 client. there are still 3 or 4 connections up for it.

You should clearly know that rolling back (=rewwriting history) is not an option

But why you don’t move back your node to support the official blockchain?

[smarterhash]

coin is dead - no exchanges

[testcoin]

If you have access to your internet connection - Modem and Routers

Access Port-Forwarding
Input our 'intra-net' IP address of your Device that has your KSC-Qt wallet
[In Windows, run a command line and type in: ipconfig /all
....to find your local IP address]
OPEN PORT: 10011
and
PORT: 11010

Depending on your Modem, you will probably have to set up two Port Forwarding lines to do this.

This will allow for incoming signals from other wallets and act more like a Node
This should work nicely....


Try it and then post here so I can watch it....
ALSO

Unlock your wallet(s) to Stake

In theroy - the POS difficulty should rise :-) and the system should start to move nicely
...well - way better then it is now



Current Block is: 190451

What is your node??

My block height is still 190432 as no any node can be seen in the network

I'd unlock my wallet to stake only if I could connect to you

[chronicsky]

190211

0 COnnections

.conf looks like this


rpcport=10011
rpcport=11010
port=z
addnode=68.44.77.62
addnode=68.44.77.62
addnode=107.170.120.197
addnode=198.23.242.217
addnode=188.226.180.141
addnode=115.28.129.207
addnode=70.40.55.248



Am i doing anything wrong ?

[crocko]

Hello !

I use the version 1.1 on Win7 64bit and this config file:

rpcuser=anythingyouwant
rpcpassword=anythingyouwantbutnotliketheaboveandlong
rpcallowip=localhost
rpcconnect=localhost
rpcport=10011
rpcport=11010
addnode=68.44.77.62
addnode=68.44.77.62
addnode=107.170.120.197
addnode=198.23.242.217
addnode=188.226.180.141
addnode=115.28.129.207
addnode=70.40.55.248
daemon=1
server=1
listen=1
maxconnections=50

My wallet don't sync, I am stuck at block 189173.
I have no progress despite I am connected even several hours per day to the KSC network.
Please help me !