Use balance_delta in txn list #731
No reviewers
Labels
No labels
accessibility
app-parity
area: creator
area: daemon
area: design
area: devops
area: discovery
area: docs
area: installer
area: internal
area: livestream
area: performance
area: proposal
area: reposts
area: rewards
area: search
area: security
area: subscriptions
area: sync
area: ux
area: viewer
area: wallet
BEAMER
channel
comments
community PR
consider soon
core team
css
dependencies
electron
Epic
feature request
first-timers-only
good first issue
hacktoberfest
help wanted
hub-dependent
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
merge when green
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
notifications
odysee
on hold
playlists
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
recsys
redesign
regression
resilience
sdk dependent
Tom's Wishlist
trending
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-desktop#731
Loading…
Reference in a new issue
No description provided.
Delete branch "txn_list"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@kauffj why was
tx.fee
divided byappend.length
. Did it serve any particular purpose.@kauffj, @tzarebczan This also fixes, the problem where fee only txns still show in the list. Now only relevant transactions are shown
@hackrush - can you give an example of a fee only transaction?
@hackrush01 because this is presenting each individual outpoint as a unique transaction to a user, I think it is less confusing to distribute the fee across all of the outpoints.
Consider a transaction with say, 5 outpoints. If we show the fee on each outpoint without distributing it, a user is decently likely to interpret the transaction fee as 5x as large as it actually was. I think it is better this fee is shown as 1/5 for each outpoint.
Minor changes requested.
This can be combined into one
if
statement rather than 2.This is a very confusing line. Does it have to work this way? I check if I have an
amount
, and if I do, I usebalance_delta
, but if I don't, I usevalue
?If this is correct, perhaps something should be changed in the APIs to make this less confusing/complex.
@tzarebczan A few 'fee only' txns
I'll have to check the tx ids, but do you know where those came from in terms of app actions?
I don't remember even a bit, these are very old transactions, and I don't
remember what I did.
On Sat, Nov 18, 2017 at 3:26 AM, Thomas Zarebczan notifications@github.com
wrote:
--
-Regards
-Amit Tulshyan