Ferc V3 has been deployed for a week. Overall, it ran well and has been very successful.

But I have found the following issues that may go against the original intention of FERC20:

1. Some deployers set very short freeze time.

   As I mentioned on Twitter when I released V1 at 1st of June, the idea of FERC20 is derived from ordinals. Due to Bitcoin's low scalability, the confirmation speed of ordinals is slow, which ironically helps prevent fast and batch minting. Therefore, the freezing period is designed to simulate this characteristic of a slow blockchain. If the freezing period is set too short, it will inevitably result in a large number of fast and batch minting, making it impossible to achieve fair minting.

   So, in this version, I made some update. When deploying tokens, if a freezing period is set, it must be a minimum of 10 minutes.

   Perhaps this will lower the speed of minting, but it allows more people to participate and prevents it from becoming a game for a few participants.

2. The list display is not reasonable

   Due to FERC20's serverless architecture, the frontend browser directly interacts with the blockchain and smart contracts. As a result, it is not possible to sort or filter the token list, which makes it difficult for many users to find specific tokens. To address this issue, the community is working on a project to improve this.

   However, this work requires some time. So, in this version, I have changed the default display order to prioritize the most recently deployed tokens at the top. While this solution is not optimal, it at least provides more visibility for newly deployed tokens.

   These days, I have been reviewing on the original intentions and purposes of designing FERC20. I realized that in many cases, the more complex a system is, the further it may stray from fairness. FERC20 started with a focus on fairness, but in order to become a comprehensive token issuing tool, it has become quite complex. Therefore, the next step will involve making it simpler at the frontend.

Ferc V3 has been deployed for a week. Overall, it ran well and has been very successful.

But I have found the following issues that may go against the original intention of FERC20:

1. Some deployers set very short freeze time.

   As I mentioned on Twitter when I released V1 at 1st of June, the idea of FERC20 is derived from ordinals. Due to Bitcoin's low scalability, the confirmation speed of ordinals is slow, which ironically helps prevent fast and batch minting. Therefore, the freezing period is designed to simulate this characteristic of a slow blockchain. If the freezing period is set too short, it will inevitably result in a large number of fast and batch minting, making it impossible to achieve fair minting.

   So, in this version, I made some update. When deploying tokens, if a freezing period is set, it must be a minimum of 10 minutes.

   Perhaps this will lower the speed of minting, but it allows more people to participate and prevents it from becoming a game for a few participants.

2. The list display is not reasonable

   Due to FERC20's serverless architecture, the frontend browser directly interacts with the blockchain and smart contracts. As a result, it is not possible to sort or filter the token list, which makes it difficult for many users to find specific tokens. To address this issue, the community is working on a project to improve this.

   However, this work requires some time. So, in this version, I have changed the default display order to prioritize the most recently deployed tokens at the top. While this solution is not optimal, it at least provides more visibility for newly deployed tokens.

   These days, I have been reviewing on the original intentions and purposes of designing FERC20. I realized that in many cases, the more complex a system is, the further it may stray from fairness. FERC20 started with a focus on fairness, but in order to become a comprehensive token issuing tool, it has become quite complex. Therefore, the next step will involve making it simpler at the frontend.