Problem: can't see how long a problem has been claimed for
People sometimes claim problems and disappear, leaving it in a locked state.
Maintainers can free these problems, but they shouldn't do this unless the time the problem has been locked for exceeds 432 blocks.
Solution:
Display how many blocks a problem has been claimed for
Problem: nostrocket is not aware of the current Bitcoin height
Solution: anyone with votepower can publish blocks, anyone without votepower can validate them.
I'm claiming [Problem: nostrocket is not aware of the current Bitcoin height] on the nostrocket problem tracker so that I can work on it and other people don't duplicate my efforts.
Happy 800k blocks
I'm closing [Problem: nostrocket is not aware of the current Bitcoin height] on the nostrocket problem tracker, it's been resolved or become obsolete.
To me the idea of claiming a problem is itself problematic, because it introduces a lock where it's not really necessary. Patches or pull requests should be invited from all comers and merged quickly so the doers can build momentum.
This rule is in response to an observed problem when operating at scale (most of this protocol has been tested in reality).
Patches *are* invited from everyone, and merged quickly.
What often happens when you have 30+ people working on the same set of problems is that multiple people spend time on the same problem without telling each other, and everyone who tries to send a PR after the first patch is merged gets annoyed that they wasted their time, this is a pain point that can be resolved very simply: you MAY claim a problem to work on it, but if you work on it without claiming it you accept the risk that you might be wasting your time.
This risk disappears if you claim it first.
