From 393ed982945cc5d53dddf3653d429b871e3b86a1 Mon Sep 17 00:00:00 2001 From: raphjaph Date: Sat, 25 Jan 2025 10:13:14 +0100 Subject: [PATCH] Use full tags for signing --- Messaging.md | 2 +- Oracle.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Messaging.md b/Messaging.md index b31bf4b..975de92 100644 --- a/Messaging.md +++ b/Messaging.md @@ -423,7 +423,7 @@ See [the Oracle specifications](./Oracle.md#oracle-announcements) for more detai * [`x_point`:`oracle_public_key`] * [`oracle_event`:`oracle_event`] -where `signature` is a Schnorr signature over a sha256 hash of the serialized `oracle_event`, using the tag `announcement/v0`. +where `signature` is a Schnorr signature over a sha256 hash of the serialized `oracle_event`, using the tag `DLC/oracle/announcement/v0`. ### The `oracle_attestation` Type diff --git a/Oracle.md b/Oracle.md index 6fb543e..4e49061 100644 --- a/Oracle.md +++ b/Oracle.md @@ -94,7 +94,7 @@ UTF-8 is chosen as being a widely supported and easy to implement encoding forma For numerical outcomes represented in bases greater than 10, each digit should be converted to base 10 before being encoded (note that base 10 numbers in UTF-8 take values in the 0x0030-0x0039 range). This helps preventing any confusion about the capitalization of letters or the introduction of non-standard characters. -Signing should be done using the [signing algorithm](#Signing-Algorithm) using the tag `attestation/v0`. +Signing should be done using the [signing algorithm](#Signing-Algorithm) using the tag `DLC/oracle/attestation/v0`. ### Serialization of event descriptors