From 2bf547ca7a438dab1da842109669559635758fa5 Mon Sep 17 00:00:00 2001 From: jintekc Date: Wed, 28 Jan 2026 14:52:14 -0500 Subject: [PATCH 1/4] Add bibtex entry for SEC2 --- src/references.bib | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/src/references.bib b/src/references.bib index d6bff9f..cf70dda 100644 --- a/src/references.bib +++ b/src/references.bib @@ -162,7 +162,7 @@ @techreport{RFC8785 This document describes the JSON Canonicalization Scheme (JCS). This specification defines how to create a canonical representation of JSON data by building on the strict serialization methods for JSON primitives defined by ECMAScript, constraining JSON data to the Internet JSON (I-JSON) subset, and by using deterministic property sorting.} } -@techreport{SEC, +@techreport{SEC1, title = {Standards for Efficient Cryptography 1 (SEC 1): Elliptic Curve Cryptography}, author = {Certicom Research and Daniel R. L. Brown}, institution = {Standards for Efficient Cryptography Group (SECG)}, @@ -181,6 +181,24 @@ @techreport{SEC The schemes are intended for general application within computer and communications systems.}, } + +@techreport{SEC2, + title = {Standards for Efficient Cryptography 2 (SEC 2): Recommended Elliptic Curve Domain Parameters}, + author = {Certicom Research and Daniel R. L. Brown}, + institution = {Standards for Efficient Cryptography Group (SECG)}, + number = {Version 2.0}, + year = {2009}, + month = {May}, + url = {https://www.secg.org/sec2-v2.pdf}, + abstract = {This document lists example elliptic curve domain parameters at commonly required security levels +for use by implementers of SEC 1 [SEC 1] and other ECC standards like ANSI X9.62 [X9.62], ANSI +X9.63 [X9.63], and IEEE 1363 [1363] and IEEE 1363a [1363A]. + +It is strongly recommended that implementers select parameters from among the parameters listed +in this document when they deploy ECC-based products in order to encourage the deployment of +interoperable ECC-based solutions.}, +} + @techreport{SHA256, title = {Secure Hash Standard (SHS)}, author = {{National Institute of Standards and Technology}}, From bd59eaa668d112ba6b67cc018538f5a913708c33 Mon Sep 17 00:00:00 2001 From: jintekc Date: Wed, 28 Jan 2026 14:53:39 -0500 Subject: [PATCH 2/4] Update terminology SEC citation --- src/terminology.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/terminology.md b/src/terminology.md index 510cc6d..a1dd20a 100644 --- a/src/terminology.md +++ b/src/terminology.md @@ -140,7 +140,7 @@ The algorithm is specified in BIP340 Cryptosuites v0.1 {{#cite BIP340-Cryptosuit ## Genesis Bytes { #genesis-bytes } The bytes used to generate a **did:btcr2** identifier. These bytes are either a 33-byte compressed -Standards for Efficient Cryptography (SEC) encoded secp256k1 public key or a 32-byte SHA-256 hash +Standards for Efficient Cryptography (SEC2) encoded secp256k1 public key or a 32-byte SHA-256 hash of a [Genesis Document]. ## Genesis Document { #genesis-document } From 6dbc09c8f99fbde48e5520edab3a0433da4b69f6 Mon Sep 17 00:00:00 2001 From: Jintek Date: Wed, 28 Jan 2026 15:41:52 -0500 Subject: [PATCH 3/4] Update src/terminology.md Co-authored-by: Jay Oster --- src/terminology.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/terminology.md b/src/terminology.md index a1dd20a..0ed572d 100644 --- a/src/terminology.md +++ b/src/terminology.md @@ -140,7 +140,7 @@ The algorithm is specified in BIP340 Cryptosuites v0.1 {{#cite BIP340-Cryptosuit ## Genesis Bytes { #genesis-bytes } The bytes used to generate a **did:btcr2** identifier. These bytes are either a 33-byte compressed -Standards for Efficient Cryptography (SEC2) encoded secp256k1 public key or a 32-byte SHA-256 hash +Standards for Efficient Cryptography ({{#cite SEC2}}) encoded secp256k1 public key or a 32-byte SHA-256 hash of a [Genesis Document]. ## Genesis Document { #genesis-document } From 6fd1380cac893483f6fcb2a3d925155cc22dbfb6 Mon Sep 17 00:00:00 2001 From: jintekc Date: Thu, 29 Jan 2026 09:39:07 -0500 Subject: [PATCH 4/4] SEC citation, remove SEC2 --- src/operations/create.md | 3 +-- src/references.bib | 20 +------------------- src/terminology.md | 2 +- 3 files changed, 3 insertions(+), 22 deletions(-) diff --git a/src/operations/create.md b/src/operations/create.md index 263cb6e..1f944da 100644 --- a/src/operations/create.md +++ b/src/operations/create.md @@ -29,8 +29,7 @@ or from a [Genesis Document]. An secp256k1 public key can be used as the [Genesis Bytes]. The key MUST be in its compressed SEC format: a 33-byte representation consisting of a single prefix byte (`0x02` or `0x03`) followed by the 32-byte x-coordinate of -the elliptic curve point. -Reference Section 2.3.3 in SEC 1: Elliptic Curve Cryptography {{#cite SEC}}. +the elliptic curve point. Reference Section 2.3.3 in SEC 1: Elliptic Curve Cryptography {{#cite SEC}}. ## Genesis Document Hash diff --git a/src/references.bib b/src/references.bib index cf70dda..d6bff9f 100644 --- a/src/references.bib +++ b/src/references.bib @@ -162,7 +162,7 @@ @techreport{RFC8785 This document describes the JSON Canonicalization Scheme (JCS). This specification defines how to create a canonical representation of JSON data by building on the strict serialization methods for JSON primitives defined by ECMAScript, constraining JSON data to the Internet JSON (I-JSON) subset, and by using deterministic property sorting.} } -@techreport{SEC1, +@techreport{SEC, title = {Standards for Efficient Cryptography 1 (SEC 1): Elliptic Curve Cryptography}, author = {Certicom Research and Daniel R. L. Brown}, institution = {Standards for Efficient Cryptography Group (SECG)}, @@ -181,24 +181,6 @@ @techreport{SEC1 The schemes are intended for general application within computer and communications systems.}, } - -@techreport{SEC2, - title = {Standards for Efficient Cryptography 2 (SEC 2): Recommended Elliptic Curve Domain Parameters}, - author = {Certicom Research and Daniel R. L. Brown}, - institution = {Standards for Efficient Cryptography Group (SECG)}, - number = {Version 2.0}, - year = {2009}, - month = {May}, - url = {https://www.secg.org/sec2-v2.pdf}, - abstract = {This document lists example elliptic curve domain parameters at commonly required security levels -for use by implementers of SEC 1 [SEC 1] and other ECC standards like ANSI X9.62 [X9.62], ANSI -X9.63 [X9.63], and IEEE 1363 [1363] and IEEE 1363a [1363A]. - -It is strongly recommended that implementers select parameters from among the parameters listed -in this document when they deploy ECC-based products in order to encourage the deployment of -interoperable ECC-based solutions.}, -} - @techreport{SHA256, title = {Secure Hash Standard (SHS)}, author = {{National Institute of Standards and Technology}}, diff --git a/src/terminology.md b/src/terminology.md index 0ed572d..ffde3ba 100644 --- a/src/terminology.md +++ b/src/terminology.md @@ -140,7 +140,7 @@ The algorithm is specified in BIP340 Cryptosuites v0.1 {{#cite BIP340-Cryptosuit ## Genesis Bytes { #genesis-bytes } The bytes used to generate a **did:btcr2** identifier. These bytes are either a 33-byte compressed -Standards for Efficient Cryptography ({{#cite SEC2}}) encoded secp256k1 public key or a 32-byte SHA-256 hash +Standards for Efficient Cryptography ({{#cite SEC}}) encoded secp256k1 public key or a 32-byte SHA-256 hash of a [Genesis Document]. ## Genesis Document { #genesis-document }