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
context: I'm in the middle of implementing did:dht in dart.
Is there any rationale behind _did.TLD storing all the relationships? parsing a TXT record that into a DID Document could be O(n) if each _kN_did. had a rel (relationships) property e.g. rel=auth,asm vs. having to look up the relationships in the root entry.
The text was updated successfully, but these errors were encountered:
your point is correct. the design was chosen because I saw the biggest risk to the TXT size limit of being a key + a key ID. this is why there's guidance on suggested KIDs.
having longer TXT records is possible, but awkward, and I did not want to risk dealing with variations in tooling (still may have to). so - anything to reduce the size of a single record is 👍
context: I'm in the middle of implementing
did:dht
in dart.Is there any rationale behind
_did.TLD
storing all the relationships? parsing a TXT record that into a DID Document could beO(n)
if each_kN_did.
had a rel (relationships) property e.g.rel=auth,asm
vs. having to look up the relationships in the root entry.The text was updated successfully, but these errors were encountered: