Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transaction List - Claim update amounts incorrect #947

Closed
tzarebczan opened this issue Oct 11, 2017 · 1 comment
Closed

Transaction List - Claim update amounts incorrect #947

tzarebczan opened this issue Oct 11, 2017 · 1 comment
Assignees
Labels
type: bug Existing functionality is wrong or broken

Comments

@tzarebczan
Copy link
Contributor

tzarebczan commented Oct 11, 2017

@tzarebczan commented on Sun Sep 24 2017

The Issue

Currently, an update claim transaction shows the bid amount as the amount of the transaction. Since an update tx takes the previous bid input, funds are moved from the previous claim to the new one, so they aren't really spent during a transaction where the bid is not changed. In this case, it would show 0 and only a fee.

There are also 2 other scenarios to take into account and calculate the transaction amount based on the original bid - a lower bid and higher bid. For a lower bid, you'd have a net positive amount on the update. For a higher bid, you would have a net negative amount.

per @hackrush01, this would be a daemon side fix.

Expected behaviour

Update tx amount should show net positive or negative bid amount

Actual behaviour

Update tx amount shows the bid amount

System Configuration

  • LBRY Daemon version:
  • LBRY App version:
  • LBRY Installation ID:
  • Operating system:

Anything Else

Screenshots

@tzarebczan
Copy link
Contributor Author

tzarebczan commented Nov 7, 2017

Sounds like an app side change still needed based on the way it was implemented on the daemon, re opening on app side.

@hackrush01 is aware

@tzarebczan tzarebczan reopened this Nov 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Existing functionality is wrong or broken
Projects
None yet
Development

No branches or pull requests

3 participants