Skip to content
Snippets Groups Projects

Transaction history table improvements

    • Open Issue created by Moul @moul

    First

    Then

    Around
    • Use the authentication methods, to get the pubkey we want to get the history of
    • Allow to check transactions from several pubkeys: merge transactions
    • Add options to display the resulting table output in a “less” (pager) or directly to stdout
    • Paint green incoming txs and red outgoing txs
    • Option to display or to hide the header for faster result (not sure how this will speed up the cmd)
    • Allow to sort rows according to a column as for net cmd
    • Add progression bar when --uids option is passed (will become useless with GVA) The progress bar might still be necessary to process the data.
    Content management
    • !160 (merged): Add --full-pubkey option to display the whole pubkeys
    • Separate columns for the uids and for the pubkeys
    • #394: Allow to display txs between two dates rather than the whole txs list
    • Always display pending txs (and an estimation date when it’s sure they will enter the blockchain)
      • Option to display one of the UTXO, pending or both
    • Options to display only one of absolute or relative amounts, or both
    • Option to display created UD --ud, consummed
    • #391: Display relative amounts using the UD value from a chosed moment or at the time of the tx.
    • Add filter options (remove transaction based on comment matching or issuer)
    • Handle multi-issuer tx display
    • Option to display only sent or only received txs
    • Add an option to display inputs and outputs
    • TBR: --uids request once duplicate between sent and received, would no longer make sense with GVA
    Content handling
    • Handle other outputs’ conditions (XHX, CSV, CLTV)
    1 of 23 checklist items completed · Edited
    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items ...

    • Activity

    Please register or sign in to reply