Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutRoadmapCareersInternshipsFAQContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • Reading Paths
  • Glossary
  • Metrics Reference
  • Formal Cheat Sheet
  • Formal Foundations19
  • Properties and SVA16
  • Property Development and Constraints19
  • Proof Engines and Convergence23
  • Formal Applications20
  • Equivalence Checking14
  • Formal Coverage and Signoff15
  • Methodology and Debug13
  • Interview Prep15
  • Capstone: A Chip-Block Verification Lab24
    • The Brief
    • Stage 1: FIFO and Handshake
    • Stage 2: Registers and Arbiter
    • Stage 3: Pipeline and Equivalence
    • Stage 4: Induction and Signoff
    • Solutions
      • Solutions: FIFO Property Set
      • Solutions: Bridge and the Assumption Trap
      • Solutions: Registers and the Property Mutants
      • Solutions: Arbiter Wait Bound
      • Solutions: Pairs and Chain
      • Solutions: Pipeline, Twin and ECO
      • Solutions: Counter and Induction
      • Solutions: Ledger and Final Manifest
    • Appendix: Run It Yourself on an Open-Source Flow
Loading lesson

←Capstone: A Chip-Block Verification Lab
  1. Topics
  2. Formal Verification
  3. Capstone: A Chip-Block Verification Lab
  4. Solutions

Part 10 of 10Part 10 of 10/Capstone: A Chip-Block Verification LabAll levels

Solutions

The causes, killing properties, failing steps and fixes of all sixteen planted faults, the property mutants, and the reference ledger with its final manifest.

  • 8topics
  • 8lessons

Open this topic after your own package passes the engine. Each lesson repeats the runs of the stage that posed the exercise, now with the cause: a table of cause, fix, killing property and failing step for every planted fault, the trace read step by step, and the failing partner that makes each proof evidence. The last lesson holds the reference ledger, the injected defects, and the manifest that prints the single PASS line. All 16 planted faults are covered.

Lesson

After it you can...

Solutions: FIFO Property Set

Name the cause, property and step of the five FIFO faults, and the mutants of the properties no fault reaches.

Solutions: Bridge and the Assumption Trap

Read the three bridge faults, and show which one an input rule hides.

Solutions: Registers and the Property Mutants

Name the three register faults and kill every register property with a mutant.

Solutions: Arbiter Wait Bound

Read the starvation fault at two steps, and show the bound is exact.

Solutions: Pairs and Chain

Prove the reset pairs with their helper assertions and show each failing partner.

Solutions: Pipeline, Twin and ECO

Read the twin fault, the induction windows, and the scoped ECO claim with its partner.

Solutions: Counter and Induction

Name the helper that closes the counter and the cause of its planted fault.

Solutions: Ledger and Final Manifest

Run the reference ledger through the manifest and defend the review answers.

Suggested order: the lessons in stage order, each after its own stage. Compare your table with the table of each lesson before reading the trace: a cause that you wrote differently but that fits the trace is not wrong, but a failing step that differs from the table is worth rerunning.

A failing trace names a failing property. The property points at the cause in the listing. The fix is rerun. A counterexample row in the ledger records that the property kills the fault.
How each solution is built: the failing trace names the property, the property points at the cause in the listing, the fix is rerun, and a counterexample row records the kill.
Check yourself Why do these lessons repeat the proof runs of the stages?

A cause is only a claim until a run shows it: each lesson ends with the failing run at the smallest depth, and the ledger cites exactly those runs.

Related topics

  • Back: Stage 4 Final Manifest and Review

  • Formal Glossary

PreviousNext: Solutions: FIFO Property Set

Up next

Up nextSolutions: FIFO Property Set

Sign in to save progress

Practice this lessonPrevious lessonReport an error

See also

  • The Brief
  • Stage 1: FIFO and Handshake
  • Stage 2: Registers and Arbiter