fix: make bark and utxorpc gRPC startup errors deterministic
Signed-off-by: cryptodj413 <[email protected]>
Signed-off-by: cryptodj413 <[email protected]>
11-experiment everyone sweep (5 NA throughputs + 6 Plutus levels) re-run with the unbounded-mempool default. Completes the 750n trio alongside the wfa-ls and top-stake-fraction commits. Includes case.csv, config.yaml, summary.txt, time.txt for each. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
In `conwayGovTransition`, we remove the condition on `hardforkConwayBootstrapPhase` for checking `ZeroTreasuryWithdrawals`. We then replayed the preview, preprod and mainnet public chains with this change which guarentees there were no empty treasury withdrawals pre-Conway era.
Bump `cuddle` to 1.7.0.0
Signed-off-by: Eric Torreborre <[email protected]>
We no longer need to check for thunks in the contents of `BlockTransitionError`, becasue the constructor uses `deepseq` to force everything to normal form. We could of course bring back strictness annotation and `NoThunks` instances for all of the predicate failures, however this whole overhead is an overkill, because: * we do not need to optimize for the failing case and it is ok to introduce a little overhead upon failure. FTR: the only time we persist predicate failures is when we write to disk temporarely for chains with bad blocks. * Maintaining `NoThunks` instances for *all* predicate failures for a single edge is a burden * There is a plan to utilize laziness in predicate failures in order to add timing measurement for failure checks in ledger rules
Signed-off-by: cryptodj413 <[email protected]>