Support auto-claiming of Publish+Channel rewards #2209

Closed
opened 2019-01-18 20:10:48 +01:00 by tzarebczan · 1 comment
tzarebczan commented 2019-01-18 20:10:48 +01:00 (Migrated from github.com)

The Issue

Now that we have chainquery validating publishes via the mempool, we should be able to streamline/automate the claim process for first publish/channel. After a publish/channel, continue calling the api to claim (silently) it for X amount of time until it succeeds. If it doesn't, a popup alerting the user that something may have gone wrong/claim later would be a nice touch.

Suggested Solutions

Tell us your suggested solutions if you have any.

System Configuration

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

Anything Else

Screenshots

Internal Use

Acceptance Criteria

Definition of Done

  • Tested against acceptance criteria
  • Tested against the assumptions of the user story
  • The project builds without errors
  • Unit tests are written and passing
  • Tests on devices/browsers listed in the issue have passed
  • QA performed & issues resolved
  • Refactoring completed
  • Any configuration or build changes documented
  • Documentation updated
  • Peer Code Review performed
<!-- 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-desktop/releases - Standalone daemon: https://github.com/lbryio/lbry/releases We are also available on live chat at https://chat.lbry.io --> ## The Issue Now that we have chainquery validating publishes via the mempool, we should be able to streamline/automate the claim process for first publish/channel. After a publish/channel, continue calling the api to claim (silently) it for X amount of time until it succeeds. If it doesn't, a popup alerting the user that something may have gone wrong/claim later would be a nice touch. ### Suggested Solutions Tell us your suggested solutions if you have any. ## 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: - LBRY App version: - LBRY Installation ID: - Operating system: ## 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 --> ## Internal Use ### Acceptance Criteria 1. 2. 3. ### Definition of Done - [ ] Tested against acceptance criteria - [ ] Tested against the assumptions of the user story - [ ] The project builds without errors - [ ] Unit tests are written and passing - [ ] Tests on devices/browsers listed in the issue have passed - [ ] QA performed & issues resolved - [ ] Refactoring completed - [ ] Any configuration or build changes documented - [ ] Documentation updated - [ ] Peer Code Review performed
tzarebczan commented 2019-11-02 18:06:21 +01:00 (Migrated from github.com)

We decided we want users to do these manually.

We decided we want users to do these manually.
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#2209
No description provided.