Skip to content

fix(evolution): decode deeply nested CBOR and Plutus data without recursing per level (#662) #665

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

Open
Kshot3000 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(evolution): decode deeply nested CBOR and Plutus data without recursing per level (#662) #665

Show file tree
Hide file tree
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
5 changes: 5 additions & 0 deletions .changeset/cbor-deep-nesting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"@evolution-sdk/evolution": patch
---

Decoding deeply nested CBOR no longer overflows the call stack. The ledger limits the size of each leaf of Plutus data, not its depth, so a datum can nest roughly as deep as the transaction size allows (around 16,000 levels); `CBOR.fromCBORHex` failed with `RangeError` from about 1,719 levels and `Data.fromCBORHex` with a `ParseError` wrapping one from about 1,250. The offset CBOR decoder now runs on an explicit stack instead of recursing once per level, `cborValueToPlutusData` converts on an explicit action stack with structural type guards (the `Schema.is` guards validated each subtree recursively), and `Data.fromCBORBytes` / `Data.fromCBORHex` decode through those two functions directly, keeping the `ParseError` failure surface, instead of through the recursive schema parser. The `FromCBORBytes` / `FromCBORHex` / `FromCDDL` schemas keep their existing validation behaviour.
Loading