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
In terms of proving conformance/interoperability across different language implementations, today we have test vectors that allows us to go as far as validating each individual DNS record is in the correct format, but those checks does not guarantee the "bundle" (encodedDNS packet) that gets uploaded to the DHT is in the valid/expected format.
Provided the BEP44 message has deterministic signature AND different DNS packet encode libraries ALWAYS produces the same bytes given the same set of records even in DIFFERENT orders (these are big assumptions), it would be the most ideal for us to have test vector as close to the final output as possible: ie. either the BEP44 message itself, or the encoded DWN packet before the signature wrapping + test vector for BEP44 support.
Provide a way for implementers to prove conformance for different feature sets
The text was updated successfully, but these errors were encountered: