clarify a few points about updates
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 8
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
update LBRY spec to clarify that an update to a claim does not reset the activation delay. right now an update is treated as a new claim and resets the activation delay counter.
update spec to clarify that an update cannot change a name (and post-fork, a normalized name). updates must keep the name consistent.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the relevant update rules in the LBRY specification. Clarify that updating a claim does not reset its activation delay, and that updates must preserve both the name and, post-fork, the normalized name. Done means the specification explicitly states all three constraints.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100