k0vic this is my post from earlier today:


So some hours later I came back to my laptop to see I had received another stake, this time for 30 Tron as we'd gone over block 4000, but again my wallet had gone into "Not staking as none of your coins are mature" mode. I don't know if this involves the staking going to "false" as I didn't know to even check for this prior to reading your post. I left it for a while to see if it would come good. After approx an hour since the stake had been received it was still in the same "Not staking as none of your coins are mature" mode. I left if for another half hour and was about to reboot it again thinking there's something wrong when it suddenly started staking again with 'weight' all the way back to 1 (and that was over well over 6 hours ago and my 'weight' is now 538 so expecting another stake any moment).

I guess the arrival of the staked coins sends it into "Not staking as none of your coins are mature" mode for a short while. Next time it does this I'll check to see if the staking status has change to 'false'.

Arielbit. The buffoon of such a high standard of buffoonery, other buffoons are falling over themselves to emulate....

I installed the new wallet the Dev tweeted at around 1230 utc. This immediately resolved the problems the previous QT wallet had been having. It started staking within a few minutes and I then received 2 payments just minutes apart. The 'your weight' had come off the boil a bit as a result of the payments (I guess) but it was still staking happily. Went to bed about an hour later and at around 2030 utc this morning I checked to see if any further stake payments had been received overnight. Nothing further had come in and unfortunately the wallet had gone back to "Not staking as none of your coins are mature"!

Played around with it for a bit but it didn't look like it was ever going to be rectified, even after restarting the wallet. Eventually decided to reboot my machine (Win 8.1) and start the wallet up again. That seemed to do the trick and, although it initially had the 'coins not mature' message, after a few minutes it started staking again and within an hour I'd received another payment.

Has anyone else had this happen where the wallet's stopped staking? Does anyone know why that would happen and how to mitigate it?

Okay, so conventional wisdom says if you see an order book where there's a far steeper rise in asks than there is in bids, there's far more sellers than buyers. It's one of those supposed 'no brainer' right-there-in-your-face indicators. But my experience in this space shows that often this supposedly obvious indicator is actually completely misleading.

For a start, when the depth chart isn't centred properly (as is the case with the one you've shown) you can see asks rising steeply but (seemingly) without corresponding bids, but those asks are way off to the far right so although (again at face value) there seems to be more sellers, the depth chart may in fact have a corresponding number of rising buyers further down the pricing scale, but they're just off the graph to the far left not visible, so it's not balanced.

But more importantly than this, just because there aren't large numbers of bids but there seems to be large numbers of asks doesn't automatically mean the price isn't going to rise. Again and again I have seen just this profile and I've thought just what you're thinking (this isn't going to spike much as the steep ask angle will put a stop to any rise pretty quickly and the limited bids indicate limited buyers). But I've been wrong more times than right when thinking this way and, even with a steep ask angle in the order book, the coin has still spiked up substantially and chewed through all those asks to go way beyond the limited band of trading the order book suggested was likely. Often the asks will start being pulled as people see it accelerating upwards because they're suddenly worried they're going to miss a major rally by selling too low. Of course at some point the inverse is true as major volumes of asks start being added back on to the books where people think the thing might peek (but if there are committed whales with a lot of BTC available they can pump it, particularly if most of the increasingly high asks are their own to help power the pump by buying and selling to themselves - all part of the gross levels of manipulation that go on ad nauseum in crypto)

And the other really huge factor is when whales starts accumulating. The order book depth doesn't indicate this at all. The downward pressure of the past couple of days is likely to be a mass accumulation occurring. That means a handful of whales are getting ready to pump it by severely limiting what's for sale until it reaches a new ATH (or like with what happened with Crave) one far greater than the ATH many times over.

I guess what I'm saying is there are dozens of scenarios on how these rallies and manipulative pumps work. Those order book depth charts do not tell a succinct story of how things are going to play out. It could be a wild ride similar to what happened with Crave, or it could just fizzle out and everyone will lose interest. Anything's possible.

There are many differing scenarios on when the profile of an order book determines a set and known outcome. The depth of buy and sell walls, the ascent and descent angles all mean differing things depending on where an asset is at in its development cycle. Rather than just posturing a view with statements such as


perhaps you could be more specific about what exactly leads you to this view (i.e. features and aspects of the order book profile) and what exactly you think is going to happen.

Such eloquence....

Mining has finished now (at block 3400).

There's a dynamic PoS period now for approx 30 days where you will get increased and varying staking rewards for holding coins in your wallet. Go to the OP on this thread to see how it works.

Yes, I'm on 3522 too.

Thanks for your attempt to get a working wallet to us all NSCrypto. It did run again after reboot. But as soon as the dev's tweet was posted I've downloaded the official updated wallet and am running that now. Seems to be okay and I'm staking again.

Oh dear, just when I thought my problems were sorted it just crashed.



Can't get it to go again now!!

Dev...where are you??!!  We need a working wallet!!!

Okay thanks. Still saying they're not mature. Hopefully what you've said is correct and it will start staking again soon.

I'll let you know how it goes (and I'll send you the first stake too if all goes well!)


PS - Canada's only a short hop, skip and a jump from Australia (NOT!)

