Another thing worth noting is the switch from a 10% interest cap to 2% at height 836213 (roughly the time the conflicted transactions occurred). i still have two interest payments being confirmed in one wallet, but another wallet now has a conflicted txn that was being confirm.
Keep staking and keep an eye on the number of confirms, if/when it gets conflicted. (Seems like if it gets past 4 or 6 confirms, it's good to go, which indicates a possible conflict between older (un-updated 2.0) wallets and the new 2.0.7.)
EDIT: One just came in, so I'll see how many confirms it gets.
EDIT: Two came in. One with 9 confirms now and one with 6.
EDIT: 7 have come in now, and they all appear to be getting confirmed.
EDIT: Current height is 836908. Current blocks per hour is 53. Current inflation is at 1.235%.
-Steve
Good food for thought! Thank you!
Just for the record, here is what my wallet with the biggest number of interest transactions shows (again, this is after installing 2.0.7, downloading & applying latest bootstrap, then re-scanning wallet):
(all times shown are in New York time zone; transactions listed without omissions)
-Unaccepted Interest at 15:13, a minute after block 836413
-Interest (accepted) at 15:18 at block 836418 (trns d95dd41661ccb7293e5b5f1ea52a99b276a9db051a4a4e408b304988b43fdffd) - (accepted, 611 confirmed as of time of writing this).
-Send transaction at 15:20 at block 836762 -
this was NOT sent by me at that time; I assumed t
he new fixed bootstrap reload may have resulted a re-broadcast of a previously unconfirmed transaction. (trns 0cdc46facc62f08b55c73db5d1b493354e477fb1baebe421b24ec12339796c9c)
After that point, I started seeing the amount of 5075 SLR (or 5085, don't remember exactly) showing up in the Unconfirmed stats, then going back to Spendable, I guess first having been in Staked. This process was repeating - and matches the following long list of Unaccepted attempts of that amount to stake.
The 5075/5085 amounts are listed as input/output of the Send transaction described above.
https://chainz.cryptoid.info/slr/tx.dws?0cdc46facc62f08b55c73db5d1b493354e477fb1baebe421b24ec12339796c9c.htmthe list of transaction history continues as follows (soon after block 836762):
-Unaccepted Interest at 15:34 (trns 6f6b334b37799fe3873c5eb30a3cd89b23180fbd098860f3e569dd900bb419cc, address: 8afk5pWMQACZkyKy83LNNTBwM5LUA5M2pF, also appearing in block 836413!)
-all following Interests are also Unaccepted, counted 49 of them, up to 20:50. last trns in the list - e435762f8baffd90db42f48e64c8651255a169f92c9fac5f0f346b7797caae32
Many of these were also for that same address as the first one above, but there were also other addresses trying to stake and not accepted.
-Interest which is still being confirmed (246) at 21:03, address is the same 8afk5pWMQACZkyKy83LNNTBwM5LUA5M2pF.
-Long list of Interests which are still being confirmed until up to now (and apparently will be), with only one Unaccepted at 23:31.
On another wallet, the Reload Blockchain I did (but still using the new bootstrap that came with 2.0.7) resulted in an out-of-balance issue (30000 SLR from the wallet "disappeared", only ~1000 left). Then I did a re-scan of the wallet and balances got fixed.
This reminded me of the "spendable + staking = total > real total" issue, which so far appears after an upgrade and looks like a re-scan fixes it. I will now post another separate note on that and will need some feedback from people seeing that issue. This IS related to yet another issue with a Windows error message that appears at auto-restarting when Rescan Wallet is selected - when the Windows error message pops up, a Wallet Rescan is NOT initiated after manually starting the wallet, so then one thinks they re-scanned but actually that did not happen.