The impact of the CIP 37 (Conflux-Rust V1.1.1) update on Developers

This update is a compatible version update, and the consensus layer of the public chain has not changed.

This upgrade is close to the Chinese holiday, hasty upgrade may not get enough technical support, we suggest you to upgrade with caution. It is recommended that all Conflux ecological products be upgraded to new nodes after February 22. Conflux-rust will use the new address format starting with v1.1.1. The new address format will be used wherever the address is included in the request parameters and return results.

The Conflux foundation recommends that the future Conflux ecosystem gradually phase out the old version of hex40 address format (starting with 0x) and replace it with base32 address format (starting with a network identifier, such as CFX :). ConfluxScan will have conversion between old and new addresses.

The old and new address formats are only converted once, and the original private key and mnemonic can be logged into the Conflux wallet account normally, without any impact on personal assets.

CIP37 For details, see: github.com/Conflux-Cha…

See also: Chinese translation forum. The conflux. Fun/topic / 474 / t…

V1.1.1 Upgrade content

Incompatible change

CIP-37: indicates that the Conflux address format is changed to Base32. RPC interactions with full nodes do not support hexadecimal addresses similar to the Ethereum format.
Store all data (including directories storage_db, blockchain_db, and net_config) in a directory configured with conflux_data_dir (the default directory is blockchain_data).

Compatible WITH RPC changes

Add cfx_getSupplyInfo to return the CFX supply.
Include networkId in the cfx_getStatus response.
Include address in the cfx_getAccount response

To improve the

Support the CIP-37 address format in the mining_author parameter.
Reduce latency in log publish-subscribe, now we publish logs as soon as they become available.
Implementation of execution tracking features, including detailed call/create/return/internal transfer events triggered by the transfer, checking for trace information allows applications such as ConfluxScan to track accurate traces of CFX transfers.
Optimized the testing framework and solved some random test failures.

I am a Conflux eco-developer, what do I need to do?

Conflux will officially complete the upgrade tutorial and SDK versions by January 31, but it is recommended that all mines, exchanges, wallets and DApps do not update the new node (RPC) before February 22. Users using official RPCS will be able to stay put while a new version is released and the old RPCS will remain in place until at least the end of March.

After updating the node (RPC), it needs to update and use a new SDK. After that, without additional adaptation, it can only interact with the base32 address (starting with a network identifier, such as CFX :). Please remind users of wallets, exchanges and smart contracts.

Impact on front-end pages

Portal

When Portal is updated to version 0.5.10, the API returns the old HEX40 format address (starting with 0X), the signature only supports the old HEX40 format address (starting with 0X), and there is a prompt when the transfer is transferred to the old HEX40 format address (starting with 0X).
When Portal was updated to version 0.5.11, the API returned only base32 addresses, and the signature supported both the old hex40 address format (starting with 0x) and base32 address format (starting with a network identifier, such as CFX :).
The DApp needs to consider the possibility that users may not upgrade to a new version of Portal, and the API returns both old and new addresses.

How does Conflux Javascript SDK fit with CIP37

Chinese version: juejin.cn/post/692014…

Impact on back-end servers

How does the SDK fit into the reference

How does Conflux Java SDK work with CIP37

Chinese version: juejin.cn/post/692269…

How does Conflux Golang SDK fit CIP37

Checking in progress

Node Document Configuration

Directory changes:

All data is now stored in the conflux_data_dir directory./blockchain_data by default.

Previous default directory structure:

├ ─ ─ blockchain_db ├ ─ ─ net_config ├ ─ ─ storage_db ├ ─ ─ conflux ├ ─ ─ the log ├ ─ ─ the yaml ├ ─ ─ start. The bat ├ ─ ─ start. Sh ├ ─ ─ Stderr. TXT ├ ─ ─ tethys. TomlCopy the code

The current default directory structure

├ ─ ─ blockchain_data │ ├ ─ ─ blockchain_db │ ├ ─ ─ net_config │ └ ─ ─ storage_db ├ ─ ─ conflux ├ ─ ─ the log ├ ─ ─ the yaml ├ ─ ─ start. The bat Bass Exercises ── start. Sh Bass Exercises ── Bass ExercisesCopy the code

Adaptation Method 1 (recommended) :

Create the blockchain_data directory and move the blockchain_db, net_config, and storage_db directories to blockchain_data. Do not modify the configuration file tethys.toml.

Adaptation method 2:

Do not move the directory, set it in the configuration file tethys.toml

conflux_data_dir = "."
netconf_dir = "./net_config"
block_db_dir = "./blockchain_db"
Copy the code

SDK upgrade description document