My withdrawal issue had been resolved by STEX.COM. The coin was returned to my STEX wallet and I was able to withdraw it securely to my personal wallet.

Please don't ask them to re-scan their wallet. There is nothing wrong with the blockchain or syncing. They can lose Tx_key and other transfer information if they deleted their wallet cache since the receiver address and the Tx_key are stored on local cache. I am still talking with them to solve the matter.


They may not want to give Tx_Key for the following reason:
1. Transfer to Multiple wallets at the same time uses the same Tx_ID and Tx_Key. However, sharing Tx_Key in this case will not affect other recipient because the recipient address is needed together with Tx_key in order to decode the correct result, and since there is only 2 outputs (minimum) at the transaction, there is no other recipient in this transaction.
2. Multiple Claim. Those holding Tx_key can claim that he's the one who transfer the fund to you. (example: You requested 1,000 LTHN payment from 2 persons. Person#1 transferred you 1,000 LTHN. But since Person#1 posted its Tx_key and Tx_ID publicly, Person#2 can also claim that he transferred 1,000 LTHN to you too). Nobody can prove who is the actual sender as no sender information is stored on the transaction.

For this case, since the receiver only expected from one sender and since they were accused for transferring the coin to wrong wallet, they must come out with the Tx_Key. Or at least provide a screenshot at blockchain explorer with a proof that they transferred it correctly.

For monero-based coin like Lethean, there is another tool called Tx_proof which can solve all the security issues of sharing Tx_key. Tx_proof is generated using Tx_ID + Tx_key + Recipient address, and therefore it's unique for each recipient address. Multiple claim is also not possible since only those with correct Tx_key can keep generating different but valid Tx_proofs for a transaction while false claimer can not.

There is no reason for not sharing Tx_proof for any transaction. I recommend all exchange to provide Tx_proof for their withdrawal process.

Affected Coin: Lethean
Details: Coins not arriving at wallet when 16-hex (8 byte) payment ID is used even though valid Tx_ID is given.

Withdrawal issue had been RESOLVED by STEX.COM.

What I can say up to this point, STEX.COM is not a scam. They are here for real business, but their support team has a lot of room for improvement.

Special thanks for LETHEAN team for assisting me solving this issue.

Dero has a good tech. It could be one of the most innovative coin among others.
However, since the main product isn't yet delivered, it's difficult to gain trust from wider user base especially with the premine issue is not yet solved. The development can be halted once the premine is dumped (which can happen anytime). Whoever investing now is at the mercy of the anonymous dev team.
The risk is extremely high for investor.
If the dev team decided to lock the premine (which I hope so), it will reduce the risk for investor therefore it can attract more people with stricter risk profile.

I understand the premine is wholly belong to the dev team since they are the one who started Dero and work the hardest. My suggestion is to lock the premine according to the progress of the Dero project itself. Once the whole product is out, the Dev team can dump their premine. or Save some since they should believe in Dero too.

For those expecting moon, good luck and see you on the other side of the moon.

Good points. But your additional components are actually good factors that create FOMO instead of adding more FUD

FOMO = NBS + NF + OD

FOMO: Fear of Missing Out

If FOMO > FUD then [People will buy and price will go up]
If FOMO < FUD then [People will sell and price will go down]
If FOMO = FUD ---->>>> Stagnant.

I am not trying to stop Dero. I support Dero. But if I can contribute to make/push it to be more open/transparent it'll be better for the community as a whole.

FUD Formula:
FUD = AD + NT + NAeP + CPiT + URP + NSC + PoR

FUD: Fear, Uncertainty, and Doubt
AD: Anonymous Developer
NT: Non-Transparency (e.g. unlocked pre-mined wallet / secretly transferring out the pre-mined balance)
NAeP: Not addressing existing Problem correctly (e.g. uncontrolled block/side-block generation, coin emission is not as per whitepaper.)
CPiT: Communication problem among team member (e.g. key team member(s) suddenly left)
URP: Unreleased Product
NSC: No Source Code Released
PoR: Personal Level of Risk-Tolerance

I think it's logical and normal to have some FUD in this project. Once all components are removed, the FUD will be gone by itself.
Currently buying Dero is like gambling with your money. If you can't afford to lose your money, please stay away and watch. Otherwise, let's FOMO, cross our finger and support the development team so that they can deliver the new crypto tech.

Hi, all. I saw the posting regarding pre-mined balance on the ANN page #1.
First, I am here not to create FUD or anything.
I just tried to generate the way Captain took the screenshot. That screenshot doesn't show any SPENT balance on the pre-mined wallet. The actual balance could be as it is shown or it could be "0" or anything in between. Anyone with their own wallet (which is spent before) can try to generate both "Full Wallet" and "Watch-able View Key Only wallet"; and compare the result.

Please check the following screenshot for my generated wallets:



Transparency is the key for any coin to success. Many with FUD will come here to refute any technological development if the development team is not transparent.

Therefore, my suggestion to this problem is:
1. Send some amount of Dero to other wallet from the pre-mined wallet. The amount doesn't matter. It can be 1 Dero or 0.01 Dero. (you're welcome to use my address at dERonmJchVsaVD6mMxGPbeFmfwkQpdj8vGtfCxqv1xzrNHtw874QyAeEqUsN3k7sTW2ifpASftUQqKr hsavSwMK98PThnxYbXZ)
2. Re-generate wallet using "Full" spent key which shows at least 1 spent transaction.
3. Screenshot and change ANN page #1

Fact #1: Many of cryptonote anti-ASIC coins are actually immune to 51% attack.
Fact#2: Most of the 51% attack were triggered only after the ASIC is widely available. Most attacks were triggered by ASIC devices.
Fact#3: Customizing CN algo is way easier than modifying ASIC. Therefore it is easy to stay ASIC resistant for CN based coin.