Skip to content

CIP-0153 | Add range limits to amounts in builtin Value #1095

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rphair merged 1 commit into from
Oct 28, 2025
Merged

CIP-0153 | Add range limits to amounts in builtin Value #1095

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CIP-0153/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,6 +91,7 @@ We propose the following set of builtin functions to accompany the new builtin t
- it returns a Mary-era Value with the `Coin` inserted, silently discarding any previous value.
If the `BuiltinInteger` argument (the quantity) is zero, the `Coin` is removed.
- Both `BuiltinCurrencySymbol` and `BuiltinTokenName` must be no longer than 32 bytes (unless the amount is zero).
- The amount (`BuiltinInteger`) must satisfy -2<sup>127</sup> ≤ amount ≤ 2<sup>127</sup>-1.
2. `lookupCoin :: BuiltinCurrencySymbol -> BuiltinTokenName -> BuiltinValue -> BuiltinQuantity`
- it returns the quantity of a given `Coin` in a Mary-era Value.
3. `unionValue :: BuiltinValue -> BuiltinValue -> BuiltinValue`
Expand All @@ -106,6 +107,7 @@ We propose the following set of builtin functions to accompany the new builtin t
6. `unValueData :: BuiltinData -> BuiltinValue`
- decodes a `BuiltinData` into a `BuiltinValue`, or fails if it is not one.
- All currency symbols and token names must be no longer than 32 bytes.
- All amounts must lie between -2<sup>127</sup> and 2<sup>127</sup>-1 (inclusive).

A note on `valueData` and `unValueData`: in Plutus V1, V2 and V3, the encoding of `BuiltinValue` in `BuiltinData` is identical to that of the [existing `Value` type](https://plutus.cardano.intersectmbo.org/haddock/latest/plutus-ledger-api/PlutusLedgerApi-V1-Value.html#t:Value) in plutus-ledger-api.
This ensures backwards compatibility.
Expand Down