You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The blockchain will be adding the ability to assign a value to supports. This will allow us store metadata along with supports, including channel signing. The type should be flexible to support multiple use cases.
Use case ideas:
Reposting content(lbryio/lbry-sdk#2028)
Commenting (with/without tips)
Ratings
Community tagging
Blockchain based subscriptions
The text was updated successfully, but these errors were encountered:
I would not worry about that for now. The whole point of the comments prototype is to get something out before we know exactly what's on the blockchain side. It will fill the gaps for us.
I started writing up something for this and then lost it, so I'll be a bit briefer here. I know we'll start adding metadata and signing to supports soon, and I also think we should consider generating some type of authentication keys that users can exchange in this manner also . One example would be the creator-owned relationships - where a subscription (special support) on the blockchain allows receiver to view certain parts of the channel metadata (would need to be spec'd out) and share a content key to unlock future premium publishes.
The blockchain will be adding the ability to assign a value to supports. This will allow us store metadata along with supports, including channel signing. The type should be flexible to support multiple use cases.
Use case ideas:
Reposting content(lbryio/lbry-sdk#2028)
Commenting (with/without tips)
Ratings
Community tagging
Blockchain based subscriptions
The text was updated successfully, but these errors were encountered: