Skip to content
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

Jump to bottom

Specification of how the script context is converted into Data #3280

Closed
effectfully opened this issue Feb 3, 2023 · 0 comments · Fixed by #3306
Closed

Specification of how the script context is converted into Data #3280

effectfully opened this issue Feb 3, 2023 · 0 comments · Fixed by #3306
Labels
alonzo 📜 formal-spec

Comments

@effectfully
Copy link

The Plutus repo has an issue regarding the ordering of inputs in TxInfo. The conclusion in that thread seems to be that the behavior is expected, but the way the script context is converted into Data needs to be explicitly elaborated on in the ledger spec. Hence this ticket.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
alonzo 📜 formal-spec
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add description of lex order for sets in Alonzo spec IntersectMBO/cardano-ledger
2 participants
@JaredCorduan @effectfully