Currently, when using the “track a specific address” related function, I found that there is an experienced pain point. I want to optimize suggestions simultaneously, hoping to better meet the individual needs of high-asset users:

The current function may operate by default according to the “automatic matching after excluding less liquid currencies” logic, but in actual use, some high-asset users (such as users with multiple currencies) are unable to operate all automatically matched currencies one by one due to their large asset size; more importantly, there is a clear requirement to “specify an address to track, but only want to synchronize a specific currency under that address” — for example, when tracking an “Ma Ji” related address, they only need to synchronize their ETH coin dynamics, not other currencies under that address.

It is now recommended to optimize this function. The core direction is to open the “user's own choice of bound currency” permission. For details, please refer to the following optimization points:

Retain the original default option of “automatic matching after excluding small liquidity currencies” to meet basic user needs;

A new “Custom Currency Selection” portal has been added. When users track a specific address, they can manually check the existing currencies (such as ETH, BTC, etc.) under that address, and only synchronize the ticking currency movements;

If you are concerned that small liquidity coins will affect the experience, you can mark “low liquidity tips” for less liquid coins in the custom selection interface, and let the user decide whether to choose instead of directly blocking them.

This optimization can not only solve the operational burden of “not being able to fully open all automatically matched currencies” for high-asset users, but also accurately meet the personalized tracking requirements of “designated address+designated currency”, further improving the flexibility and practicality of the function

When using the “track specific address” related functions, we have identified an experience pain point and would like to share optimization optimized to better meet the difficult needs of high-net-worth users:

Currently, the function may operate by default based on the logic of “comparable matching currencies after excluding those with low liquidity”. However, in actual use, some high-net-worth users (e.g., users holding multiple currencies) cannot operate on all qualified currencies one by one due to their large asset scale. More opinions, there is a clear demand for “considering to track a certain address but only considering to sync the dynamics of specific currencies under that address” — for example, when Tracking related addresses to “Machi Big Brother”, users only need to sync the dynamics of its ETH currency, not other currencies under that address.

We now suggest considering this function, with the core direction being to open up the permission for “users to decide select bound currencies”. Specific optimization points can be considered to be considered:

Retain the original default option of “marginal matching after excluding currencies with low liquidity” to meet the needs of basic users;

Add a “custom currency selection” entry. when users track a specific address, they can manually check the existing currencies under that address (such as ETH, BTC, etc.) and only sync the dynamics of the checked currencies;

If there are amounts that currencies with low liquidity may be considered the experience, a “low liquidity reminder” can be marked for such currencies in the custom selection interface, introduced users to decide whether to select them instead of blocked them.

This optimization can't only solve the operational burden of high-net-worth users who “cannot enable all assessed currencies” but also satisfies the vulnerable Tracking needs of “specific address + specific currency”, further improving the flexibility and practicality of the function.