Skip to content

Mention inline datum CIP-32 within the Alonzo spec document #4960

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.

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

Open
nfrisby opened this issue Mar 31, 2025 · 2 comments
Open

Mention inline datum CIP-32 within the Alonzo spec document #4960

nfrisby opened this issue Mar 31, 2025 · 2 comments
Labels
🖋️ documentation Everything related to documenting code, processes, etc.

Comments

@nfrisby
Copy link
Contributor

nfrisby commented Mar 31, 2025

The Alonzo spec says

Image

But the later "inline datum" CIP violates that https://cips.cardano.org/cip/CIP-32.

This Issue is a suggestion to add a footnote to the Alonzo spec's text mentioning CIP-32, just so that the reader of the document would be warned.


Unless the Ledger Team already decided that it's hopeless to keep each of their specs fully-up-to-date, and so not worth it to make ad-hoc attempts like this one?

@nfrisby nfrisby added the 🖋️ documentation Everything related to documenting code, processes, etc. label Mar 31, 2025
@carlostome
Copy link
Contributor

Inline datums are already documented in the Babbage era specification: https://github.com/intersectmbo/cardano-ledger/releases/latest/download/babbage-ledger.pdf (Section 3), which is when they were introduced. Maybe what is missing in the Babbage spec is a reference to the CIP.

Since specifications for later eras build (and change) previous ones and this is already documented, I think there is no need to change the Alonzo spec.

@lehins
Copy link
Collaborator

lehins commented Mar 31, 2025

@carlostome I think what @nfrisby is trying to say is that the motivation for not doing inline datums in Alonzo was that it would "affect UTxO storage requirements". Which we went ahead and did in Babbage anyways.
So, I don't think it is a mistake or anything, but a clarification that not to store datums in UTxO in Alonzo was a choice, not a requirement is missing, IMHO

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🖋️ documentation Everything related to documenting code, processes, etc.
Projects
None yet
Development

No branches or pull requests

3 participants