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

Determine and communicate minimum Publish deposit #628

Closed
tzarebczan opened this issue Sep 27, 2017 · 1 comment
Closed

Determine and communicate minimum Publish deposit #628

tzarebczan opened this issue Sep 27, 2017 · 1 comment
Labels

Comments

@tzarebczan
Copy link
Contributor

The Issue

This issue stems from #604 / lbryio/lbry-sdk#920. A new form component was recently added which doesn't allow a bid less than 0.01 (0.16 release) and 0.1 (master).

When you click publish, you don't get any feedback besides highlighting of the bid field (not easy to see sometimes). When you mouse over the LBC value for the bid, you see a tooltip that says - "Please enter a valid value...two nearest values are 0 and 0.01"

Steps here would be to:

  1. Determine what the minimum LBC bid for publishing should be and clearly communicate that to users. This discussion is relevant for the minimum: Allow abandoning of publishes even if it loses LBC lbry-sdk#768
  2. App needs to notify users when their bid is invalid according to the minimum
  3. Mention publishing fees on Publish page

Steps to reproduce

  1. Go to publish page
  2. publish something but put deposit as .001
  3. pressing publish just highlights the div but no error

Expected behaviour

App should alert user that something is wrong with the bid

Actual behaviour

App just highlights the bid field

System Configuration

  • LBRY Daemon version: 0.16.1
  • LBRY App version: 0.16.0
  • LBRY Installation ID:
  • Operating system: Windows

Anything Else

Screenshots

@kauffj
Copy link
Member

kauffj commented Oct 3, 2017

This is fixed. It still doesn't give the minimum as required by transaction fees, but this is variable and can't be known unless lbry adds an API call to provide it.

@kauffj kauffj closed this as completed Oct 3, 2017
Ruk33 pushed a commit that referenced this issue Feb 25, 2022
I'm leaving the generic "Unexpected JSON" error alone for now, as I think this should be fixed at Nick's end.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants