Hello , Im still little bit confused about steelth minting process. I tried to found answers on bittalks and also steelth forum with no results , decided to write to the dev and thanks for him I got answer but need more info So here is the question and answer:
Q;How it is that when I received Steallth coin for example 1000 coins in one transaction and each coins has same "staking" day. after couple days only some of them are staking , than there is a brake for couple days and another part is staking. Is not that all coins supposed to have same stake day as they were reset when I receive transaction? How it works ?
A;Staking works exactly as you described: the whole number of coins in the wallet in broken down to small chunks and these chunks stake separately. The whole number of coins stake only on the first staking: after you receive the coins in your wallet, the entire number of coins stake. Then coins are broken down to small chunks for staking.
So as far as I understand minting is depends by how many days your coins are on the wallet and actually how many of them you have - when the amount is reaseneble big than the passibility to stake in third day is bigger. However if I receive 1000 coins in one transaction their age is equal. They are broken down to small chunks (1. Are chunks broken for equal parts? For example from my 1000coins it will make 10 x 100 coins ?) If yes shoudnt be that their "weight" is same and they all supposed to stake in same time - that means all coins start staking in same day?
When they staking I receiving small parts of minting as a transactions - and suddenly minting stop - is it this 15-th day? Than as dev said the amount are again split to chunks - (Is that also their age are "reset" and again need to wait 3-9 days? To make staking?) Is that true I will receive 20% annual if wallet open and connected 24h/365 days?
Thanks for all answers:)
Q;How it is that when I received Steallth coin for example 1000 coins in one transaction and each coins has same "staking" day. after couple days only some of them are staking , than there is a brake for couple days and another part is staking. Is not that all coins supposed to have same stake day as they were reset when I receive transaction? How it works ?
A;Staking works exactly as you described: the whole number of coins in the wallet in broken down to small chunks and these chunks stake separately. The whole number of coins stake only on the first staking: after you receive the coins in your wallet, the entire number of coins stake. Then coins are broken down to small chunks for staking.
So as far as I understand minting is depends by how many days your coins are on the wallet and actually how many of them you have - when the amount is reaseneble big than the passibility to stake in third day is bigger. However if I receive 1000 coins in one transaction their age is equal. They are broken down to small chunks (1. Are chunks broken for equal parts? For example from my 1000coins it will make 10 x 100 coins ?) If yes shoudnt be that their "weight" is same and they all supposed to stake in same time - that means all coins start staking in same day?
When they staking I receiving small parts of minting as a transactions - and suddenly minting stop - is it this 15-th day? Than as dev said the amount are again split to chunks - (Is that also their age are "reset" and again need to wait 3-9 days? To make staking?) Is that true I will receive 20% annual if wallet open and connected 24h/365 days?
Thanks for all answers:)
It was me that answered to your PM, but I`m not the dev
I`m a XST investor. It`s not necessary that all "chunks" stake the same day.
After about 20 days your wallet begins to mint everyday.
Yes, it`s true. The POS ROI is 20% annually.
So many people are trying now to copy XST`s code
Exactly: with 100 XST in a staking wallet, you earn 20 XST annually. I`m not sure though what`s the minimum amount to stake.
Don`t worry, the dev is here and cares about the coin
Scroll back our thread: when the StealthClient got effected by the daylight savings time, the dev intervened promptly and solved the issue. 
