From 39e90e1a8ef2deda8bfca45ae6fc4f88159b17e5 Mon Sep 17 00:00:00 2001 From: MozirDmitriy Date: Mon, 5 May 2025 20:52:38 +0300 Subject: [PATCH] docs: fix broken anchor link in ICS-030 spec (#24696) Co-authored-by: Alex | Interchain Labs --- docs/spec/_ics/ics-030-signed-messages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/spec/_ics/ics-030-signed-messages.md b/docs/spec/_ics/ics-030-signed-messages.md index 9913149051..a7c56715b9 100644 --- a/docs/spec/_ics/ics-030-signed-messages.md +++ b/docs/spec/_ics/ics-030-signed-messages.md @@ -89,7 +89,7 @@ must equal the constant `"message"`. The `@type` field corresponds to the type o structure the user will be signing in an application. For now, a user is only allowed to sign bytes of valid ASCII text ([see here](https://github.com/cometbft/cometbft/blob/v0.37.0/libs/strings/string.go#L35-L64)). However, this will change and evolve to support additional application-specific -structures that are human-readable and machine-verifiable ([see Future Adaptations](#futureadaptations)). +structures that are human-readable and machine-verifiable ([see Future Adaptations](#future-adaptations)). Thus, we can have a canonical JSON structure for signing Cosmos messages using the [JSON schema](http://json-schema.org/) specification as such: