This repository has been archived by the owner on Jul 27, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 66
Problem: confusing and incorrect history display #846
Comments
bors bot
added a commit
that referenced
this issue
Jan 8, 2020
848: Problem: Client CLI does not show transaction type in history r=tomtau a=devashishdxt Solution: Show transaction type in history. This addresses a part of #846 Sample output after this change: ``` +------------------------------------------------------------------+--------+----------------------+-----+------------------+--------------+--------------------------------+ | Transaction ID | In/Out | Amount | Fee | Transaction Type | Block Height | Block Time | +------------------------------------------------------------------+--------+----------------------+-----+------------------+--------------+--------------------------------+ | cc88d0ca2cbcd6ce167a6db426f40c3da034deb5b4e4f09e5ec01f39af80c0ea | IN | 24999999999.99999703 | - | Withdraw | 92 | 2020-01-07T10:14:17.764748000Z | +------------------------------------------------------------------+--------+----------------------+-----+------------------+--------------+--------------------------------+ ``` Co-authored-by: Devashish Dixit <devashish@crypto.com>
fee can be taken from block_results, as there's an event with the actual fee paid: https://github.com/crypto-com/chain/blob/master/chain-abci/src/app/mod.rs#L357 |
This was referenced Jan 20, 2020
one other related issue to display: #929 |
I put the transaction details in a separate issue: #968 |
tomtau
added a commit
to tomtau/chain
that referenced
this issue
Jan 30, 2020
Solution: - removed the "balance change" output custom fee calculation / deduction - added paid fee to the balance change that's directly taken from events / attributes Note: transaction details was moved to a separate issue: crypto-com#968
tomtau
added a commit
to tomtau/chain
that referenced
this issue
Jan 30, 2020
Solution: - removed the "balance change" output custom fee calculation / deduction - added paid fee to the balance change that's directly taken from events / attributes Note: transaction details was moved to a separate issue: crypto-com#968
bors bot
added a commit
that referenced
this issue
Jan 30, 2020
969: Problem: incorrect fee display in history (#846) r=tomtau a=tomtau Solution: - removed the "balance change" output custom fee calculation / deduction - added paid fee to the balance change that's directly taken from events / attributes Note: transaction details was moved to a separate issue: #968 Co-authored-by: Tomas Tauber <2410580+tomtau@users.noreply.github.com>
bors bot
added a commit
that referenced
this issue
Jan 30, 2020
969: Problem: incorrect fee display in history (#846) r=tomtau a=tomtau Solution: - removed the "balance change" output custom fee calculation / deduction - added paid fee to the balance change that's directly taken from events / attributes Note: transaction details was moved to a separate issue: #968 Co-authored-by: Tomas Tauber <2410580+tomtau@users.noreply.github.com>
bors bot
added a commit
that referenced
this issue
Jan 30, 2020
969: Problem: incorrect fee display in history (#846) r=tomtau a=tomtau Solution: - removed the "balance change" output custom fee calculation / deduction - added paid fee to the balance change that's directly taken from events / attributes Note: transaction details was moved to a separate issue: #968 Co-authored-by: Tomas Tauber <2410580+tomtau@users.noreply.github.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
in client-cli (perhaps similar issue is in client-rpc), deposit tx will be shown as "out", amount: "0.00000000", fee: "the amount deposited".
If one does a transfer of any amount within the same wallet, the display is logical, as it'll show as "out", amount: "0.00000000", fee: "real fee".
It'll be useful to display transaction types + have some command for a detailed transaction view; or any other ideas?
The text was updated successfully, but these errors were encountered: