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
-`l` ("left", CID link, optional): link to sub-tree Node on a lower level and with all keys sorting before keys at this node
-`e` ("entries", array of objects, required): ordered list of TreeEntry objects
-`p` ("prefixlen", integer, required): count of bytes shared with previous TreeEntry in this Node (if any)
-`k` ("keysuffix", byte array, required): remainder of key for this TreeEntry, after "prefixlen" have been removed
-`v` ("value", CID Link, required): link to a sub-tree Node at a lower level which has keys sorting after this TreeEntry's key (to the "right"), but before the next TreeEntry's key in this Node (if any)
The v field is documented as:
✅ A CID link.
✅ Required.
⚠️ A link to a sub-tree Node.
After experimenting with my own repository's CAR, I've concluded that this is most likely an accidental merge of two separate fields:
v:
A CID link.
Required.
A link to the Lexicon value corresponding to this TreeEntry's key.
t:
A CID link.
Optional (CID link || null).
A link to a sub-tree Node.
The text was updated successfully, but these errors were encountered:
https://atproto.com/specs/repository#mst-structure
atproto-website/content/specs/repository.md
Lines 85 to 92 in 4744a24
The
v
field is documented as:After experimenting with my own repository's CAR, I've concluded that this is most likely an accidental merge of two separate fields:
v
:t
:The text was updated successfully, but these errors were encountered: