Once the wallet is ready, will already have agreed with an exchange to do the swap. I have contacted one already and waiting a reply. Typically a swap is open for months to give everyone enough time. I've just updated the OP with the latest blockchain file, it's been good so far. I'm now in the process of creating 2 more nodes, 1 has just gone online now, and later today the second will be up. I will vote for a complete rebrand too. When are you planning to do the swap? Can I run the wallet now with the bootstrap file from the OP?Wondering if I run into more forking issues still.
|
|
|
3 of us so far want the rebrand! I have the domain already, wait bit longer and make a decision. I'll then select 2-3 new logos for us to select the best one. I'm going to start using the twitter account again from tomorrow, hopefully get some of previous people back. Give them a chance to stake before the swap happens!
|
|
|
I hope everyone withdraw their coins before it was removed!
|
|
|
Everyone will get a 1:1 swap on the new blockchain
|
|
|
Okay everyone, couple of things...
When the new wallet is ready, to run a masternode will require 10,000.
=====
Other thing, what do people think of a rebrand?
Either use just: Krypt, dropping 'Koin' (domain krypt.cash)
Or complete change...
Phore (domain phore.io)
'bearer of a specified thing'
bearer leads into: a person or thing that carries or holds something.
|
|
|
The main problem is not enough connections!
The nodes I'm going to setup this week, I'll going load a small amount of coins so will mint new blocks and help keep the blockchain moving.
|
|
|
If you notice, most of those are not fully synced so not staking either!
|
|
|
I'm on that too, and not seeing any other connection with more blocks, are you? getpeerinfo in debug console I think what you might be seeing, if you are synced but there hasn't been any new blocks for a while, it starts displaying the sync icon. But actually you are, it's just not had new blocks! Having sync issues again.. cannot get past block number 1575799 ... does anybody know a way to fix this?
|
|
|
Ok, I've now updated the OP with the blockchain (blockheight 1601694). https://www.dropbox.com/s/th064e09eaxtr7c/KryptKoin_bc.zipWill start adding new nodes to see if that helps us with the syncing. If anyone loads the blockchain file and seem to have coins missing, try in the debug console: checkwallet It will tell you if there is a mismatch, if so enter: repairwallet Afterwards reload wallet.
|
|
|
I see you managed to work around the error, but did you have coins staking?
And those 'lost' coins will stake again.
Looking at the connections in the console, those 2 connections with 1,569,xxx blocks yesterday (16th) are now at 1,571,xxx and 1,572,xxx
The nodes already setup are only at 1,531,xxx and cannot sync quick enough when those 2 connections are generating blocks so quickly. We need more connections but before adding more nodes to try and help, I want a copy of their blockchain files.
I hope one of those visit the thread and provide a copy, so I can use. And they consolidate their addresses to decrease the generating blocks!
Current supply is at 17,950,686. It's not increasing by much even though the blocks being generated at at high rate.
|
|
|
I've noticed 2-3 connections, first was 1,55x,xxx and now 1,569,xxx blocks. The blockchain file I provided is 1,526,165. So if you are staking and minting dust it's causing the blockchain to increase much quicker or possibly had a longer chain than I provided. Although the coin supply is not increasing by much! Even the nodes cannot keep up and sync fast enough, thus causing everyone else to be constantly syncing! Please consolidate using the coin control function to send the coins to yourself (to the same address). You'll be staking within 3 hours again. Also if one of those who has the longer chain, please upload the blockchain files and either post here or PM me. So I can then use to spin up a couple more nodes. And also add to OP. database (folder) blk0001.dat blkindex.dat Just reminder for everyone: If you've been staking for a long time without using the coin control, it would have split your KTK into lots of smaller and smaller blocks. For the network that's good, but for a user it's very important to use the coin control on a regular basis to avoid hundreds of blocks being created in a single address.
The KTK staking could be part of multiple addresses in your wallet, so when you try to send maybe that is causing the error. If you simply select the checkbox for one address in coin control it will highlight all blocks, but if part of it is staking it will return an error.
If your wallet is locked, and you want to send coins don't unlock to stake. This is more important if you have lots of small blocks in each address. When you then enter your password to confirm a transaction, it might stake from another address while it processes the send transaction. Again this goes back to how many blocks in each address, the higher amount means it will stake much more frequently.
To override completely, close the wallet and edit the kryptkoin.conf, add reservebalance=AMOUNT-HERE
Example:
reservebalance=50000
And it will stop any coins staking even when the wallet is unlocked. Then you can send the coins to yourself to consolidate. Afterwards edit the kryptkoin.conf file again and delete 'reservebalance' restart wallet and in 3 hours will start staking again.
|
|
|
Here are the seeder and nodes: addnode=159.203.178.201 addnode=159.203.185.23 addnode=174.138.37.32 addnode=146.185.173.230
See if that helps by adding to the kryptkoin.conf file. I'll also setup another couple of nodes and post once live to see if that improves things further. Yes, exchange is how the swap will happen. Any that are not swapped will be burned.
|
|
|
Plan is to arrange with an exchange, makes it easier for everyone
|
|
|
Yeah, it's a waiting game. It's not just a simple wallet update, going to require a coin swap once it's ready!
So right now allows everyone to stake to build their coins for when the swap takes place.
The sync is painfully slow, so understand peoples frustration with the wallet!
|
|
|
The seeders have now been updated with the longer chain, plus 2 additional nodes have been setup.
|
|
|
Blockheight now is 1520711 And should be fine, it's ok on my dev wallet laptop. Thank you for clarifying.
Can you confirm what the current block # is on this chain please? Also, I assume the DNS seeder in the wallet will find the correct nodes if I download the longer chain?
|
|
|
As I mentioned in my last post, found a longer chain on my dev wallet laptop and so provided the blockchain.
I've updated the OP with the new file. After finding a longer chain can't continue using an older one!
Everyone should download so we can get on the same chain.
|
|
|
Yes, it's annoying! have to manually sort them back into single amount. But the new update will be completely different, even how PoS works. So won't have the same issue. It's going to be a while though because of the work involved. Likely we will also need to do a coin swap onto the new blockchain! For now just wanted to get the network moving again and hopefully over time more people will come back and open wallets to help keep it moving. Wallet is up to date and staking... ... and I instantly remembered my biggest bugbear with KTK: Coin piles aren't auto-combined when staking. This means piles get smaller and smaller, until you have hundreds or thousands of piles and the wallet becomes super bloated and super slow. If KTK is to be resurrected, my one wish would be to look into auto combining, like DMD Diamond does ( https://bitcointalk.org/index.php?topic=580725.0).
|
|
|
It is at the moment, contacted them to reinstate the wallet but still under maintenance. Advise no one purchase from there until the wallet is back online. Is Yobit the only exchange to get KTK? Need to get KTK added on Coinmarketcap
|
|
|
|