Release Notes on Token Swap Service and ArcBlock Asset Chain

The ArcBlock Token Swap and Asset Chain release is being released using a method called “grayscale release” and is similar to BlueGreenDeployment. This method has been widely adopted in Internet services, but in the past, the blockchain field has rarely heard, or used, the release practice. We believe that companies like Baidu, who are mature advanced technology companies, can be learned from and used in a new generation of blockchain services.

So what is Greyscale release?

Here’s the explanation on Baidu Encyclopedia:

Grayscale release (also known as canary release) is a way of publishing which uses A/B testing, that is, let some users continue to use product feature A, while some users began to use product feature B, if the user has no objection to B, then the scope is gradually expanded and all users are moved to B above. Grayscale release can ensure the stability of the overall system, and minimizes the impact of upcoming changes to the overall service.

Grayscale: This period of grayscale release from the beginning to the end of the period, called the grayscale period.

Simply put, we are releasing a full-featured product and service, not a beta version, but in this product and service is released in stages to test and optimize the actual environment.

There are different strategies to choose which users will see the new version: a simple strategy is to use a random sample; some companies choose to release the new version to their internal users and employees before releasing to the world; another more sophisticated approach is to choose users based on their profile and other demographics. Our goal, either way, is to build an amazing service where we are continually testing and adding new features into production that improve the user experience.

Why should asset chains and swap services be grayed out?

One primary purpose: security.

Security represents two sides of the same coin here — on one hand we want to ensure the security of user assets, and on the other, we want to ensure the security of the asset chain itself.

The ABT asset chain is based on the already mature ArcBlock blockchain framework, which has already been in production for more than one year and has proven to be resilient, secure and very reliable. However we still need more practical verification, that is, really more testing on the asset chain (including simulated attacks, Inviting white-hat hackers to attack, simulating real-life tests such as network and system catastrophic events), we don’t want to wait until we find a problem to solve it, but rather try to find out what’s possible on our own.

During the grayscale period, we will be limiting the daily amount of token swaps and recommend that users initially use small swap requests. If you change in a large number of native ABT and return, you will be limited by the daily limit.

What’s the difference between Native ABT and ERC20 ABT?

You could argue that the ABT asset chain and Ethereum are connected by a bridge through the token swap service (Token Swap). The Token Swap Service is a bidirectional token swap service ensuring that the ABT token can exist at either end and circulate freely in both directions through the swap service.

As many of you already know, Ethereum has severe performance issues making ERC20-based tokens not very practical use in applications and services. However, Ethereum is now the de facto standard especially for Decentralized Finance (DeFi), and a variety of services can be easily connected with Ethereum. ArcBlock is application-focused, and developers can develop high-performance applications on ArcBlock and by bridging the swap service, ABT users can benefit from the increased utility by being able to access both networks ensuring interoperability between the two.

The role of Native ABT token is the application, and giving developers increased capabilities to build blockchain-enabled applications and experiences at scale.

What are the limitations and tests during the grayscale release?

Limitations during grayscale release:

• The number of swaps will be limited
• The waiting time may be slightly longer (generally no more than 24 hours)
• Occasional service suspensions, which may temporarily stop services and upgrades when we find risk issues. However, there is no risk or loss of tokens when that occurs.

Test:

• We do a series of security tests, including chain maintenance and upgrades in more extreme cases
• Some chain protocol upgrades, forks, security recovery, etc. testing
• User assets are secure during testing, but the experience and performance may be affected occasionally

Asset chain nodes:

• All nodes run by ArcBlock and partners in the initial release
• Gradually invite partners or users to join the asset chain node
• End sit free to join or exit nodes

Note that the ABT asset chain does not have mining block rewards, mortgage incentives, but using ArcBlock to develop and operate applications can get ABT rewards, to obtain these rewards or use some ArcBlock services (such as Atomic Swap, etc.), you must run the asset chain nodes. This is the basis of ABT asset chain decentralization and the reason sturdy.

When will the grayscale end?

Because software development is a gradual process, we will continue to upgrade our asset chain and swap services in the future, so we may be able to use grayscale releases for new features for a long time. Therefore, the grayscale period will remain for a long time, but the user may not feel the “grayscale” when the basic functions are complete.