lbry-sdk
lbry-sdk copied to clipboard
lbryio
Update `staked_amount` to include stakes inside a channel in that channels amount
-
effective_amountstays as is -
staked_amountis a new field that- is sum of staked lbc for a claim and all its supports
- is not affected by activation delay
- for a channel, also includes the
staked_amountof all content claims (not recursive, doesn't descend into channels signed by channels) in that channel
- add new field to resolve for channels that lists the sum effective amounts for a channel's content claims
- make sure you can sort by that field (via
claim_search) - potentially have effective_amount changes take effect immediately when accessed via claim_search (or via special flag)
sorting is less important, just getting the info on resolve is the most useful for the first feature
this is basically now the only missing piece in having the naming/bidding system user experience be far more compelling (searching changes and reposting changes are done app side)
@kauffj Last we discussed this, we mentioned that a claim should be its total supports, plus its channel's total supports. This way new content from a known credible source gets the right bump by just being from a credible source. Not just its own supports. Is that no longer the case or did it just get lost in the shuffle?
There's no way to stop someone from creating another channel/account and supporting it from there, so I don't think it makes sense to force it. Plus, we want publishers to self support as well.
