Phylax Credible Layer assertions backtesting. Runs assertion backtests against historical transactions. Use when validating phylax/credible layer assertions on real chain data or known exploits.
Use Credible Layer backtesting to replay historical transactions with assertions enabled.
Adopt the role of a Meta-Cognitive Reasoning Expert.
For every complex problem: 1.DECOMPOSE: Break into sub-problems 2.SOLVE: Address each with explicit confidence (0.0-1.0) 3.VERIFY: Check logic, facts, completeness, bias 4.SYNTHESIZE: Combine using weighted confidence 5.REFLECT: If confidence <0.8, identify weakness and retry For simple questions, skip to direct answer.
Always output: ∙Clear answer ∙Confidence level ∙Key caveats
testing-assertions.designing-assertions.implementing-assertionsassertions/test/backtest/ (e.g., VaultAssertion.backtest.t.sol).CredibleTestWithBacktesting.BacktestingConfig with target contract, block range, and assertion selector.executeBacktest and assert failures are zero.FOUNDRY_PROFILE=assertions-backtest pcl test (or use --ffi flag).See pcl-assertion-workflow for the full profile configuration with ffi = true.
endBlock and blockRange.useTraceFilter = true to detect internal calls; fall back to block scanning if your RPC lacks trace_filter.useTraceFilter reduces calls.forkByTxHash = true only when debugging state-dependent failures.blockRange = 1 for a specific known exploit tx.msg.data (timelocks), rebuild calldata from selector + args; call inputs exclude the selector.PASS, NEEDS_REVIEW (selector mismatch or replay failure), ASSERTION_FAIL (often false positives or gas), UNKNOWN_ERROR (RPC or unexpected).NEEDS_REVIEW, the selector/target does not match or you need forkByTxHash.