|
Just completed a fork and now the dev wants to do another.
Keeps mentioning "updates" and forks in order to build anticipation and hopefully speculative buying.
|
|
|
|
After this rally, START then fell into a long and sustained decline that began on Oct 6 2014, and grinded to a halt on Nov 20 2014. During this period, START dropped 95% in value. This is when START became a regular PumpersPick.
You're forgetting one thing, supply. look at BALLS.. its dropped what 93% down to 7 satoshi last I looked? There is no way you could pump BALLS with the amount of supply in the coin. Another example... lets' see you pump Dogecoin |
|
|
|
With all the work / updates supposedly being done .. where are any updates to the source code? Last commit was back toward the end of January .. something smells like bullshit.  |
|
|
|
Client crashed on me with this error: ************************
ETRKEPTION: NSt8ios_base7failureE
CDataStream::ignore() : end of data
HyperStake in ThreadMessageHandler()
terminate called after throwing an instance of 'std::ios_base::failure'
what(): CDataStream::ignore() : end of data
Aborted
Wtf is that... or what happened  It also keeps throwing a repeating message in the terminal: Qstring::arg: Argument missing: Not minting because wallet is locked We have noticed the error with CDataStream too. It is only affecting some users, but allejupa was able to find the line in the code and we are investigating it further. The argument missing has been fixed, you can pull the latest repo from github.com/hyperstake/hyperstake and build. Thanks presstab !! I knew you would probably have some answer  You are awesome dev! |
|
|
|
Client crashed on me with this error: ************************
ETRKEPTION: NSt8ios_base7failureE
CDataStream::ignore() : end of data
HyperStake in ThreadMessageHandler()
terminate called after throwing an instance of 'std::ios_base::failure'
what(): CDataStream::ignore() : end of data
Aborted
Wtf is that... or what happened It also keeps throwing a repeating message in the terminal: Qstring::arg: Argument missing: Not minting because wallet is locked |
|
|
|
If you were a fruit store, and wanted to sell fruit to the customer.. But the customer's got a money printing machine, would you sell your fruit to that customer? No!
This is how stores work. And we really need a sort of store for BALLS.
Why would they buy any significant additional amount if it was just as easy to obtain the same printing machine?  |
|
|
|
|
Not enough marketing, = not many new buyers... therefore people are scared and want to sell.
Plus too much supply.
|
|
|
|
Mac fag checking in. Running 1.4.10 and smooth sailing so far. Staking and all.
Curious behaviour as the staking icon goes red more than I've ever seen but I can't
see a problem.
Does it go red for long periods at a time? Long enough that you can hover the mouse over it and tell me what pops up when it's red? If you put: debug=stake in the clam.conf file in the same folder as your wallet.dat and restart, it will write stake-related stuff to debug.log in the same folder as it stakes. You could "tail -f debug.log" in that folder and see whether anything looks different when it's red. Staking basically consists of hashing each of your staking outputs every 16 seconds and comparing the result with a target based on the network difficulty. If the output hashes lower than the target, you get to stake a block. "debug=stake" will cause these hashes that are being compared to be logged. I couldn't find an existing one, so I created a clam.conf and added debug=stake. I'm hoping I did it correctly. I added a screengrab of data flow. http://imgur.com/Gmcfbf8 When I hover the cursor over the red icon, it sometimes says 0 weight. And then other times it says not staking because I don't have mature coins. But then I stake at least once a day. Hope this helps. Thanks for everything! /s/ Same thing was happening to me on a previous version (1.4.7 i think) and the 0 weight was also showing. I haven't seen it happen to me again yet on this latest version.. but I'll watch for it. It can stay red for up to one minute, i've seen it myself. When you hover over it says 'Not staking because you don't have mature coins' It doesn't appear to affect staking in the long run, i always just put it down to new blocks being generated and that it was a normal thing. I have the debug switch on at the moment so i'll try and upload the debug.log next time i see it happen. I think I caught a red patch in the debug log. This is the point where it was red and then normalized: ERROR: AcceptToMemoryPool : ConnectInputs failed 275b33ea6daf21907648b93235e33942d63c759c139efe8135f9e88a02aec89f ERROR: ConnectInputs() : afa49bad29ccfd608c5aefb44d407fabfea69fa15d3ea1f5c256d783b10daf6e prev tx already used at (nFile=1, nBlockPos=319403622, nTxPos=319404329) ERROR: AcceptToMemoryPool : ConnectInputs failed afa49bad29ccfd608c5aefb44d407fabfea69fa15d3ea1f5c256d783b10daf6e ERROR: ConnectInputs() : 58c3a3c1186b5c89c3ac5772eced46233bff83cee7de7c8efc6fe1f3b96029a7 prev tx already used at (nFile=1, nBlockPos=342165995, nTxPos=342168405) ERROR: AcceptToMemoryPool : ConnectInputs failed 58c3a3c1186b5c89c3ac5772eced46233bff83cee7de7c8efc6fe1f3b96029a7 ERROR: ConnectInputs() : 9236ca795d0acf1016cfaa99887c75e79465376f9d64dfa6f7c02fcbffd2ec62 prev tx already used at (nFile=1, nBlockPos=342323040, nTxPos=342323537) ERROR: AcceptToMemoryPool : ConnectInputs failed 9236ca795d0acf1016cfaa99887c75e79465376f9d64dfa6f7c02fcbffd2ec62 ERROR: ConnectInputs() : 0b675b9287c686a297de540dbc6909342dcd494164ee73fc7a14484b53e436a1 prev tx already used at (nFile=1, nBlockPos=342592588, nTxPos=342593400) ERROR: AcceptToMemoryPool : ConnectInputs failed 0b675b9287c686a297de540dbc6909342dcd494164ee73fc7a14484b53e436a1 stake took 0s stake took 0s stake took 0s stake took 0s SetBestChain: new best=c4f00cb1bd10f1465095c98ace135a9cde9beff8f28f92469835487faf060c35 height=360756 trust=16799287784950803720 blocktrust=156701501658267 date=03/01/15 04:48:48 ProcessBlock: ACCEPTED stake took 0s SetBestChain: new best=8e2c754fd4bcadb59b715244d7f885f2059120b7d862f0b0e29f1c01e929a9c7 height=360757 trust=16799443607527302960 blocktrust=155822576499240 date=03/01/15 04:49:20 ProcessBlock: ACCEPTED stake took 0s SetBestChain: new best=8aec101da5519366c1b71c094f9ddf4d213860433299fd918f89ef03b83a62d6 height=360758 trust=16799598557078531095 blocktrust=154949551228135 date=03/01/15 04:49:36 ProcessBlock: ACCEPTED Any update on why this happens ? Mine seemed to stay red longer this morning Edit: also seems to be happening more frequently (icon turning red) Edit #2: Restarted wallet and symptom seems to have mysteriously disappeared (for now?) |
|
|
|
Mac fag checking in. Running 1.4.10 and smooth sailing so far. Staking and all.
Curious behaviour as the staking icon goes red more than I've ever seen but I can't
see a problem.
Does it go red for long periods at a time? Long enough that you can hover the mouse over it and tell me what pops up when it's red? If you put: debug=stake in the clam.conf file in the same folder as your wallet.dat and restart, it will write stake-related stuff to debug.log in the same folder as it stakes. You could "tail -f debug.log" in that folder and see whether anything looks different when it's red. Staking basically consists of hashing each of your staking outputs every 16 seconds and comparing the result with a target based on the network difficulty. If the output hashes lower than the target, you get to stake a block. "debug=stake" will cause these hashes that are being compared to be logged. I couldn't find an existing one, so I created a clam.conf and added debug=stake. I'm hoping I did it correctly. I added a screengrab of data flow. http://imgur.com/Gmcfbf8 When I hover the cursor over the red icon, it sometimes says 0 weight. And then other times it says not staking because I don't have mature coins. But then I stake at least once a day. Hope this helps. Thanks for everything! /s/ Same thing was happening to me on a previous version (1.4.7 i think) and the 0 weight was also showing. I haven't seen it happen to me again yet on this latest version.. but I'll watch for it. |
|
|
|
|
What is the current block number so we can verify correct chain?
|
|
|
|
|
Staking icon says not staking... will this be that way until block 200k?
|
|
|
|
|
Should we have staking enabled when the fork occurs, or doesn't it matter?
Thanks
|
|
|
|
If its an "anonymous coin" how will we know what it is?  |
|
|
|
It's all good, he just has to wait now that's all
I actually don't mind all too much and if it is safer to not use a bootstrap... then fine. |
|
|
|
Is there a bootstrap.dat available to download???
Thanks!
Hmmm.. so is / or will there be one? Why do you need one..... Because its taking forever for me to sync the new wallet, I deleted all the old files I had except for my wallet of course. That is because you deleted all of your files, except wallet.dat. You should have just downloaded the new wallet, extracted file and opened new wallet. Some devs tell you to delete all old files in AppRoaming, but IgotSpots did not tell you to do that. Now you will have to wait for the block index and chain to redownload again. I always just try and open new wallets, then if that does not work, then try downloading entire blockchain again, BIG PAIN IN THE ARSE! Having to download large blockchains, can take days some times. If you did not delete from trash can, put the files back in APPROAMING. And it will open up a lot quicker. Peace! Dennis Correct. There was no need to download the blockchain from the beginning at all for this upgrade Whenever I upgrade, I like to do a clean upgrade because I compile from source. There is no "approaming" in linux. Most other coins/devs provide a bootstrap.dat... with an sha256sum to verify the file, this dev feels it isn't safe.. so whatever. No. there's a .Snowballs file. Basically the same thing. It doesn't matter if you are compiling from source or not. There is no need to delete all those files. If you did, it's your own fault that you had to wait for the blockchain to load. It amazes me how many people cause their own problems and then try to blame the dev. I'm not trying to blame you, I just stated that you feel it isn't safe. That's all. I'm also not looking for drama. |
|
|
|
Is there a bootstrap.dat available to download???
Thanks!
Hmmm.. so is / or will there be one? Why do you need one..... Because its taking forever for me to sync the new wallet, I deleted all the old files I had except for my wallet of course. That is because you deleted all of your files, except wallet.dat. You should have just downloaded the new wallet, extracted file and opened new wallet. Some devs tell you to delete all old files in AppRoaming, but IgotSpots did not tell you to do that. Now you will have to wait for the block index and chain to redownload again. I always just try and open new wallets, then if that does not work, then try downloading entire blockchain again, BIG PAIN IN THE ARSE! Having to download large blockchains, can take days some times. If you did not delete from trash can, put the files back in APPROAMING. And it will open up a lot quicker. Peace! Dennis Correct. There was no need to download the blockchain from the beginning at all for this upgrade Whenever I upgrade, I like to do a clean upgrade because I compile from source. There is no "approaming" in linux. Most other coins/devs provide a bootstrap.dat... with an sha256sum to verify the file, this dev feels it isn't safe.. so whatever. |
|
|
|
If a bootstrap download becomes compromised, someone will malicious intent could have assistance disrupting a network by tricking people into using their chain (which wouldn't be noticed until it's too late; won't describe how that works here) to gain momentum for several attack vectors
With very secure downloads, it's fine, but many people post fake links around here and stupid people click them all the time. Starting fresh and verifying each individual block against the checkpoint server and neutral peers is the best way to keep the chain safe. It might take a little longer for users to sync, but I don't care if it means not compromising safety
Ok... I guess that makes sense. |
|
|
|
Is there a bootstrap.dat available to download???
Thanks!
Hmmm.. so is / or will there be one? Why do you need one..... Because its taking forever for me to sync the new wallet, I deleted all the old files I had except for my wallet of course. Just be patient. It will sync. isn't it possible to just download the new wallet and start the new wallet up without deleting your roaming? Yes, it is possible, mine is now sync'd ... but it would just be faster with a bootstrap.dat.. Edit.. well with the upcoming fork, maybe it isn't easy to have a bootstrap.dat right now.. I think it would be safer though, so everyone could download the bootstrap.dat and be on the correct fork, when the fork does come. no ? |
|
|
|
Is there a bootstrap.dat available to download???
Thanks!
Hmmm.. so is / or will there be one? Why do you need one..... Because its taking forever for me to sync the new wallet, I deleted all the old files I had except for my wallet of course. |
|
|
|
Is there a bootstrap.dat available to download???
Thanks!
Hmmm.. so is / or will there be one? |
|
|
|
|
Show Posts
