If all goes well, confirmations should eventually be brought down to a reasonable number. That should reduce the possibility of that happening quite significantly.

Huge improvement on CPU usage. I run the wallets on older PC's and they are both responsive now while staking.

Reply sent.

How much in being "staked"? Staked coins are not available until the stake reward is confirmed. Currently it takes 510 confirms.

I reinstalled 2.03 last night and got it running again. Just installed 2.04. So far so good.

I didn't like it. Wouldn't load at all. Reverted back to original .conf file.

I'm giving the .conf idea a try. I copy/pasted the original .conf file and then deleted the nodes from the original and pasted the list from the explorer.

It's quite possible and it's really only a couple of lines of code.

I'm having trouble synchronizing one of my wallets. It's trying to download blocks beyond the current, 835297. This may be due to people running older wallets. It may be necessary to update the next wallet (2.04) to reject any connections below 2.04. This had to be done for Feathercoin if I remember correctly when they were switching to a centralized coin structure.

You can also use the options menu. There's a reserve feature right in the main panel.

As with any staking wallet, any balance in staking cannot be spent until the stake has been confirmed. There is a way to limit how many coins you'd like to have available for staking at any given time through the console menu.

POST is a little different from some of the coins I've staked. Block counts can be a little random at times because although it's supposed to be uniform across the network, sometimes people who you connect to are just like you, reloading the wallet at the same time so the consensus has to readjust accordingly. I've seen my arch wallet go in and out of sync several times before finally settling on the consensus.

The calculation total is different. Usually a staking wallet will shove the coins staked in the "staking" area and they won't release until your stake has confirmed. Depending on how you've added coins your stake will be a random amount and your unstaked coins will remain in the spendable column. It's possible for more coins in the spendable to begin staking also following a found block, and as confirmations occur it gets slowly released into the soendable column. Come to think of it, that's most likely why the first workable release is staking so slowly and blocks are long. Two reasons: 1st, not many people are staking so there's a smaller percentage of available stake possibilities and 2nd, many of us who are staking have wallets with long coin ages so the entire amount gets popped down into the staking column and we have to wait for our stake to confirm before finding another block. However there is that problem of both values showing up between spendable and staking and it appears to be doubling, it isn't. The software is just tossing your spendable back and continuing to wait for your "stake" to mature. We won't know how it's really going to react until we start seeing matured stakes imo.

DO NOT open the same wallet on two different computers. It can corrupt the wallet. You can transfer some coins to a new wallet and then stake on two computers with two different wallets, but I'd wait until the blocks start happening more regularly to do so.

You're the only one. Things often need tweaks and adjustments before they work properly. Quit whining and have a little patience.

Not sure what's going on. There are new blocks being found and it appears it's all on one chain. I haven't found a block since the first one, but I see more blocks being found as the days progress. The staking process appears to be functional, slow as it is.

More or less. I ran the ARCH wallet on an Asus netbook with an Intel Atom n270 CPU, still found blocks. I found one block already with Solarcoin on the same netbook computer. But after nearly 24 hours and 33 blocks found, the network doesn't have enough participants yet to really get the ball rolling. I have to repeat though, sometimes it can take days to find a block. Other times you'll get a few in one day.

You can go days and sometimes weeks without finding a block. The more participants on the network, the greater the chances of anyone generating a block. It's really just a numbers game.

This part could be fixed. It does seem a bit cpu hungry.

That's how staking works. Those percentages are a representation of your chances of generating a block with your network weight taken into consideration. Though post is a little different. My experience with staking other coins shows this behavior as completely normal. Some will not be accepted, which is also normal.

It's counter intuitive. Often you'll notice that your wallet will display now as the time it will generate a block, which means your wallet is ready to generate one, but you still have to consider coin age, and whatever else post-staking takes into account while running through its algo.

This wallet staking behaves like every other staking coin I've worked with.

I have a strong feeling that the mathematical error was caused through anomalies in the math due to the nature of switching from pow to pos. Few people were running the wallets and the software couldn't cope. It looked like a mathematical overflow error. I have some experience in programming, older machines, but the principles are the same and the same kind of errors occur when you overlook a detail like that.