If your block was strong enough to stake on both forks, it would have been included in the longest chain, not waiting for someone with barely any coins to determine it.
I honestly don't understand what this means. There are different PoS mechanisms, but I was thinking of just any mechanism where "randomly" someone can stake, and nobody else, and that the probability of it to be you, is proportional to your stake ; I don't want to go into details of how this is done (there are different ways). The idea was simply that at this point in chain and time, it was Joe's turn to stake. And then Jack's turn to stake. And then....
It is just stupid because IT NEGATES YOUR STAKING POWER TO DETERMINE THE LONGEST CHAIN!
But you don't care about that "power to decide". You only care about reaping in the reward. We were thinking about otherwise "honest" stakers, that do not want to double spend or anything. Just reap in staking rewards (minting). You mint wherever you can, because that's why you are staking in the first place. Not to impose any decision you don't care about.
And running a Multistaking wallet will increase the memory & CPU requirements and energy needed.
This very very small "proof of work" doesn't compensate the possible loss of a minting reward if ever your chain doesn't win because of propagation delays in the network, or because of an orphaning 5000 blocks from now.
I suggest you pick a PoS coin at least 3 years old and attempt to write a Multistaking wallet,
so you can learn 1st hand you are wasting your time.
Also when you are done , you can post the differences in hardware resources used verses a single wallet version.
Multistaker will require more resources, depending on the ram & cpu requirements.
So your PoS is in fact PoW ?
But what you will find out at the end of the month is the single chain client makes just as much money as the multistaker while requiring less resources.
If nobody is multistaking then 1) you cannot know and 2) then the consensus is just imposed by randomness (which is good), but you are not protected against multistaking. That's the point. As long as people only run official "random selection" staking algorithms, indeed, PoS will find a consensus. But it is vulnerable to multistaking and having no possibility to come to consensus. It's most probably because PoS is only used on rather small chains with not much at stake, that nobody has been implementing multi stake algorithms.
Also is your Multistaker going to be able to run on 2 forks or 4 forks or 8 forks at the same time.
Looking forward to watching you attempt it.
Of course, that is exactly the divergence of consensus that is the "nothing at stake" problem. If, however, people are so gentle as to adhere all to a random selection algorithm and not multistake, then by definition, this divergence cannot happen. That is similar to saying that if nobody is attempting a 51% attack on a PoW system, then the chain is secure with PoW.
The Block is Chosen by the CoinAGE not the amount of coins.
[Coin-age] = [amount of coins] x [days in stake]
Huh ? But what if you have 2 identical blocks, where only one single transaction is different:
Block A: Mary has spend 10 coins that are 517 blocks old to Joe
Block B: Mary has spend the same 10 coins that are 571 blocks old to, Janice.
Block A and block B are identical except for this double spend. (this is the ONLY case where consensus is necessary).
Now, Alice receives block A at 12:00:02 and mints block C on top of it. However, it only gets to Joe at 12:01:00, but gets it at Jake at 12:00:30.
Alice receives block B at 12:00:08.
Bob receives block A at 12:00:09, but received block B at 12:00:05, and mints an IDENTICAL BLOCK D = C on top of it. Bob gets it at Jake at 12:00:45 and at Joe at 12:00:45.
So now Jake receives Alice's chain before Bob's and Joe receives Bob's chain before Alice's.
So Jake will build block E identical to block F on top of Alice's chain
Joe will build block F identical on top of Bob's chain.
Everybody is honest here. But at the end of the day, after I don't know how many identical blocks containing identical transactions, there will be a difference, orphaning one of both. As long as all stakers include all the transactions in the common mem pool, their blocks are identical according to your criterium, and the double spend by Mary is not resolved by consensus on both prongs.
Just because two users have the same amount of coins per block, does not mean the CoinAge will Match.
The CoinAge Factor is excluded because it destroys the LIE.
If the transactions are identical, yes. And you stake for sake of the minting, not because you want to decide something.