Quote from: ashguine on July 22, 2019, 02:07:08 AM

Organize the problem as it is not in focus. Huh

(1) The biggest problem is the mine pool with more than 50% share. As you know, if you have more than 50% share, you can rewrite the chain.
(2) What happened to Tradesatoshi, my Tradesatoshi balance was 0. Tradesatoshi's YTN balance increased while Tradesatoshi was repairing the YTN wallet. And that amount was the same as the YTN I sent from Tradesatoshi to Crex24.
In other words, during maintenance, I could get the same amount of YTN that I sent to the Crex 24 YTN. (YTN disappeared during maintenance but can be retained by converting it to BTC)
(3) YTN is maintained at an unusually high frequency at replacement frequency compared to other coins. In other words, chain rewriting and wallet vulnerabilities may have been attacked.
It is impossible to provide evidence for (2). I get up in Tradesatoshi and roll back my history.
About (1) and (3), it is what is actually happening.

I thought that the hash balance of the pool would be the same as before if I returned the algorithm to YescryptR16 to solve the 50% problem, but I don't think so now.
Please think about the action of the community.
Creation of a GUI miner for recommending other coins (Community claimed that it would lead to an increase in Yenten's ad and pool. Conversely, it increased the dissatisfaction of YTN users.)
We recommend that you open the YescryptR16 pool and move it out of CPU-POOL (no one will ever mine old coins without replacement).
It is up to you to decide if the community is ineffective or capable, but already, Yenten is not at the stage of discussing CPU and GPU mining.
The system itself is not functioning due to limited YTN deposits and withdrawals.

If you discuss Yenten, you should discuss the issues I raised.
Another problem is that it is a non-critical one.

1) We are now solving the 50% problem, we need more new miners to mine in other pools.
I also want to note that the problem is an exaggeration, because cpu-pool is reliable and will not do block replacement.

2) 3) When was the translation? What the transaction id? What are the coins? (hacked v2.x.x?)
We remind once again that the v2.x.x coins were hacked and not supported by the exchanges, so they simply do not exist in the v3 branch.
Why raise an old problem that have solved? It harms the populization of the coin.
The wallet v 3.x.x is stable, not cracked and the coin is actively developing, creating services around itself.