Determine and communicate minimum Publish deposit #628

Closed
opened 2017-09-27 18:39:59 +02:00 by tzarebczan · 1 comment
tzarebczan commented 2017-09-27 18:39:59 +02:00 (Migrated from github.com)

The Issue

This issue stems from https://github.com/lbryio/lbry-app/issues/604 / https://github.com/lbryio/lbry/issues/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: https://github.com/lbryio/lbry/issues/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

<!-- Thanks for reporting an issue to LBRY and helping us improve! To make it possible for us to help you, please fill out below information carefully. Before reporting any issues, please make sure that you're using the latest version. - App releases: https://github.com/lbryio/lbry-app/releases - Standalone daemon: https://github.com/lbryio/lbry/releases We are also available on Slack at https://slack.lbry.io --> ## The Issue This issue stems from https://github.com/lbryio/lbry-app/issues/604 / https://github.com/lbryio/lbry/issues/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: https://github.com/lbryio/lbry/issues/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 <!-- For the app, this info is in the About section at the bottom of the Help page. You can include a screenshot instead of typing it out --> <!-- For the daemon, run: curl 'http://localhost:5279' --data '{"method":"version"}' and include the full output --> - LBRY Daemon version: 0.16.1 - LBRY App version: 0.16.0 - LBRY Installation ID: - Operating system: Windows ## Anything Else <!-- Include anything else that does not fit into the above sections --> ## Screenshots <!-- If a screenshot would help explain the bug, please include one or two here -->
kauffj commented 2017-10-03 14:40:17 +02:00 (Migrated from github.com)

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.

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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-desktop#628
No description provided.