|
Is there a bootstrap.dat available to download???
Thanks!
|
|
|
|
ya this coin is fucked
What can I say. Nom Nom & Nom. This is exactly the point when accumulation is in progress. Accumulation or death? I can't get the client wallet to even run correctly from sourcecode... don't have this problem with compiling any other wallets. It compiles, but doesn't run well at all. Obvious fake / crap coin, is obvious. |
|
|
|
|
So since just-dice stakes the majority of clams daily, what happens if that staking stops?
How does it affect the network?
2nd question is:
Sometimes my staking icon turns red, like it stops staking.. I have mature coins though, why is it doing this?
Note, i'm on v1.4.7 and sometimes I do get stakes.
|
|
|
|
Here's some of the debugging info... does "fail" mean it simply didn't find a suitable result that round, or that there's some issue?
Seems that is normal, from Dooglus' answer: To stake a block, the hash of the output that is trying to stake must be lower than the target hash. In this case 38f... is less than 2d4d... (it's one character shorter) and so it wins the right to stake. Then every 16 seconds you'll see your outputs trying to stake: [STAKE] searching for staking opportunity:
2015-02-18 07:22:09 [STAKE] checking 18 output(s)
2015-02-18 07:22:09 [STAKE] check fe7c7692b2ca1969ed4fb431144f6a15815f2a57b3bda9bbf8fcb2f338af9d28:107 (4.00 CLAM)
2015-02-18 07:22:09
[STAKE] fail: hash 413d56c739eb1bf553a51d7f642fe66d094f931746e433b14cda85178224d7ce
[STAKE] > target 2d53118d2c00000000000000000000000000000000000000000000000000
2015-02-18 07:22:09 [STAKE] check fe7c7692b2ca1969ed4fb431144f6a15815f2a57b3bda9bbf8fcb2f338af9d28:125 (4.00 CLAM)
2015-02-18 07:22:09
[STAKE] fail: hash ccd1436cf112218abb68f704f1bfbd54f4b9206d3bc58dc76162af15a05e5266
[STAKE] > target 2d53118d2c00000000000000000000000000000000000000000000000000 I have 18 unspent outputs, but I've cut the log off after the first 2 failed to stake. In both cases the hash is much bigger than the target, and so those outputs didn't get to stake. |
|
|
|
It will be a 1:1 swap on a reputable exchange (TBD where). The reason for not forking the current chain is simple; the changes are far too drastic and won't work well with what we already have
Which exchange and when does this take place, would be nice to know since balls seem very difficult to move/send. Any news on this? |
|
|
|
It will be a 1:1 swap on a reputable exchange (TBD where). The reason for not forking the current chain is simple; the changes are far too drastic and won't work well with what we already have
Which exchange and when does this take place, would be nice to know since balls seem very difficult to move/send. |
|
|
|
|
So when is this new chain coming out or will we have a whole new client?
Edit: ah i see .. "It will be a 1:1 swap on a reputable exchange (TBD where). The reason for not forking the current chain is simple; the changes are far too drastic and won't work well with what we already have"
When about will this take place?
|
|
|
|
I get "segmentation fault" when I clicked repair wallet.
I don't get this error. Anyone else? Additional note: client crashed with the seg fault, but upon restarting, the wallet was repaired.. |
|
|
|
|
I get "segmentation fault" when I clicked repair wallet.
|
|
|
|
You could definitely just copy someone elses files (so long as they are the same bdb version, os, etc), but the problem is that you don't know if they are valid. You are trusting someone else.
A bootstrap gives you the entire blockchain, and then your client scans through the rules for the entire chain and indexes it. This is safe. The other way can work I have done it with a copy and paste of blkindex.dat blk0001.dat and database folder), but its not as safe.
Makes sense, thanks for explaining! |
|
|
|
Download the bootstrap.dat file from the first post. Place the extracted bootstrap.dat into the folder you just deleted everything from. Start your hyperstake.exe (the new version) and patiently wait for the bootstrap process and for your wallet to sync. If your wallet jumps out of bootstrap mode before it finishes (it should be taken through block 235k) then go back into the folder, name bootstrap.dat.old back to bootstrap.dat and then restart your wallet.
Good luck.
Why does bootstrap.dat always have to be imported? Can't someone just upload the blk*.dat files and the client would just instantly use them and start finishing syncing online? Just sick of always having to wait for this importing. What is the reason for it? |
|
|
|
good luck  Thanks, you too.. but not good luck to your fud spreading. If you don't like this coin, why not just move on to something else hey? I'm sure there are plenty of other coins you can troll and fud about |
|
|
|
now your turn... explain me why you hold this coin and why you think it is a good buy?  Its the only coin that has brought up this concept of building an rpg game out of / on top of the blockchain, not counting stuff like huntercoin that is just basically human mining coins but has now turned into bots.. It is a feasible concept and it is worth the chance to risk some money on it, in the event that it does take off. |
|
|
|
considered it is based on just promises and few b&w drawings ? hell yes
promises and drawings? As if the coin doesn't exist ?  Someone sounds sore that they didn't buy in cheaper  |
|
|
|
I hope you do ban the version and/or behavior too, just would make sense. I hope people would then upgrade. Maybe banning the behavior would still allow v1.4.5 versions to exist.. whereas banning version would eliminate v1.4.5 clients too if they are reporting wrong? |
|
|
|
a) Because v1.4.4 gets a lot of peers to de-sync and keep requesting the same blocks over and over again, wasting other peers' upload capability.
b) Also because v1.4.3.1 to v1.4.5 have a bug that makes most peers fail to advertise their external IP address, making them impossible to discover, severely limiting peer availability.
c) v1.4.5 also has a bug that makes it identify itself as v1.4.4, meaning we can't even easily ban v1.4.4 from the network to work around a) above.
So together we have less available peers, each of which has their bandwidth being wasted, and no easy way of fixing this waste. The three bugs together make the network crappy for the few up to date peers on the network.
Hi Dooglus.. with all these issues is there any way to verify or confirm that let's say you have a current version (1.4.7) wallet, and it would be staking correctly?? I get the feeling a lot of people are not getting the stakes they should. What should we look for .. are there signs in Debug.log ? And what would help continue staking.. simply keep restarting the wallet and hope to connect to "good" peers  Edit: removed non-essential question |
|
|
|
ok, another silly question. Is their any advantage to running more than one wallet, on different PC's verses using just one wallet on one pc? since clams can be split, or is there any limitations using one wallet for everything lol THX again, Bad things can happen if you run the same wallet.dat file on multiple instances and/or computers etc.. I read in the past about how you shouldn't do that, I would have to dig up a link I think it would be ok with different wallet.dat files though on separate machines. Yes you are very correct on that if using the same wallet.dat. What I am wondering is the latter, running say 5 wallets on their own pc, clean installs (own wallet.dat) So say, which is better or no difference? ex: 500 clams staking in 1 wallet on 1 pc, or 100 clams each staking on 5 different wallets. (100 on each wallet) Just didn't know if their is anything to be gained by multiple wallets, perhaps better for the client network I suppose but probably no real gain in actual staking rate or odds.... If you see what I am saying lol but I still wonder or maybe I am thinking to much into it  THX Just show advanced options in send.. and use the inputs button. Send coins to different addresses (that you create in same wallet) using that, to split them up.. no reason to use other wallet.dat's You can keep them all split up in the same wallet, I'm guessing you could even split the inputs/stacks up in the same address. I keep my coins split up in small stacks/amounts, so others don't get tied up while staking. Is that what you're talking about? |
|
|
|
ok, another silly question. Is their any advantage to running more than one wallet, on different PC's verses using just one wallet on one pc? since clams can be split, or is there any limitations using one wallet for everything lol THX again, Bad things can happen if you run the same wallet.dat file on multiple instances and/or computers etc.. I read in the past about how you shouldn't do that, I would have to dig up a link I think it would be ok with different wallet.dat files though on separate machines. |
|
|
|
Hey gang, new to clam here. I am downloading client 1.4.5 is this the latest wallet to use? and also am downloading a bootstrap mentioned in previous post here. Ok, just don't want to waste time with wrong client THX v1.4.7 will be available soon as binaries, if not already. Its' already available as sourcecode: https://github.com/nochowderforyou/clams/releasesSo, I wouldn't install 1.4.5.. wait for 1.4.7 |
|
|
|
Re-Post from dooglus, via IRC #clams: <@dooglus> running clamd -externalip=a.b.c.d with your actual external IP address seems to fix the problem
So, if anyone is having connectivity problems with 1.4.5, a possible work around would involve running the client with the -externalip=yourIP flag. Interesting, thank you.. I will try that Alternatively, I found the cause of the problem and fixed it. See https://github.com/nochowderforyou/clams/issues/137 for details. I tagged a new release, v1.4.6, which I'm guessing will have binaries made available soon-ish. Thanks Dooglus !! Awesome! |
|
|
|
|
Show Posts