Okay thanks NSCrypto. I've just installed it (feeling very exposed though....only that you seem genuine enough from the way you've written your posts have I decided to risk it. What part of the world do I need to travel to if all my coins suddenly disappear? Ha!)

It seems to be running okay. Here are three 'getinfo's done in quick succession that show it has caught up to the current block (I think)


20:31:28

{
"version" : "v1.0.0.0-g32a928e",
"protocolversion" : 60014,
"walletversion" : 60000,
"balance" :,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 3398,
"timeoffset" : 0,
"moneysupply" : 997680.00000000,
"connections" : 1,
"proxy" : "",
"ip" : "0.0.0.0",
"difficulty" : {
"proof-of-work" : 46905416.78901562,
"proof-of-stake" : 0.00024440
},
"testnet" : false,
"keypoololdest" : 1428949250,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"unlocked_until" : 0,
"errors" : ""
}


20:32:47

getinfo


20:32:48

{
"version" : "v1.0.0.0-g32a928e",
"protocolversion" : 60014,
"walletversion" : 60000,
"balance" :
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 3466,
"timeoffset" : 0,
"moneysupply" : 1005440.00000000,
"connections" : 4,
"proxy" : "",
"ip" :
"difficulty" : {
"proof-of-work" : 50455053.71080633,
"proof-of-stake" : 0.00024414
},
"testnet" : false,
"keypoololdest" : 1428949250,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"unlocked_until" : 0,
"errors" : ""
}


20:33:02

getinfo


20:33:02

{
"version" : "v1.0.0.0-g32a928e",
"protocolversion" : 60014,
"walletversion" : 60000,
"balance" :
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 3497,
"timeoffset" : 0,
"moneysupply" : 1006060.00000000,
"connections" : 2,
"proxy" : "",
"ip" :
"difficulty" : {
"proof-of-work" : 50455053.71080633,
"proof-of-stake" : 0.00027445
},
"testnet" : false,
"keypoololdest" : 1428949250,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"unlocked_until" : 0,
"errors" : ""
}


Unfortunately I'm back to "not staking because you don't have mature coins" so I guess will have to wait the 8 hours (or 7 or 6 or 9 or whatever it is) to get staking again.

So are you inferring that this compile you've done rectifies the issue currently being experienced with the Windows wallet?

It defaults to look for "positron.conf" (unless you specify something different using a command line option).

C-CEX is currently showing a status of "maintenance" for their Positron wallet.

There are clearly ongoing issues on the network over and above the Win wallet problem. The PosiTron Block Explorer at http://45.33.72.95:3001/ is now stuck on 3447 at this time whereas Bittrex is on 3476.

In the existing Win wallet we're waiting for the dev to fix?

What block are you on?

I received one 20 Tron stake payment earlier today prior to the fork. It's still immature at 105 confirmations. And All my balance is sitting in the "Stake:" status  but the wallet is continually 50+ blocks behind. Currently (as at 09:37 utc) it's at 3387 of 3439 blocks (whilst at the same time the PosiTron Block Explorer at http://45.33.72.95:3001/ is at 3447).

Not sure how you can be staking though as the arrow status icon down in the bottom right corner is grey on my wallet while ever it's in this condition.

I don't think anyone knows at this stage. I'm on 3367 of 3417 too but this PosiTron Block Explorer http://45.33.72.95:3001/ says we're at 3433.

Looking in the debug.log file for the wallet there are (on my mine at least) hundreds of connection time-outs where the wallet's trying certain peers but they're not letting it connect.

Until we hear back from the dev we can't do too much about it I guess (unless there's a QT expert on here that can work out how to put appropriate addnode= or connect= commands into a positron.conf file to force the wallet to go to specific peers, but I have no idea whether that's even something that would resolve the issue).

Hey positrondev,

How's the fix for the wallet coming along? I know in a recent post you said you were exhausted so perhaps you've fallen asleep??!!

It's been over 2 hours since your post above saying


and I know many are keen to get their PoS staking happening.

Interestingly though, there are still PoS payments being made.

This address has had two in the past 10 or so minutes. Are these from a different type of wallet to the Windows one that's now stuck?

http://45.33.72.95:3001/address/PQE887VdHaY2KSQBxVbLtEWBPKKyztCeTP

Is there anything we can put into a conf file on the current wallet to force it to connect to peers that are on the correct chain as per http://45.33.72.95:3001/ ?

Mine did too but it's on the wrong chain. Has "synced" at 3349 where as

http://45.33.72.95:3001/ site the dev gave us a page or two back is at 3413

Still awaiting new wallet. I had deleted peers.dat and done a -reindex on the old but must still be on the wrong chain as I've said.

Yep, me too




What's up mods? You're not normally this virulent.

Further update. After playing with it for a bit longer I've found I'm more like to have peers showing in the network monitor when I turn off the Wi-Fi and just leave the phone connecting via the 3G network.  That's not to say I haven't seen it connect to peers while it's on the Wi-Fi (which is my home Internet connection that works perfectly well for all other devices connected including this phone).

Yes, it's a very old version of Android now (2.3.3 on a HTC Desire Z). I just can't bring myself to upgrade my phone as the new ones are all much bigger (which I personally don't like) and this one's worked so well for so long now. But there are some apps that don't work properly and this could be what I'm experiencing. I'll be forced to go to a new phone in the not too distant future.