Compile-time random netlist constant
ConceptIn the OpenTitan signoff checklist, compile-time random netlist constants are security countermeasure values such as LFSR seeds or scrambling constants that are baked into a block's generated netlist at compile/synthesis time rather than held in programmable software-visible state.
First seen 7/16/2026
Last seen 7/16/2026
Evidence 1 chunks
Wiki v1
WIKI
Compile-time random netlist constant
In OpenTitan's D2S signoff checklist, compile-time random netlist constants are listed as one of the standardized security countermeasures that must be implemented. They are values such as LFSR seeds or scrambling constants that are baked into the synthesized netlist so that they are fixed at hardware build time and not visible or controllable at runtime via software.
Mechanism in OpenTitan
NEIGHBORHOOD
No graph connections found for this entity yet. It may appear in future ingestion runs.
explore full graph →RELATIONSHIPS
1 connectionsLFSR seeds are examples of compile-time random netlist constants.
LINKED ENTITIES
1 linksCITATIONS
4 sources4 citations — click to collapse
[1] Compile-time random netlist constants are a security countermeasure category in the OpenTitan signoff checklist. Signoff Checklist - OpenTitan Documentation
[2] Examples of compile-time random netlist constants include LFSR seeds and scrambling constants. Signoff Checklist - OpenTitan Documentation
[3] Compile-time random netlist constants are exposed to topgen via the randtype parameter mechanism in the comportable IP Hjson file. Signoff Checklist - OpenTitan Documentation
[4] Default random seeds and permutations for LFSRs can be generated with the gen-lfsr-seed.py script. Signoff Checklist - OpenTitan Documentation