Hal Finney is dead, so I guess you have a pretty good claim

Without knowing how you have that broken up, I can't help. The minimum stake time is ten days, so it depends on the size and age of your blocks. I've never had a problem with HBN staking, but I could just be lucky

Well played

from bootstrap, it usually takes 3-4 hours. Not terrible. It will show out of sync until it's finished reindexing, even if the block height is correct. This isn't a problem, it's just the way it works

Also, and this is something that's a little confusing so I figure it's good general information (for all satoshi based coins) is that you don't HAVE to use the default folder. You can make one and point the client to it. But you have to point it to the folder every time you call it for the daemon, and it needs to be in the launch command line for the QT.

The command is -datadir. For QT, you would run it with hyperstake-qt -datadir=/some/predefined/directory. In windows, you would want to modify the link target to be hyperstake-qt -datadir=\some\predefined\directory

For daemon access, it's hyperstaked -datadir=/some/predefined/directory to launch the daemon and then hyperstaked -datadir=/some/predefined/directory <command> from there out. I actually use this a lot to have multiple copies of the blockchain. Again, this is totally optional.

You might want to define the ports (rpcport=<port> , port=<port> ) but if it's not giving any conflicts, that's totally optional. I always run txindex=1 so I have ALL block transaction data, but that too is optional. It looks fine.

Mainly for speed, and also for the new guy trying to get synched. Good developers try to maintain an up to date bootstrap so that new people don't have to wait (sometimes literally) days to get up to speed. For instance, bitcoin synching from a bootstrap takes around seven hours. Synching from the network can take over a week.

On smaller coins, it's more a convenience. Also, it is possible for your local copy of the block chain to get corrupted, and a bootstrap will get you to a reasonable block height and allow those last few blocks to synch fast, instead of starting from zero.

Yes, but that quote is damn near exactly how the sons of bitches SELL this stupidity to the American public. We are, despite what it often seems, a very insular society. Do not mistake the actions of the United States of America for the will of it's slaves. Most of us don't like, or trust our rulers. But most of us are complacent, and afraid. The country that I grew up in does not exist anymore. It's now a police state very similar to Germany just before the ascent of the Nazi party to ultimate power. There is more wealth, and the nationalism is less targeted (slightly), but it's very similar.

And fuck Godwin, this is reality.

Fair enough. I often use the command line even when I have the GUI available, so I guess it comes down to taste if you have the resources

I have to wonder why you're running QT on such a limited machine. Wouldn't it be simpler and smaller to just run truckcoind or hyperstaked per your other adventure?

Yes, you put it in (in this case) .hyperstake (or the windows/Mac equivalent) and then delete everything but wallet.dat, hyperstake.conf and bootstrap.dat

The reason for renaming it is that the core code looks for bootstrap.dat to import a static blockchain, and it imports the whole freaking thing before indexing it. That saves a shitload of time. The reason for not just copying the whole .hyperstake (or whatever coin) data directory is that the data may be corrupt, have transactions only specific to your wallet, etc. And of course, the size. Everything that is needed for the client to extract all that information is in the blk000* files. There are several of them as the blockchain grows, so if you're making a bootstrap AND there is more than one, you need to combine them in serial order. It's easy to do, and it will save you endless headaches when synching a new install or recovering a messed up wallet install.

Another thing I do, and highly suggest if you're not running on a Pi or something tiny like that is add txindex=1 to your configuration file. This pulls ALL the blockchain data, like a block explorer. so you can pull up the data from any valid block in the chain in your own client, not just the ones you had a transaction in

https://ecua.mobi/how-to-create-bootstrap-dat/


There ya go. I used it once, but didn't have a download directory setup. I do now, and once GMC is fixed, I'll be using this script to maintain a constantly updated bootstrap. Might do the same for all the coins I collect Though that would require a bigger server than I have right now. At any rate, the script works with minimal modification, or you can just do it manually. You MIGHT need to run this as root or chown your blocks directory to make it work, though.

I'm not home right now, but I have a script for it. Basically it's a script that gathers all the BLK000*.dat files in order and put's 'em together, renames the output bootstrap.dat, and then copies it to your specified directory for download. Can be set as a cron, so it stays up to date. I've only used it once, I usually just do it manually. (cat blk0000 blk0001 blk000* ... > bootstap.dat

As long as it's not conflicting with something else, it really don't matter. 22, 587, and about five others are system ports and illegal for RPC or P2P, but that's about it. I often run multiple instances and just set whatever port I have available so that they don't conflict. I don't remember the ports that were supposed to be assigned to HYP, but it practically don't matter as long as they're not the same as something else you have running.

A very special thank you to Noise23, who has been working with the GameCredits team (mostly with me) to solve our stuck blockchain. Once again, he has proven to be a gentleman and a scholar!

That's not new.

HYP was forked from TRK. What you do is make sure that the port and rpcport are set to different ports in your hyperstake.conf and truckcoin.conf files. That is in the wiki, I'm pretty sure
EDIT: Ya ninja'd me

As for the gentleman with the error message, it's not critical. Presstab did do an updated client a few days ago to eliminate the warning, but it's only an irritant. Nothing will hang, stop, or otherwise cause you problems, it's just obsolete code that he hadn't gotten to yet.

Brief update:

We have discovered what the problem is, and have (in testing) made the chain move. We probably need about two more days to have a release ready.

This WILL be a hard fork. The lack of notice is due to the emergency, it would have been far better if we'd forseen this and been able to make a smooth transition, but the ugly truth is that the blockchain was solidly stuck. It's something in KGW, which is not in the new client. It's still a 1 block difficulty retarget, taken from another coin that has been very stable. More details when everyone is ready, but in testing we made it work.

The first release is likely to be a bit ugly, as we're trying to get things working correctly ahead of making them pretty. Then we will release non mandatory updates as quickly as we can to make everything nice.

Vegas, PM me, or Noise23, or both. I'm the mouthpiece, I don't know if the beta is useable at this moment.

Aye. What Ross did, if he is indeed DPR (I am not convinced), was to do what they do without their sanction. If he had done it with their sanction, any harm he may have done would be ignored.

A politician wants power like a drowning man wants air. Before becoming a full fledged anarchist, I briefly thought the Repugnicans had better ideals than the Democraps. I worked on the camapaign of a (now former) state governor, and met most of the republican leadership during that time. They were almost all truly evil men, in every sense of the word. But even the few who weren't still wanted that power. They wanted to do good with it, but wanting the power was FAR more important than what they did with it.

This is one of the many reasons I run Linux. Better control over RAM but yes, it sounds like high cpu usage. Basically, either get more ram, or deal with it freezing up from time to time, or close some of your wallets till you're fully synced. Synching itself is rather cpu intensive. Staking moreso.

Here's what I do. Not just with Tek, where I rarely have problems.

First run getpeerinfo, and copy all of your current peers to a text file. Just in case. Stop the client or daemon.

Then, go into .tekcoin folder (or users\<username>\appdata\roaming\tekcoin if windoze) and edit tekcoin.conf to remove or better comment out your addnodes. All of them. (#addnode= makes it invisible to the client).

Now, delete peers.dat and restart the client or daemon.

Wait about ten minutes. usually it will find good peers.

Thou hast reclaimed your identity?