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 computation of the claim trie is the bottleneck on sync, and it will soon be the overall bottleneck on each new block. Many LBRY streams presently use this mechanism but have no need for claim competition, as they are grouped by channel.
We need to enable a mechanism to allow these streams-in-a-channel to migrate to a non-competitive registration. The proposed method is that we will modify the trie to ignore claims for the root node (aka, claims with an empty name will no longer compete). We will no longer allow someone to competitively claim the root node; there's no way to view it presently anyhow.
Subtasks
update LBRY spec to, among other things, remove the requirement that URLs have a name component. Add examples of URLs with only a claim ID.
we need a hard-fork plan for this.
the hard-fork will need to pull all the claims in root at present out of the trie.
should the RPC methods to query claims by name return the entire list of no-names?
proof RPC methods will need to not support empty claim names
The text was updated successfully, but these errors were encountered:
lyoshenka
changed the title
need to allow non-trie claims
Allow claims outside the claimtrie
Jan 19, 2021
The computation of the claim trie is the bottleneck on sync, and it will soon be the overall bottleneck on each new block. Many LBRY streams presently use this mechanism but have no need for claim competition, as they are grouped by channel.
We need to enable a mechanism to allow these streams-in-a-channel to migrate to a non-competitive registration. The proposed method is that we will modify the trie to ignore claims for the root node (aka, claims with an empty name will no longer compete). We will no longer allow someone to competitively claim the root node; there's no way to view it presently anyhow.
Subtasks
The text was updated successfully, but these errors were encountered: