Home / Input Output / plutus
Apr 10, 6-7 PM (0)
Apr 10, 7-8 PM (0)
Apr 10, 8-9 PM (0)
Apr 10, 9-10 PM (0)
Apr 10, 10-11 PM (0)
Apr 10, 11-12 AM (0)
Apr 11, 12-1 AM (0)
Apr 11, 1-2 AM (0)
Apr 11, 2-3 AM (0)
Apr 11, 3-4 AM (0)
Apr 11, 4-5 AM (0)
Apr 11, 5-6 AM (0)
Apr 11, 6-7 AM (0)
Apr 11, 7-8 AM (0)
Apr 11, 8-9 AM (0)
Apr 11, 9-10 AM (0)
Apr 11, 10-11 AM (1)
Apr 11, 11-12 PM (0)
Apr 11, 12-1 PM (0)
Apr 11, 1-2 PM (0)
Apr 11, 2-3 PM (0)
Apr 11, 3-4 PM (0)
Apr 11, 4-5 PM (0)
Apr 11, 5-6 PM (0)
Apr 11, 6-7 PM (0)
Apr 11, 7-8 PM (0)
Apr 11, 8-9 PM (1)
Apr 11, 9-10 PM (0)
Apr 11, 10-11 PM (0)
Apr 11, 11-12 AM (0)
Apr 12, 12-1 AM (0)
Apr 12, 1-2 AM (0)
Apr 12, 2-3 AM (0)
Apr 12, 3-4 AM (0)
Apr 12, 4-5 AM (0)
Apr 12, 5-6 AM (0)
Apr 12, 6-7 AM (0)
Apr 12, 7-8 AM (0)
Apr 12, 8-9 AM (0)
Apr 12, 9-10 AM (0)
Apr 12, 10-11 AM (1)
Apr 12, 11-12 PM (0)
Apr 12, 12-1 PM (0)
Apr 12, 1-2 PM (0)
Apr 12, 2-3 PM (0)
Apr 12, 3-4 PM (0)
Apr 12, 4-5 PM (0)
Apr 12, 5-6 PM (0)
Apr 12, 6-7 PM (0)
Apr 12, 7-8 PM (0)
Apr 12, 8-9 PM (0)
Apr 12, 9-10 PM (0)
Apr 12, 10-11 PM (0)
Apr 12, 11-12 AM (0)
Apr 13, 12-1 AM (0)
Apr 13, 1-2 AM (0)
Apr 13, 2-3 AM (0)
Apr 13, 3-4 AM (0)
Apr 13, 4-5 AM (0)
Apr 13, 5-6 AM (0)
Apr 13, 6-7 AM (0)
Apr 13, 7-8 AM (0)
Apr 13, 8-9 AM (0)
Apr 13, 9-10 AM (0)
Apr 13, 10-11 AM (0)
Apr 13, 11-12 PM (0)
Apr 13, 12-1 PM (1)
Apr 13, 1-2 PM (6)
Apr 13, 2-3 PM (1)
Apr 13, 3-4 PM (0)
Apr 13, 4-5 PM (0)
Apr 13, 5-6 PM (0)
Apr 13, 6-7 PM (0)
Apr 13, 7-8 PM (0)
Apr 13, 8-9 PM (0)
Apr 13, 9-10 PM (0)
Apr 13, 10-11 PM (0)
Apr 13, 11-12 AM (0)
Apr 14, 12-1 AM (0)
Apr 14, 1-2 AM (0)
Apr 14, 2-3 AM (0)
Apr 14, 3-4 AM (0)
Apr 14, 4-5 AM (0)
Apr 14, 5-6 AM (0)
Apr 14, 6-7 AM (0)
Apr 14, 7-8 AM (0)
Apr 14, 8-9 AM (1)
Apr 14, 9-10 AM (3)
Apr 14, 10-11 AM (1)
Apr 14, 11-12 PM (2)
Apr 14, 12-1 PM (0)
Apr 14, 1-2 PM (3)
Apr 14, 2-3 PM (3)
Apr 14, 3-4 PM (5)
Apr 14, 4-5 PM (0)
Apr 14, 5-6 PM (1)
Apr 14, 6-7 PM (1)
Apr 14, 7-8 PM (1)
Apr 14, 8-9 PM (0)
Apr 14, 9-10 PM (0)
Apr 14, 10-11 PM (0)
Apr 14, 11-12 AM (0)
Apr 15, 12-1 AM (0)
Apr 15, 1-2 AM (0)
Apr 15, 2-3 AM (0)
Apr 15, 3-4 AM (0)
Apr 15, 4-5 AM (0)
Apr 15, 5-6 AM (0)
Apr 15, 6-7 AM (0)
Apr 15, 7-8 AM (0)
Apr 15, 8-9 AM (0)
Apr 15, 9-10 AM (1)
Apr 15, 10-11 AM (3)
Apr 15, 11-12 PM (0)
Apr 15, 12-1 PM (1)
Apr 15, 1-2 PM (3)
Apr 15, 2-3 PM (0)
Apr 15, 3-4 PM (0)
Apr 15, 4-5 PM (2)
Apr 15, 5-6 PM (2)
Apr 15, 6-7 PM (1)
Apr 15, 7-8 PM (0)
Apr 15, 8-9 PM (0)
Apr 15, 9-10 PM (0)
Apr 15, 10-11 PM (0)
Apr 15, 11-12 AM (0)
Apr 16, 12-1 AM (0)
Apr 16, 1-2 AM (0)
Apr 16, 2-3 AM (0)
Apr 16, 3-4 AM (0)
Apr 16, 4-5 AM (0)
Apr 16, 5-6 AM (0)
Apr 16, 6-7 AM (2)
Apr 16, 7-8 AM (0)
Apr 16, 8-9 AM (0)
Apr 16, 9-10 AM (0)
Apr 16, 10-11 AM (1)
Apr 16, 11-12 PM (0)
Apr 16, 12-1 PM (1)
Apr 16, 1-2 PM (2)
Apr 16, 2-3 PM (4)
Apr 16, 3-4 PM (1)
Apr 16, 4-5 PM (0)
Apr 16, 5-6 PM (0)
Apr 16, 6-7 PM (0)
Apr 16, 7-8 PM (0)
Apr 16, 8-9 PM (0)
Apr 16, 9-10 PM (0)
Apr 16, 10-11 PM (0)
Apr 16, 11-12 AM (0)
Apr 17, 12-1 AM (0)
Apr 17, 1-2 AM (0)
Apr 17, 2-3 AM (0)
Apr 17, 3-4 AM (0)
Apr 17, 4-5 AM (0)
Apr 17, 5-6 AM (0)
Apr 17, 6-7 AM (0)
Apr 17, 7-8 AM (1)
Apr 17, 8-9 AM (0)
Apr 17, 9-10 AM (4)
Apr 17, 10-11 AM (0)
Apr 17, 11-12 PM (0)
Apr 17, 12-1 PM (2)
Apr 17, 1-2 PM (1)
Apr 17, 2-3 PM (3)
Apr 17, 3-4 PM (2)
Apr 17, 4-5 PM (1)
Apr 17, 5-6 PM (0)
Apr 17, 6-7 PM (0)
70 commits this week Apr 10, 2026 - Apr 17, 2026
fix(bench): prevent ValueData benchmark crash (#7723)
The ValueData/UnValueData benchmark generator produced Values up
to 50_000 entries, but the `valueData` builtin rejects inputs
whose totalSize exceeds `valueDataMaxSize` (40_000). Oversized
inputs caused CekEvaluationFailure, which benchWith escalates
via `error`, tearing down the whole Criterion run and discarding
earlier measurements.

Tie the generator directly to the builtin's constant: export
`valueDataMaxSize` from PlutusCore.Value and use it in place of
the local `maxValueEntries`. This makes the two limits
structurally impossible to drift apart. Enable NumericUnderscores
in the package's default-extensions so the constant can be
written as `40_000`.
fix(bench): prevent ValueData benchmark crash
The ValueData/UnValueData benchmark generator produced Values up
to 50_000 entries, but the `valueData` builtin rejects inputs
whose totalSize exceeds `valueDataMaxSize` (40_000). Oversized
inputs caused CekEvaluationFailure, which benchWith escalates
via `error`, tearing down the whole Criterion run and discarding
earlier measurements.

Tie the generator directly to the builtin's constant: export
`valueDataMaxSize` from PlutusCore.Value and use it in place of
the local `maxValueEntries`. This makes the two limits
structurally impossible to drift apart. Enable NumericUnderscores
in the package's default-extensions so the constant can be
written as `40_000`.