LaconicNetwork/cosmos-sdk
9
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 2 Wiki Activity

docs: fix broken anchor link in ICS-030 spec (#24696)

Browse Source 
Co-authored-by: Alex | Interchain Labs <alex@interchainlabs.io>
This commit is contained in:
MozirDmitriy 2025-05-05 20:52:38 +03:00 committed by GitHub
parent 9c757efee7
commit 39e90e1a8e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/spec/_ics/ics-030-signed-messages.md
View File

@ -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: