Skip to content

Commit

Permalink
Update overview.md
Browse files Browse the repository at this point in the history
Correct ranges of 64bit signed and unsigned integers.
  • Loading branch information
bjornkihlberg authored Dec 7, 2023
1 parent d8b24c4 commit 9cf32f1
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/transaction-metadata/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,11 +36,11 @@ The Cardano Foundation's integrations team hosted a session on transaction metad

Metadata can be expressed as a `JSON` object with some restrictions:

All top-level keys must be **integers** between 0 and 2^64 - 1. Each metadata value is tagged with its type. **Strings** must be at most 64 bytes when UTF-8 is encoded. **Bytestrings** are hex-encoded, with a maximum length of 64 bytes. Metadata aren't stored as `JSON` on the Cardano blockchain but are instead stored using a compact binary encoding (**CBOR**).
All top-level keys must be **integers** between 0 and 2^63 - 1. Each metadata value is tagged with its type. **Strings** must be at most 64 bytes when UTF-8 is encoded. **Bytestrings** are hex-encoded, with a maximum length of 64 bytes. Metadata aren't stored as `JSON` on the Cardano blockchain but are instead stored using a compact binary encoding (**CBOR**).

The binary encoding of metadata values supports three simple types:

- Integers in the range `-(2^64 - 1) to 2^64 - 1`
- Integers in the range `-(2^63) to 2^63 - 1`
- Strings (`UTF-8` encoded)
- Bytestrings
- And two compound types:
Expand Down

0 comments on commit 9cf32f1

Please sign in to comment.