commit d460b5d74205a94365a51d915863ae459c33146b parent 5dffbf846dac3499f7bccb36fcb62e0eb1bf40b5 Author: Antoine A <> Date: Tue, 17 Feb 2026 16:14:39 +0100 dd80: improve subject format name Diffstat:
| M | design-documents/080-short-wire-subject.rst | | | 14 | +++++++------- |
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/design-documents/080-short-wire-subject.rst b/design-documents/080-short-wire-subject.rst @@ -190,8 +190,8 @@ mathematical fariness across any alphabet size. } - SIMPLE: no special encoding use the current very verbose encoding -- CH-YUH: BASE32 encode and trunc N chars -- NZ-SBI: BASE32 encode and trunc 36 char split in 3 chunk of 12 char +- CH_YUH: BASE32 encode and trunc N chars +- NZ_SBI: BASE32 encode and trunc 36 char split in 3 chunk of 12 char - BTC: trunc and encode in segwit address .. ts:def:: TransferSubject @@ -226,7 +226,7 @@ mathematical fariness across any alphabet size. interface NzSbiSubject { // Subject for New Zealand Settlement Before Interchange system - type: "NZ-SBI"; + type: "NZ_SBI"; // 12 chars to set in the Particulars field particulars: string; @@ -249,15 +249,15 @@ Sometimes some clients will have more restriction than others. We will sometimes // BTC: bitcoin address type SubjectFormat = | "SIMPLE" - | "CH-YUH" - | "NZ-SBI" + | "CH_YUH" + | "NZ_SBI" | "BTC"; The backend will expose the supported formats in its ``/config`` endpoint. -- "SIMPLE" & "CH-YUH" -> SimpleSubject +- "SIMPLE" & "CH_YUH" -> SimpleSubject - "BTC" -> BitcoinSubject -- "NZ-SBI" -> NzSbiSubject +- "NZ_SBI" -> NzSbiSubject Proof of Work -------------