[ANN][CKS] Chicks | Current Supply @ 128,000 | PoS only @25% APR | masternodes!

[Testing Crypto]

i was on the forked chain deleted all data and added connect bit to the config
now stuck @  "blocks" : 50030 any ideas ?

   Can you post a copy of your .conf file? Did you resync with a new wallet.dat or the same one? I can see you on the network, but will need a little more info on why it stuck @ block 50030 & that has happen to me a few times (on other networks). I just resync with a new wallet.dat & then once it sync up to the top block & then close the application to swap with old wallet.dat. Also helps to keep new wallet.dat for the future, make several backups & then when your current wallet.dat gets bloated (around 1MB+) then transfer everything to the new wallet.dat you used to get resync. Make sure once you do get all syncd, you change the .conf file back to addnode= & remove the connect= only for the fresh sync.

Code:


{
"addr" : "86.184.84.190:36018",
"services" : "00000001",
"lastsend" : 1493331704,
"lastrecv" : 1493331403,
"conntime" : 1493331401,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 50030,  // try to start with a rescan=1 or a fresh wallet.dat (make sure to back it up first!!)
"banscore" : 0
}
]

[hexdump]

i was on the forked chain deleted all data and added connect bit to the config
now stuck @  "blocks" : 50030 any ideas ?

   Can you post a copy of your .conf file? Did you resync with a new wallet.dat or the same one? I can see you on the network, but will need a little more info on why it stuck @ block 50030 & that has happen to me a few times (on other networks). I just resync with a new wallet.dat & then once it sync up to the top block & then close the application to swap with old wallet.dat. Also helps to keep new wallet.dat for the future, make several backups & then when your current wallet.dat gets bloated (around 1MB+) then transfer everything to the new wallet.dat you used to get resync. Make sure once you do get all syncd, you change the .conf file back to addnode= & remove the connect= only for the fresh sync.

Code:


{
"addr" : "86.184.84.190:36018",
"services" : "00000001",
"lastsend" : 1493331704,
"lastrecv" : 1493331403,
"conntime" : 1493331401,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 50030,  // try to start with a rescan=1 or a fresh wallet.dat (make sure to back it up first!!)
"banscore" : 0
}
]

i think it worked
im at "blocks" : 56417,
can you confirm its correct height ?

[Testing Crypto]

i think it worked
im at "blocks" : 56417,
can you confirm its correct height ?

yes, block explorer looks good now too & doesn't have any scrambled blocks like before.

http://chicks.acc-pool.pw/

//any chance the block explorer could update a few points?
1.  "proof-of-work" : 1.05937409 < to > "proof-of-stake" : 0.00024414
2. add the network staking weight to the "Network (GH/s)" api
3. add the BTC Price with YoBit, Nova, or Tradesatoshi (or add a new tab Markets like other block explorers have)

//13 peers & around 7000 network staking weight

https://yobit.net/en/trade/CKS/BTC
Wallet status: Online (56465 blocks)

https://novaexchange.com/market/BTC_CKS/
Status    Online and in sync! Current height    56465

https://tradesatoshi.com/Vote
#1 135 votes

https://thecryptochat.net/chicks.php
Faucet Balance:
10.31995218 CKS 3683 payouts

ChickenIsland
https://littleworldofsatoshi.com/extra

[HarryPorter]

i think it worked
im at "blocks" : 56417,
can you confirm its correct height ?

yes, block explorer looks good now too & doesn't have any scrambled blocks like before.

http://chicks.acc-pool.pw/

//any chance the block explorer could update a few points?
1.  "proof-of-work" : 1.05937409 < to > "proof-of-stake" : 0.00024414
2. add the network staking weight to the "Network (GH/s)" api
3. add the BTC Price with YoBit, Nova, or Tradesatoshi (or add a new tab Markets like other block explorers have)

//13 peers & around 7000 network staking weight

https://yobit.net/en/trade/CKS/BTC
Wallet status: Online (56465 blocks)

https://novaexchange.com/market/BTC_CKS/
Status    Online and in sync! Current height    56465

https://tradesatoshi.com/Vote
#1 135 votes

https://thecryptochat.net/chicks.php
Faucet Balance:
10.31995218 CKS 3683 payouts

ChickenIsland
https://littleworldofsatoshi.com/extra

"1.  "proof-of-work" : 1.05937409 " - but it looks like POW is over, can not mine this coin any more, correct me if I am wrong.

so we got 123799.714 CKS coins in circulation for now, and inflation is coming only by POS with percentage 25% per year.

[Testing Crypto]

http://chicks.acc-pool.pw/

//any chance the block explorer could update a few points?
1.  "proof-of-work" : 1.05937409 < to > "proof-of-stake" : 0.00024414
2. add the network staking weight to the "Network (GH/s)" api
3. add the BTC Price with YoBit, Nova, or Tradesatoshi (or add a new tab Markets like other block explorers have)

"1.  "proof-of-work" : 1.05937409 " - but it looks like POW is over, can not mine this coin any more, correct me if I am wrong.

so we got 123799.714 CKS coins in circulation for now, and inflation is coming only by POS with percentage 25% per year.

Yes PoW ended a while ago, but the block explorer still shows that for stats & should be updated if possible.

[kurbeks]

Can anyone now tell correct correct addnodes? So it doesn sync properly to main chain and YoloBit.

[Testing Crypto]

Can anyone now tell correct correct addnodes? So it doesn sync properly to main chain and YoloBit.

  

{ "addr" : "94.23.102.99:10123", "services" : "00000001", "lastsend" : 1493822149, "lastrecv" : 1493822357, "conntime" : 1493822111, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 57442, "banscore" : 0 }, { "addr" : "13.93.84.61:10123", "services" : "00000001", "lastsend" : 1493822357, "lastrecv" : 1493822357, "conntime" : 1493822124, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 57442, "banscore" : 0 }, { "addr" : "90.225.61.229:10123", "services" : "00000001", "lastsend" : 1493822357, "lastrecv" : 1493822357, "conntime" : 1493822281, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 57444, "banscore" : 0 },

{ "addr" : "50.83.4.208:10123", "services" : "00000001", "lastsend" : 1493822357, "lastrecv" : 1493822357, "conntime" : 1493822315, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 57444, "banscore" : 0 }, { "addr" : "149.56.154.75:10123", "services" : "00000001", "lastsend" : 1493822615, "lastrecv" : 1493822615, "conntime" : 1493755278, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 57273, "banscore" : 0 }, { "addr" : "86.184.84.190:60158", "services" : "00000001", "lastsend" : 1493822615, "lastrecv" : 1493822615, "conntime" : 1493755306, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 57273, "banscore" : 0 },

{ "addr" : "169.0.231.41:21341", "services" : "00000001", "lastsend" : 1493822615, "lastrecv" : 1493822112, "conntime" : 1493755314, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 57273, "banscore" : 0 }, { "addr" : "88.88.166.130:52378", "services" : "00000001", "lastsend" : 1493822615, "lastrecv" : 1493822370, "conntime" : 1493755338, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 57273, "banscore" : 0 }, { "addr" : "178.121.121.90:8771", "services" : "00000001", "lastsend" : 1493822615, "lastrecv" : 1493822217, "conntime" : 1493755365, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 57273, "banscore" : 0 },

{ "addr" : "98.115.147.74:47010", "services" : "00000001", "lastsend" : 1493822615, "lastrecv" : 1493821697, "conntime" : 1493755382, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 57273, "banscore" : 0 }, { "addr" : "75.72.134.175:28685", "services" : "00000001", "lastsend" : 1493822615, "lastrecv" : 1493822615, "conntime" : 1493755619, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 57274, "banscore" : 0 }, { "addr" : "148.251.54.6:46702", "services" : "00000001", "lastsend" : 1493822615, "lastrecv" : 1493822612, "conntime" : 1493755684, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 57274, "banscore" : 0 },

{ "addr" : "217.175.119.125:21995", "services" : "00000001", "lastsend" : 1493822615, "lastrecv" : 1493821697, "conntime" : 1493756677, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 57278, "banscore" : 0 }, { "addr" : "90.225.61.229:54151", "services" : "00000001", "lastsend" : 1493822615, "lastrecv" : 1493822370, "conntime" : 1493807372, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 57284, "banscore" : 0 }, { "addr" : "185.11.195.45:56996", "services" : "00000001", "lastsend" : 1493822615, "lastrecv" : 1493822371, "conntime" : 1493819048, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 57432, "banscore" : 0 },

[anemol]

Can anyone now tell correct correct addnodes? So it doesn sync properly to main chain and YoloBit.

On my side, the chicks.conf file

Code:

connect=149.56.154.75:10123

Don't miss to delete the blockchain is you are already sync on the bad blockchain.


We are still waiting for a developer fix.  

[kurbeks]

Thanx both

[Testing Crypto]

Can anyone now tell correct correct addnodes? So it doesn sync properly to main chain and YoloBit.

On my side, the chicks.conf file

Code:

connect=149.56.154.75:10123

Don't miss to delete the blockchain is you are already sync on the bad blockchain.


We are still waiting for a developer fix.  

There are no more nodes on the forked network, you don't want to keep connect= & that's only for the sync. Also rescan=1 will solve without having to delete the blockchain, but a developer fix isn't going to fix anything & that's just a simple fact. Sure a coder could code in checkpoints, but without a change to the staking limit from unlimited to say 30 days & then spend weeks trying to get everyone to update. The network is stable now, pushing updates & trying to get everyone on the new update would just cause more problems, but setting a reminder for a few months ahead would work.

Code:

rescan=1
addnode=94.23.102.99:10123
addnode=90.225.61.229:10123
addnode=149.56.154.75:10123
addnode=50.83.4.208:10123
addnode=13.93.84.61:10123
addnode=88.88.166.130
addnode=75.72.134.175
addnode=90.225.61.229
addnode=86.184.84.190
addnode=178.121.121.90
addnode=148.251.54.6
addnode=185.11.195.45
addnode=169.0.231.41
addnode=98.115.147.74
addnode=217.175.119.125

[anemol]

There are no more nodes on the forked network, you don't want to keep connect= & that's only for the sync.

I know  . But I did this to have the two wallets, each synchronized on a different chain. Moreover, this pertube my wallet monitor which checks that every wallet is synchronized or not (according to the peers).

[Testing Crypto]

Thanx both

Your welcome, for future problems of being on a fork (or other peers broadcasting one) & not having to delete the entire blockchain (lucky it's small database size now for a full resync) you can just use rescan=1 to fix it.

chicks.conf   //only if on a fork

Code:

rescan=1
connect=149.56.154.75:10123

chicks.conf   //normal configuration

Code:

rescan=1
addnode=149.56.154.75:10123

{
"addr" : "91.90.235.216:53786",
"services" : "00000001",
"lastsend" : 1493825394,
"lastrecv" : 1493825225,
"conntime" : 1493824043,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 17,
"banscore" : 0
},

[buwaytress]

Hey thanks guys for the helpful information. I think this issue's more or less fixed for me and I'll know better what to do if it happens again.

P.S. Hey OP, you really should give a little bit of your time here, a post a week even for a tiny update's not too much to ask for, I hope?

[Chicks]

Hi guys, i update the first post nice to that there is some action on yobit and nova.
And you can see that this coin is no dumping coin!

[rttia]

Thanks for the responses guys, think I finally understand now. I guess I'll leave the staking alone mostly for now as it's not worth the electricity to leave my computer on with only 300 chicks!

Not sure if OP is still reading, but I put in my 2nd vote (#22) already, and also waiting for airdrop and whatever other bounty is still available. Faucet gives close to average too, so that's okay.

If you have an old pc or pc parts or even just buy a second hand older pc with a small psu and it will draw only a little bit more wattage then if on idle. Then you can also handle all your  coins on one computer dedicated to staking.

hmmmmmmmm.... good idea here for restating it in new way..

[wahyu5]

Thanx both

Your welcome, for future problems of being on a fork (or other peers broadcasting one) & not having to delete the entire blockchain (lucky it's small database size now for a full resync) you can just use rescan=1 to fix it.

chicks.conf   //only if on a fork

Code:

rescan=1
connect=149.56.154.75:10123

chicks.conf   //normal configuration

Code:

rescan=1
addnode=149.56.154.75:10123

{
"addr" : "91.90.235.216:53786",
"services" : "00000001",
"lastsend" : 1493825394,
"lastrecv" : 1493825225,
"conntime" : 1493824043,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 17,
"banscore" : 0
},

I will to try this tutorial, thanks @Testing Crypto

[Testing Crypto]

Thanx both

Your welcome, for future problems of being on a fork (or other peers broadcasting one) & not having to delete the entire blockchain (lucky it's small database size now for a full resync) you can just use rescan=1 to fix it.

chicks.conf   //only if on a fork

Code:

rescan=1
connect=149.56.154.75:10123

chicks.conf   //normal configuration

Code:

rescan=1
addnode=149.56.154.75:10123

{
"addr" : "91.90.235.216:53786",
"services" : "00000001",
"lastsend" : 1493825394,
"lastrecv" : 1493825225,
"conntime" : 1493824043,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 17,
"banscore" : 0
},

I will to try this tutorial, thanks @Testing Crypto

You are welcome, also see that https://www.tradesatoshi.com/Vote has reopened voting @ 1 Day 8 Hours 2 Minutes 10 Seconds & now CKS in 2nd place? They were #1 & VirtacoinPlus wasn't even in the list (the one with 54 votes was #2 then?), now they have 177  Not that another exchange would help CKS anyway, nothing gets traded there & satoshi does not even like to trade  Just find it hard to believe that 177 honest votes without multiple VPNs or TOR were used, thought those days were past in the crypto world & guess that would be wrong.

[Jian_Liux]

Dev doesn't actively given updates, but you (Testing Crypto) give some more detail news updates
Honestly, I am amazed with you!

[Testing Crypto]

Dev doesn't actively given updates, but you (Testing Crypto) give some more detail news updates
Honestly, I am amazed with you!

Thank you, the main reason why I learned to BBcode & do my best to keep all the info in the simplest form. Since the main point of mining, buying or selling these applications coins or tokens account for what knowledge the user has on them & with enough points of information on what the user can understand about it as a whole. I've watched, tested 1000's of alts over the years, tried to help many & even the smallest point of data can be useful to the miner, buyer or seller & or investor. I still make mistakes, as we all do & only try to make sure other don't do the same.

[Chicks]

You are welcome, also see that https://www.tradesatoshi.com/Vote has reopened voting @ 1 Day 8 Hours 2 Minutes 10 Seconds & now CKS in 2nd place? They were #1 & VirtacoinPlus wasn't even in the list (the one with 54 votes was #2 then?), now they have 177   Not that another exchange would help CKS anyway, nothing gets traded there & satoshi does not even like to trade   Just find it hard to believe that 177 honest votes without multiple VPNs or TOR were used, thought those days were past in the crypto world & guess that would be wrong.

Yeah i think they cheat their votes But anyway we are on two other exchances^^