Non-Native token transfer in history add more details about CKB

[Danie0918]

Current problems：

Nervos dao deposits, which show the fee, or sudt/nft transfers, which show the sudt amount/nft label, without the unique ckb and fee.

NervoDAO lacks a message when depositing or withdrawing, which causes confusion for the user when the balance changes.

[Danie0918]

【Non-Native token transfer in history add more details about CKB】

• Requirement Description: Optimize the content of the history page to show more transaction details.

• 【History Page】Requirement Contents

1. [Amount]: Show the number of transaction types, including positive and negative.
2. [Balance Change]: Show the changes that occurred to the CKB balance for this transaction.
3. 'Type' 'Balance Change' 'Time' add sorting function.
4. When the transaction is not confirmed, the number of confirmations is displayed as ' - '.
5. Add the transaction fee field to the drop-down list to show ' - ' when the value is empty.
6. When withdrawals of type Nervos DAO are made, instead of showing transaction fees, compensation is shown.

• 【History Detail Page】Requirement Contents

1. Added topology graph. (Refer to Send page)
2. Adjust 'Block Number' 'Date' 'Income' to 'Block Height' 'Time' 'Balance Change'.
3. Add 'Type', 'Amount',' Transaction Fee', 'Status', 'Size', and 'Cycles' fields.
4. Add the ‘Cell Info’ field (refer to Cell Management, Synchronize the modification of 'Cell Details' to 'Cell Info')

[yanguoyu]

[Amount]: Show the number of transaction types, including positive and negative.

When the transaction is sent CKB to the current wallet, is the amount equal to balance change?

Add 'Type', 'Amount',' Transaction Fee', 'Status', 'Size', and 'Cycles' fields.

Just a tip: For the Cycles fields, it isn't saved into the local DB in the previous. We should add Cycles for the old transactions.

[Danie0918]

[Amount]: Show the number of transaction types, including positive and negative.

When the transaction is sent CKB to the current wallet, is the amount equal to balance change?

Yes.

Add 'Type', 'Amount',' Transaction Fee', 'Status', 'Size', and 'Cycles' fields.

Just a tip: For the Cycles fields, it isn't saved into the local DB in the previous. We should add Cycles for the old transactions.

We need to add Cycles for old transactions to ensure data uniformity.

[Kirl70]

Design Draft (5-4--5-9):

https://www.figma.com/file/6XNoimRDbFTTNm016rbIdU/Magickbase?type=design&node-id=32218%3A57456&mode=design&t=KnCUMYYLePbTRJQt-1

[yanguoyu]

nervosnetwork/neuron#3040

[homura]

IMO, the decoder here is too developer-specific for an end-user wallet. Additionally, developers may also find it confusing because the encoding of data is not restricted in any way. It is very hard to

• find what range of characters should be selected
• determine what encoding rule should be used.
• choose a correct number and address decoding rule because both of them have more than one encoding rules

I suggest that we either move this feature to another product or revise it to make it more user-friendly and intuitive.

[Danie0918]

IMO, the decoder here is too developer-specific for an end-user wallet. Additionally, developers may also find it confusing because the encoding of `data` is not restricted in any way. It is very hard to

• find what range of characters should be selected
• determine what encoding rule should be used.
• choose a correct number and address decoding rule because both of them have more than one encoding rules

I suggest that we either move this feature to another product or revise it to make it more user-friendly and intuitive.

The UI here references the CKB Explorer's design, and during development, it was found that it could not be better supported and was not necessary for the user, so we eliminated the feature.

[yanguoyu]

IMO, the decoder here is too developer-specific for an end-user wallet. Additionally, developers may also find it confusing because the encoding of `data` is not restricted in any way. It is very hard to

• find what range of characters should be selected
• determine what encoding rule should be used.
• choose a correct number and address decoding rule because both of them have more than one encoding rules

I suggest that we either move this feature to another product or revise it to make it more user-friendly and intuitive.

The UI here references the CKB Explorer's design, and during development, it was found that it could not be better supported and was not necessary for the user, so we eliminated the feature.

Understood, I will remove the parsing of the data.

[Danie0918]

[Amount]: Show the number of transaction types, including positive and negative.

When the transaction is sent CKB to the current wallet, is the amount equal to balance change?

Yes.

Add 'Type', 'Amount',' Transaction Fee', 'Status', 'Size', and 'Cycles' fields.

Just a tip: For the Cycles fields, it isn't saved into the local DB in the previous. We should add Cycles for the old transactions.

We need to add Cycles for old transactions to ensure data uniformity.

My mistake, I realized during testing that this time a misunderstanding arose. The actual requirements are as follows:

1. Replace 'Amount' with 'Asset'.
2. 'Asset' data format: Show the amount of assets sent/received or locked/unlocked without fees.
   • For transactions sent to yourself, 'Asset' needs to be shown as '--'.
   • NervosDAO will show + - the amount indicating the amount of CKB‘s unlock and lock, and '--' for withdrawals.

@yanguoyu @silySuper

[yanguoyu]

nervosnetwork/neuron#3151