Add support/stake attributes to metadata #20

New issue

Closed

opened 2019-02-11 18:02:41 +01:00 by tzarebczan · 2 comments

tzarebczan commented

2019-02-11 18:02:41 +01:00

(Migrated from github.com)

Some ideas:

Note/Comment/Description (like a permanent comment?)
Signature (sign stakes with channels?)

See original discussion in https://github.com/lbryio/lbry/issues/919

Trying to determine if there's a way to tell tips vs supports at the surface, without a type. Seems like comparing to the claim address is the only way, so we should not need this in the metadata. This breaks currently when the claim is updated, so we need to make sure claim updates keep the same address, but we may still want to pursue the type as a configured attribute.

Some ideas: 1) Note/Comment/Description (like a permanent comment?) 2) Signature (sign stakes with channels?) See original discussion in https://github.com/lbryio/lbry/issues/919 Trying to determine if there's a way to tell tips vs supports at the surface, without a type. Seems like comparing to the claim address is the only way, so we should not need this in the metadata. This breaks currently when the claim is updated, so we need to make sure claim updates keep the same address, but we may still want to pursue the type as a configured attribute.

tzarebczan commented

2019-02-15 18:03:02 +01:00

(Migrated from github.com)

Sounds like this one requires blockchain changes. Will get that issue filed if it's not already.

alyssaoc commented

2019-03-20 21:16:02 +01:00

(Migrated from github.com)

closing in favor of #919

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/types#20

No description provided.