|
What would be the address to which one would send their VOTE tokens if they don't plan to use them i.e. if one wants to burn the VOTE tokens where should they send them? Thank you.
|
|
|
|
@kaicrypzen The ChessCoin Blockchain is now round about 800MB big and with 50Mbit/s isn't a problem to load the Blockchain new?
Thx for the suggestion. Well before trying this, I wanted to understand what was going on with my client, but if nothing can be configured on my side to speed up the syncing, then I'll try syncing from scratch ... I tried running a brand new wallet and then copying wallet.dat right after that, the syncing got stuck. Then I ran a brand new wallet and let the blockchain sync entirely, the syncing finished. I then copied wallet.dat and the addresses and transactions showed up, however the balance was still missing. I then ran the commands checkwallet and repairwallet and the balance showed up. So all seems good now, yet I'm still puzzled by the slow syncing the wallet encountered ... |
|
|
|
|
Btctalk name: kaicrypzen
Rank: Hero Mamber
Current post count: 1106
GBYTE address: 3KNLEFIXBCUQNA5N3VBSMR6ZB6TWARIH
|
|
|
|
@kaicrypzen The ChessCoin Blockchain is now round about 800MB big and with 50Mbit/s isn't a problem to load the Blockchain new?
Thx for the suggestion. Well before trying this, I wanted to understand what was going on with my client, but if nothing can be configured on my side to speed up the syncing, then I'll try syncing from scratch ... |
|
|
|
It seems quite impossible for my wallet to catch up on unsynchronized blocks. Here is what happens :
At time t, 50000 blocks left
At time t + p, 45500 blocks left
At time t + p + q 45900 blocks left
And so on
It seems it will never be able to synchronize ...
Anybody experiencing the same, is this behavior considered somehow normal? Thx.
It took me 5 days to synchronize mine because I only used it three hours daily but there are many factors like fresh nodes, your connection and anti virus but it will eventually synch I keep it running more than that ... I'm using the list of the nodes provided by ZzzzeyeZzzz, do you know how to get a list of fresh nodes? This issue started to appear some weeks ago, it was never problematic to get it synced before ... For info I'm using the Linux client. So, I kept the wallet open for more than 32 hours non-stop, on a computer with an ssd, a very high speed internet connection and plenty of RAM. It synced a bit more than 800 blocks (that's nothing). Something is definitely not working as it's supposed to be ... Anyone who could help troubleshoot it please ? Thx. |
|
|
|
It seems quite impossible for my wallet to catch up on unsynchronized blocks. Here is what happens :
At time t, 50000 blocks left
At time t + p, 45500 blocks left
At time t + p + q 45900 blocks left
And so on
It seems it will never be able to synchronize ...
Anybody experiencing the same, is this behavior considered somehow normal? Thx.
It took me 5 days to synchronize mine because I only used it three hours daily but there are many factors like fresh nodes, your connection and anti virus but it will eventually synch I keep it running more than that ... I'm using the list of the nodes provided by ZzzzeyeZzzz, do you know how to get a list of fresh nodes? This issue started to appear some weeks ago, it was never problematic to get it synced before ... For info I'm using the Linux client. |
|
|
|
|
It seems quite impossible for my wallet to catch up on unsynchronized blocks. Here is what happens :
At time t, 50000 blocks left
At time t + p, 45500 blocks left
At time t + p + q 45900 blocks left
And so on
It seems it will never be able to synchronize ...
Anybody experiencing the same, is this behavior considered somehow normal? Thx.
|
|
|
|
here the update for your chesscoin.conf
...
Thanks for the frequent conf updates. My client hasn't been syncing these past days, started with my old conf, and nothing changed after two conf updates. Is anyone experiencing the same? What could be going wrong? Fyi, my conf contains only the addnode fileds. Btw, how does one get the list of the nodes? Thank you. |
|
|
|
Why not? Since the last payout from BTCD to KMD swaps is supposed to happen on the 15 th of January, and the supernet team will very officially stop working on BTCD, then it's probably for the best. I also think all the exchanges listing BTCD should do the same and add a BTC-KMD market if they still haven't. |
|
|
|
you can believe me or whoever made the erroneous post, your choice It's not about believing you or not ... The last information we have from the official information sources (blog and twitter) clearly mentions the 8 th of January as a key date. The fact that this deadline couldn't be met is not an issue per se. The issue is the lack of a very simple update. When the team realized that what they wrote about the 8 th of January was no longer achievable then they could've just made a post here and/or tweeted about it, that seems not to be costly and it may have prevented people from repeatedly asking and expressing doubts ... Didnt I post that the information wasnt accurate? If that is not sufficient, what am I to do? Yes you did and thank you for it  . The assumption is this may have been known before the 8 th and hence posted about in a proactive manner rather than in a reactive manner. |
|
|
|
you can believe me or whoever made the erroneous post, your choice It's not about believing you or not ... The last information we have from the official information sources (blog and twitter) clearly mentions the 8 th of January as a key date. The fact that this deadline couldn't be met is not an issue per se. The issue is the lack of a very simple update. When the team realized that what they wrote about the 8 th of January was no longer achievable then they could've just made a post here and/or tweeted about it, that seems not to be costly and it may have prevented people from repeatedly asking and expressing doubts ... |
|
|
|
A lot of people sold their kmd to buy btcd and do the swap.
Why would anyone do that? It doesn't make any sense, or am I missing something? To take advantage of the price difference What price difference are you referring to? The prices of btcd and kmd have generally always matched the conversion ratio, apart from some punctual btcd unexplained rises that probably noone with no insider info could have expected ... So, if one sells kmd and then buys btcd to swap it later for kmd they actually could get less kmd if they don't stake the btcd (because the ratio goes down with time to adjust with the staking). |
|
|
|
Keep in mind that our BTCD are stuck in staking and the blockchain is not moving. Just 2-4 blocks every 2 days. Mine are stuck for 20 days and there are just 35/110 confirmations. I won't be able to swap. Don't ask me why I opened the wallet for staking. My intention was to send them to bittrex and while the wallet was locked, i entered the password for sending and it gave me stake. More than 200 btcd are stuck, probably for ever. The only thing I can say is if it is possible to send the wallet.dat to the kmd team so they send me the kmd or get a 6 months extention for the swap. Otherwise I am screwed. I do not think I am the only one.
From https://bitcointalk.org/index.php?topic=1605144.msg26851472#msg26851472: Or you can just wait til it is unstuck and swaps are enabled again.
They seem to have plans to make things work before the last swap and I don't doubt the deadline will be extended if they can't manage to solve that issue in time. A lot of people sold their kmd to buy btcd and do the swap.
Why would anyone do that? It doesn't make any sense, or am I missing something? |
|
|
|
It is supposed to open in a few days. Just wait a bit. I don't think they will fix it before the deadline. Why do you think they won't?
I like how you dishonestly use the word "swap" to imply a 1-to-1 trade of BTCD for Komodo, when in fact what actually happening is massive dilution of BTCD bagholders' equity.
First, a swap doesn't necessarily mean 1-to-1. Second, even if it did, that would mean they dishonestly make you think you'll get 1 KMD for 1 BTCD instead of ~50 KMD for 1 BTCD, indeed they are fooling you big time (sarcasm in case you don't get it). Third, do you even know what dilution means? If anything could happen here it would be the complete opposite. If we assume that something like 2% isn't swapped in time, that would mean that 98% of the BTCD supply will be locked/burned/whatevs making BTCD as scarce as it gets. Assuming it is still exchangeable for whatever reason, this could create room for crazy high prices. (I'm not encouraging anyone to speculate on this.) |
|
|
|
which is the best way to switch from a full node wallet to a light one - without losing old addresses of course?
If you only have public assets (bytes for instance) then the seed is enough. Save it, uninstall your full wallet, install a light wallet and restore using the seed. You'll get your addresses with their public assets' balances. If you have private assets (blackbytes for instance) then you'll have to wait for your full wallet to sync, install a(n intermediary) light wallet elsewhere (a different user will do if you want to stay on the same machine) and transfer your blackbytes then your bytes to it. If you want your old addresses back, then after emptying your full wallet, uninstall it, install a light one and recover from the seed. You'll then have to send your assets from your intermediary light wallet to your newly installed light wallet (always leave sending the bytes at the end, because you'll need them for fees to send everything else). |
|
|
|
Hello ! J'ai profité du cours très bas pour acheter quelques GB. Du coup, maintenant que bittrex a unlock mes withdraw, j'essaie de trouver la méthode la plus efficace pour pouvoir protéger mes byteball Avant ça j'avais les pièces de l'airdrop que j'avais sur mon PC, sans backup (pas terrible). Ce que j'aimerais faire là, c'est : - Un backup papier, au moins pour les bytes. J'ai cru comprendre que pour les blackbytes, c'est pas trop possible. Pour un Backup papier, j'ai juste à sauvegarder la seed c'est ça ? Que se passe-t-il si je fais de nouvelles transactions ? Je dois resauvegarder à nouveau la seed ? J'imagine que pour ce type de backup, faut que j'utilise un portefeuille à adresse unique, non ? Ensuite, je voudrais faire un backup du dossier. J'ai pu comprendre qu'il fallait copier toute l'arborescence. Dois-je réellement refaire ce backup à chaque nouvelle entrée/sortie de fonds ? J'ai lu ça je sais plus trop où. Autre question, si le PC où je fais fonctionner le wallet flambe, ça peut arriver, tout peut arriver après tout. Imaginons que je souhaite réimporter ce dossier sur un autre PC, est-ce que ça marchera directement sans autre manipulation ? Dans ma situation (avoir un backup sur stockage externe du dossier + le seed en version papier), est-ce que j'ai besoin tout de même d'appairer un autre ordinateur pour ne pas risquer de perdre mes bytes ? Cette question trouvera surement sa réponse dans la précédente, j'en suis conscient. Est-ce plus simple pour moi d'avoir un portefeuille à adresse unique, sachant que je veux faire du cold storage ? Désolé de cette flopée de questions, j'espère que quelqu'un trouvera le temps et la patience de répondre à tout ça, j'avoue être pas mal perdu  Merci d'avance ! edit : j'ai pu faire quelques tests avec la seed, ça se comporte pas mal pour backuper les byte. J'ai changé le nom du PC indiqué dans le wallet ça a pas posé de souci pour récupérer mes pièces. Pour ce soir du coup je backup déjà ça sur mes supports externes + papier Par contre j'arrive pas à faire transiter mon wallet linux vers mon wallet windows sans faire bugguer, l'architecture du dossier doit être différente  Je me suis aussi amusé à faire mes retraits sur Bittrex, ça met environ 1 min à arriver dans le wallet, et environ 4 minutes à repartir sur Bittrex. Plutôt rapide Salut, La graine (seed) permet de récupérer toutes les adresses et d'avoir accès aux actifs publics qu'ils contiennent (byte par exemple). Le fait d'avoir un portefeuille à adresse unique n'a pas trop d'importance je pense. Un portefeuille à adresse unique te permet de ne pas avoir la monnaie (change) transférée sur une nouvelle addresse. C'est pratique pour la distribution (à l'ancienne) : Si tu a lié une adresse byteball et que tu as fais des transactions avant la distribution, tu n'as plus a retransférer tes fonds à ton adresse liée ou à lier de nouvelles adresses. Ceci n'a d'importance que si tu veux recevoir les blackbytes en rapport avec les soldes de tes adresses qui contiennent des bytes. La graine ne permet pas de récupérer les actifs privés (blackbyte par exemple), Pour cela il faut en effet effectuer une sauvegarde complète avant de faire une transaction qui implique l'envoi d'un actif privé, au cas où ça se passerait mal ... Deux manières de sauvegarder, soit tu fait une copie du dossier qui contient les infos, soit t'utilises loption de l'application pour faire une sauvegarde complète. Vaut mieux privilégier l'utilisation de l'option de sauvegarde depuis l'appli (au moins car cette sauvegarde et multiplateforme). La sauvegarde complète suffit d'ailleus à retourver tous tes actifs (donc les publics aussi). Donc si tu n'as que des bytes la graine suffit. Si tu as des blackbytes, tu devrais faire une sauvegarde complète (la graine n'est pas nécessaire dans ce cas, mais note-la quand même ). Pour la récupération, normalement sur une appli à jour et qui n'a pas été trop torturée, ça fonctionne bien, que ça soit à partir de la graine ou de la sauvegarde complète. |
|
|
|
Given the fact that the BTCD blockchain seems stuck, it appears to me that the only solution is to sell your BTCD (, transfer your BTC to an exchange that's trading KMD if necessary) and buy KMD. There might be a slight loss (or gain) if the prices of BTCD and KMD do not match the current conversion rate (which I don't know) or if KMD shoots up (or down) between the time you sell BTCD and the time you buy KMD. |
|
|
|
Using a light wallet would have solved the problem as you never would have had the problem.
 , you know that nobody can go back in time, right? It was a choice made to go against the defaults.
Yes it was and still is. That wallet dates back to the very early days. On one hand, there was no light option for desktop wallets (so no going against the default). On the other, if I had the choice I would've run it full anyway (for the sake of the network). It's the same argument people have for using Bitcoin Core wallet. - slow, SSD, takes lots of space, etc.
I wasn't arguing about it actually . I was exposing a case where one is stuck and where the answer "use a light wallet" doesn't apply. So, we agree that full node is slow. Must have a modern computer for speed.
Yes we do . There are other methods to restoring to a light wallet
Do these methods work in the case of restoring a full wallet with addresses containing blackbytes without having to wait for it to sync up? If so, then I would be grateful if you could PM them to me. Thank you. as I have done it before for several people and never charged anyone.
Thank you on behalf of everybody . I think, and believe you would agree, that it would be awesome if there was a tool to convert a full node wallet to light wallet.
Oh yeah! Thx on behalf of the one who got it . Keep'em coming. |
|
|
|
Let me butt in here to say that in some cases users might not have a choice in running a light wallet.
I personally had an app installed in full mode which had bytes and blackbytes on it, I didn't run it for months. When I launched it to sync, it synced well up to some point but then it was just almost stuck (on an HDD). What I did was make a full backup, copy it to a computer with an SSD and restore from it. Needless to say that using a light wallet wouldn't have solved the problem ...
Welcome to butt in. Everyone has a choice at running a light wallet or full node. You chose to run a full node (not the default). Needless to say.... running a light wallet WOULD have solved the problem. It wouldn't have . I'm not talking about a fresh install, I'm talking about a case where a full wallet contains blackbytes. There are two ways to regain control over the blackbytes, either sync the current full wallet up or restore in another full wallet that will sync up faster (SSD). A full backup of a light wallet does in fact keep youis fr bytes and blackbytes with a full restore. It takes about 15 seconds to sync. No matter how far back in history.
Of course it does, nobody's arguing about that . Again the case I'm exposing is if one already had blackbytes in a full wallet, the only way out, is to sync up a full wallet. Again, a light wallet is fast and stores (and restores) bytes/blackbytes via a full backup/full restore.
Again, nobody's arguing about that and again you are missing the point by talking about something that is irrelevant to the case of a full wallet with blackbytes in it (I know I'm repeating myself but it seems necessary). Resolution:
I do understand that since you have a full wallet and you will need to sync.
Yay! Finally . You can resolve the problem for the future by starting up another wallet and move your funds to it. This way, you will not have the sync issue in the future.
Yes. Having said that, once the full wallet is running on an SSD it syncs up fast and there is no more syncing issue. The whole point of my comment was actually to say that answering people who complain about syncing speed, "use a light wallet" is not helpful ... Yes "use a light wallet" in case you are fresh-installing or in case you only have bytes on your slow-syncing full wallet (cuz they can be restored through the seed), but if you have blackbytes on a slow-syncing full wallet and you want to regain control over them, well you are stuck until your full wallet syncs up or another fast-syncing (running on an SSD) full wallet where you restored from your full backup syncs up. |
|
|
|
My notebook is finally out of the warranty service, so I installed the new wallet version. Too bad that the last sync I made was around the beginning of october. It will be a while till it catches up. It could be a nightmare for those who just downloads the wallet and wants to do a sync from zero. On an HDD it's just chanceless.
Is it planned to enhance/optimize the load time?
Use the light wallet which is the default and recommended option now. You mean to say that by default, a wallet installs in minutes and syncs within seconds? So, during the install, just pick the DEFAULTs and you get an awesome user experience. Just to re-interate.... Stop messing with the options and click the defaults? Thanks. (Ok, done trolling.) Defaults for the win! Let me butt in here to say that in some cases users might not have a choice in running a light wallet. I personally had an app installed in full mode which had bytes and blackbytes on it, I didn't run it for months. When I launched it to sync, it synced well up to some point but then it was just almost stuck (on an HDD). What I did was make a full backup, copy it to a computer with an SSD and restore from it. Needless to say that using a light wallet wouldn't have solved the problem ... |
|
|
|
|
Show Posts
