I saw this tweet about the issue of "choice". For a small team, they are constantly faced with choices because their resources are limited. What you need to focus on at a certain moment determines your fate, so I have some thoughts. From January to March, because of the popularity of Trump coins, a large number of new people began to enter the chain and chose to use GMGN. Then some problems arose, the TG number was blocked and stolen. There is a fraudulent GMGN app on the Apple Store, and we have posted a banner warning on the webpage to file a complaint with Apple. Users may export their private keys themselves and then upload them to a cloud, click on a phishing link, or import them into a fraudulent app. Security issues are becoming increasingly severe. The first multiple-choice question: Is that for security or to continue with functionality? We chose security and the team fully invested in restructuring a series of security measures, including the account system. Try to conform to the usage habits of novice users as much as possible. This set took over a month. Sacrificed a bit of experience, such as the inability to export private keys. Reduced some entry barriers and improved security verification, for example, GMGN now has multiple login methods, including plugin wallet, TG login, Phantom wallet signature login, APP scan code login, email login, biometric login (coming soon). There are also various security measures, such as whitelisting withdrawals, adding whitelist TG push alerts, email push alerts, Google two-step validator, and biometric verification afterwards. Are there any other solutions for these things? No, Safety is like underwear, how can it be entrusted to others for protection? Is it worth it? After completion, reduce 5-6 user security questions per day to occasional or zero reports per day. Second Multiple Choice Question: While ensuring security, based on the team's internal assessment of 'roll up power', there is one more thing that can be done, which is to support BSC or continue optimizing SOL? We have chosen to support BSC. Because at that time, we also predicted the upcoming hot market of BSC, and users would have enthusiasm to use it. With clear demand placed here, will it become the second growth curve? After completing BSC, GMGN did indeed ride a wave of wind. At that time, many overseas users also used GMGN to trade BSC because competitors did not have it. But what I didn't expect was that the duration was not as long as expected. But there are still many issues that need to be optimized for the product, and there is user feedback every day, which needs to be improved every day. We need to continue investing our energy. Third Multiple Choice Question: Competitors have well met the demand for chain scanning, will GMGN keep up? While addressing security and BSC support, the SOL experience itself has not kept up with the trend. The performance issues of GMGN have also encountered bottlenecks. Some choices made in the early stages of entrepreneurship have caused these problems. Should we make synchronous changes? Can we change them? Follow, the product needs a big move. Don't follow, lie down and eat old books. If the user curses a few words of lack of pride, they won't curse anymore. Major changes, if users don't buy it, will they kill themselves? For example, losing the original flavor of GMGN and losing other areas of user flow? This multiple-choice question looks difficult. But it's not difficult either. If you want to do GMGN well, the answer to the choice is obvious. At that time, many people tweeted about various issues with GMGN, and there were also those who directly cursed without mentioning any problems. I have basically watched everything. I've been cursing on Twitter for almost half a month now. The scolding was well founded and made me blush. I watched it two or three times and also showed it to my team members. Some of them were particularly good at scolding, and I even contacted them, called them, and listened to their opinions. What shall I do? Shut up and reflect, admit your shortcomings, learn, improve, and practice quickly. I haven't tweeted much for a while. I can't post it, if I post it, I'll be scolded. I can't watch it either. At the beginning of the update, everyone didn't know what you were doing. As soon as it was updated, there was a lot of criticism in the group and on Twitter, and we couldn't explain it because we didn't know what we could do. Just doing it under pressure. The team worked together to figure out each problem, and if they couldn't figure it out, I went to fight the dog. Operate on GMGN to reproduce some issues. Then let the R&D team make corrections for each problem. Simultaneously undertake a major restructuring of the architecture. SOL's webpage speed, transaction speed, Windows performance optimization, and various small features and details are constantly improving. According to GMGN's 30 day statistics, my account has made 2000 transactions, played 500 dogs, and lost money again, but the problem has been solved. The past two months have been very fulfilling for us, and our mood is like a jumping machine. I did something that users didn't buy into, flattered them on the horse's lap, and felt anxious. Having done something and receiving likes and flattery from users makes me feel more comfortable. The fourth multiple-choice question: What's the next step, how to choose? The revolution has not yet succeeded, comrades still need to work hard. There are still many areas waiting to be optimized. Continue rolling, roll out a path.