1. If SAFE is on the BSC, ETH, or MATIC chains, there is no need to migrate; if it is on the SAFE3 blockchain, migration is needed.

For those using the SAFE3 mobile wallet, please wait for a while; after that, the new version of SafeWallet will support the import and migration of mnemonic phrases from the SAFE3 mobile wallet, allowing for smooth migration.

2. Before migration, first claim the transaction fees for free; both SafeWallet and SAFE4 PC Desktop have a place to claim 0.0001 SAFE for free, which is sufficient for transaction fees. After claiming, wait 1 minute for confirmation and then you can migrate.

However, if you have more than 100 addresses, the transaction fee for migration is likely insufficient, so you need to transfer a bit more SAFE in; 1 SAFE is sufficient to handle all migrations.

3. Recently, everyone has been migrating together, resulting in a massive amount of data; the SAFE4 network and interface are overwhelmed, causing some transaction sending errors, possibly due to insufficient transaction fees.

Secondly, it may be that the interface server is too busy (even a 32-core 64G server can't handle it), and we are already expanding and balancing the load.

If everyone migrates during the late night, it may go much smoother.

4. If there are missing assets after migration, it may be due to locked records of less than 0.03, which can be compensated; please wait for notification.

Secondly, it may be that the SAFE3 or SafeWallet wallet has not synced properly, leading to discrepancies in amounts, but they are actually correct; the SafeWallet wallet might also incorrectly calculate the balance.

Addresses that originally had no coins will also show having coins; in this case, verify whether the amounts listed on the migration interface are correct on the SAFE3 block explorer to determine if there was a miscalculation.

Thirdly, it’s possible that a part of the addresses was missed during calculation; if this is the case, please wait; the development team is investigating the issue, and after resolving it, just migrate again to make up for the missing addresses.

5. For the SAFE4 desktop version, you can migrate without updating the blockchain to the latest block; however, SafeWallet must wait for SAFE3 to update to the latest block before migration.

Currently, there are very few SAFE3 blockchain nodes, leading to poor synchronization; the development team is increasing SAFE3 nodes to facilitate synchronization for migration.

6. Supernodes marked with 'official supernode' are official supernodes, solely for guiding the normal operation of the SAFE4 network.

Next, the SAFE4 network is normal; the official team will only retain 2 supernodes for testing and monitoring the SAFE4 network.

Therefore, please do not vote for these supernodes to avoid affecting everyone's voting rewards later.

7. Cross-chain has not been officially opened yet; it can be used now, but there may be delays in receiving funds, so please be patient.

8. Please ensure that the main nodes and supernodes of SAFE4 are equipped according to the recommended configuration.

Operating system requirements: Ubuntu 14 and above, recommended 20.

Recommended configuration for main nodes: 4 cores, 8G, 3-5Mbp bandwidth.

Recommended configuration for supernodes: 8 cores, 16G, 10Mbp bandwidth.

Below this configuration, it can run for a short time, but over time, as the number of connections increases, memory consumption will increase.

Until the operating system automatically kills the SAFE4 node program due to insufficient memory.

The connection between supernodes and main nodes and the outside world will be cut off, preventing block production, displaying 'abnormal', and affecting rewards.

If the bandwidth is too low, it will also affect communication efficiency with other nodes, displaying 'abnormal', and impacting rewards.

The TCP and UDP of the VPS server need to have port 30303 open.

Increase the number of connections for the VPS server to: main node 1024, supernode 4096.

9. The SafeWallet iOS version previously had a signature drop; it has been re-signed on the afternoon of May 14, so please try downloading and using it.

10. For the SAFE4 white paper and the user manual for the SAFE4 Desktop version, please visit the official website for download.