Topic: LUXCoin—New PHI2 PoW/PoS Hybrid—SC—SegWit—PrivateSend—PoS Web Wallet—LuxGate - page 112. (Read 130258 times)

Any calculators for GPU vs Hash Rate ?

Did you notice that the date of the Pre-mine Burn shifted to  Q1 ? 
Meanwhile ฿0.00164004

No active connections to the network from the new wallet - any nodes I can add?

How many coins in the pre mine are they burning?

Did you notice that the date of the Pre-mine Burn shifted to  Q1 ? 
Meanwhile ฿0.00164004

If I read correctly staking will happen again soon. Do we need to do anything to facilitate that or will it happen automatically if our updated wallet is unlocked for staking?

Before any wallet update make sure to backup the wallet.dat file.

In the first post of this thread they have the link to the 4.0.0 version, since they haven't updated the link yet. But you can see the link starts like this:  https://github.com/216k155/lux/releases

That will take you to the page with all of the releases, including the latest 4.0.1. Good luck!

How can i update it?

Is your wallet synced? Have you updated to the latest wallet (4.0.1)?

73 confirmations and almost 4 hours now. Are my coins lost?

Anyone have idea why is this happening? I transfered the coins to cryptopia

Now it's 46 confirmations.

TX Id is: 1d9e6de0962567e14fef3390ae6802c01d7cd6980d1c40630cd7b41c4069639d

but sitll nothing showing up... what's happening?

WHEN WILL STAKING START?
Staking will start once the testing is completed on the new-unique-to-Lux PoS Hash function and the code is released. To ensure expectations are set correctly and not to put undue pressure on our development team, there is no hard public date set for this one except that this will be soon.


AM I LOSING MY MN AND STAKING REWARDS?
1. No, You are not. The coins which are meant for PoS and MN are not being mined at the moment.
2.Once active, the 720 coins meant daily for Pos and MN will be available again.


WHEN WILL FINAL WALLET BE RELEASED?
Currently we have released Beta version. Final official release is after we have taken in all feedback, completed testing and post PoS hash re-introduction.


WHEN WILL COINBURN/SEGWIT HAPPEN?
Once the top priorities are completed and released successfully (PoS activation and wallet release).


WHY DO YOU HAVE TO DELAY COINBURN, ISN’T IT SIMPLE?
As simple as it may sound, it is not considering we are reducing overall supply. We do not have the bandwidth to properly perform this and document the same for proof. (Some background on coin burns: https://medium.com/@alcio/how-to-destroy-bitcoins-255bb6f2142e)


WHY DOES MY WALLET TAKE SO LONG TO SYNC?
Due to DDoS, initial seeds were "overwhelmed". We have added more seeds and this is being addressed


WHY AM I GETTING ERRORS ON THE NEW WALLET?
This is a Beta release. An open beta release means the software is in the beta stage-feature complete- but likely to contain many known or unknown bugs. The focus of an open beta release is to get feedback and improve to eliminate bugs and to incorporate feedback from end user testing for the official release.


IF IT WAS AN ALPHA/BETA RELEASE, WHY WAS IT MANDATORY TO UPGRADE?
Both upgrades served different purposes. Alpha release ensured we are on the upgraded protocol as all previous versions were invalidated at 180k blockheight. Beta supports the PoS hash implementation for staking and Masternode rewards.


ARE YOU KIDDING US?
No we aren’t. We are as disappointed as you are, with the delay. We are now following a more pragmatic approach that is in the best interest of the community and the network.

Hi,

I sent my LUX coins from my wallet to Cryptopia. After about 2 hours and 27 confirmations still nothing is arrived....what's the problem?

Updated to wallet 4.0.0996 beta aka 4.0.1. Two major issues:

1) In previous wallet it was necessary to encrypt wallet, then unlock it to stake. Can't encrypt / unencrypt wallet in 4.0.1 ("encryption" is greyed out). Other than than locking and unlocking wallet again doesn't seem to enable staking either (I believe we are well 36 hours into post block 180K).

2) Closing the wallet and opening again creates "database error" and then the wallet needs to reindex blocks from disk again, which on a fast SSD coupled with a 8600K @5Ghz takes over 15 minutes. That's just not okay. I believe another user had this bug as well.

Can anyone report that issue 1) and issue 2) has been resolved / working for them?