Skip to content
This repository has been archived by the owner on Sep 1, 2021. It is now read-only.

claim names should be limited to avoid high fees #496

Open
bones7242 opened this issue Jun 28, 2018 · 1 comment
Open

claim names should be limited to avoid high fees #496

bones7242 opened this issue Jun 28, 2018 · 1 comment
Labels
level: 2 Some knowledge of the existing code is recommended needs: exploration Solution unclear, needs research priority: medium Work needs to be done within 2-3 sprints type: improvement Existing (or partially existing) functionality needs to be changed

Comments

@bones7242
Copy link
Contributor

We should limit the length of claim names because the fee gets larger with bigger names

@bones7242 bones7242 added type: improvement Existing (or partially existing) functionality needs to be changed level: 2 Some knowledge of the existing code is recommended and removed needs: triage labels Jul 3, 2018
@alyssaoc alyssaoc added needs: exploration Solution unclear, needs research priority: low Work should be done but can stay in the backlog for now labels Dec 18, 2018
@tzarebczan tzarebczan added the consider soon Discuss this issue at the next planning meeting, then remove this label label Dec 22, 2018
@tzarebczan
Copy link
Contributor

This one was recently published, fee of 0.2 LBC:
https://explorer.lbry.io/tx/d1a01118af556a3204d7a67868c87aa6023bbbcd6badb70345a9b92f72ab2eb9

@alyssaoc alyssaoc added priority: medium Work needs to be done within 2-3 sprints and removed consider soon Discuss this issue at the next planning meeting, then remove this label priority: low Work should be done but can stay in the backlog for now labels Jan 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
level: 2 Some knowledge of the existing code is recommended needs: exploration Solution unclear, needs research priority: medium Work needs to be done within 2-3 sprints type: improvement Existing (or partially existing) functionality needs to be changed
Projects
None yet
Development

No branches or pull requests

4 participants