It’s now easy to add Achain’s new network through wallets such as Metamask. Users can follow the step-by-step instructions given below to add the new network successfully. Once the network is added, users can view the new ACT tokens they have exchanged in their wallets.

1. Click the MetaMask network switch button and select Add Network at the bottom.

2. Fill in the relevant parameters for Achain’s new master network and click the Save button.

Step 1: Open your Achain wallet

Step 2: Send your entire ACT tokens to the official Achain wallet address by setting up the following:

Type: ACT
Address: ACTP3C6v7Mp6b82TecY8UhjHna2r3A8DSYc7
Amount: <Enter your entire ACT token balance>
Note (Optional): <Enter your Ethereum receiving address after the first 2 letters “0x” prefix>

ℹ️The address format of the new chain ACT is the Ethereum address. Due to the character limit of the notes on the chain, please remove the first 2 letters “0x” prefix when you fill in the Ethereum format address.

Step 3: After you send your ACT tokens, kindly send an email to hi@achain.com. Once we receive an email and verify your TX, we’ll complete the ACT token swapping process.

1. Research EIP-4200, encode the destination as a signed immediate value. These can be useful in the majority of (but not all) use cases and offer a cost reduction.
2. Improve mainnet accounts, simplify Arguments. Unpack.
3. Upgrade rpc apis and remove unnecessary comment.
4. Improve trx broadcast and test for edgecase in VerifyRangeProof.
5. Upgrade transaction calldata, evict old payloads, type PayloadID.
6. Add new transaction type and support chainId for GnosisSafeTx.
7. Core/rawdb: enforce readonly in freezer instantiation.
8. Trie: use keyvalue reader for non-mutating methods.
9. Improve network and fix serverHandler crash after setHead.
10. Graphql: fix block resolving for parent field.

1. Add the documentation of the use of cli.
2. Add Ram purchase documentation and cli can not connect to node problem documentation.
3. Replace the exceptions thrown by assert to the stack and stack operations.
4. Organize and add error codes, so that the log for the error record more detailed, easy to analyze and locate the problem.
5. Investigate Achain’s native DPOS consensus model, consider taking the optimized PBFT algorithm to ensure consistency.
6. Study whether it is possible to temporarily generate a pair of public and private keys for each peer for message interaction to ensure the security and isolation of messages.
7. Study how to minimize the redundancy of network messages during transaction or block broadcast, and improve the effective communication efficiency of messages.
8. Considering the preference of different nodes for encryption protocols, the encryption algorithm required for message encryption can be negotiated during peer handshake.

1. When handling on_incoming_block push_block, pass exception handling so that the caller net_plugin knows that the block is not applied

2. Update sync_next_expected_num by checking sync_last_requested_num instead of checking sync_state, because sync_state may be temporary in the comparison state

3. No need to retry the connection for benign_other disconnection, because there is no block message

4. Add zlibmacro add_eosio_test_executable target link library to support zlib

5. Serialization interface supports array, optional and other types

6. Update fc submodule to support blob_type type to support serialization function

7. Increased sleep time to address slower block propagation through the network

8. Initializing the scaffold framework for data types and parallel test traces

9. Complete the design of the full node side of the Blum filter

In 2020, Achain Galaxy has made significant progress, with Aurora, Eminer, and Linkeye joining the Achain Galaxy. We will continue to preserve the three-stage existing roadmap:

1. Singularity (single blockchain network)
2. Galaxy (multi-blockchain network)
3. Cosmos (cross-chain network)

At the same time, we will launch Achain Hub and Achain Gateway.

The public chains based on Achain standard will access the Achain Cosmos through Hub and interact seamlessly with other public chains in the Cosmos.

Public chains based on non-Achain standards will be counted into the Achain Cosmos through the Gateway and interact seamlessly with other public chains in the Cosmos.