Clarify allowed usage of Seed XOR standard and name
What changed, and why it matters
This commit only adds a short paragraph to documentation stating that Seed XOR is an open standard and that others may use the name and implement it freely. There is no code change, no security fix, and no vulnerability.
No security action needed; this is a policy/clarification documentation update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
A documentation-only change to docs/seed-xor.md adds an ‘Open Standard’ section clarifying licensing and naming terms for the Seed XOR feature. No firmware, build, cryptographic, or protocol code is modified.
Changed components
docs/seed-xor.mdInspect captured patch +6 / −0
diff --git a/docs/seed-xor.md b/docs/seed-xor.md
index 719a32c..b79fb84 100644
--- a/docs/seed-xor.md
+++ b/docs/seed-xor.md
@@ -157,6 +157,12 @@ with the others on a SEEDPLATE.
- right to A, down to B ... take that number, and go to that column
- down to C, that is answer: a ⊕ b ⊕ c
+## Open Standard
+Seed XOR is an open standard. Other software and hardware wallets are encouraged to
+implement support. No license or permission is required, including usage of the term
+"Seed XOR" when referring to implementations of this feature. Such implementations
+should match the process described in this documentation and be fully interoperable.
+
---
# 24 Words XOR Seed Example Using 3 Parts
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.