evaluation
Evaluate an individual IP configuration
Inspect the named release and establish technical fit.
Discuss this scopeSecurity & trust
Garmo-PUF-Core
Security — multi-source silicon PUF root-key subsystem
Evaluation package
GarSecurity & trust
THE TECHNICAL ROLE
A clear integration boundary.
Garmo-PUF-Core integration role: Security — multi-source silicon PUF root-key subsystem. Documented composition: SRAM/RO/bistable PUF source abstraction; at least two physically independent sources; Enrollment helper data with BCH/LDPC-style fuzzy extractor boundary; Aging/temperature compensation and confidence scoring.
01
SRAM/RO/bistable PUF source abstraction
02
at least two physically independent sources
03
Enrollment helper data with BCH/LDPC-style fuzzy extractor boundary
04
Aging/temperature compensation and confidence scoring
TECHNICAL OVERVIEW
Download the product briefThe details matter.
- Canonical identity
- IP-2081
- Responsibility
- Security — multi-source silicon PUF root-key subsystem
- Documented interface architecture
- PUF hard-macro sample bus, CSR, key-ladder output, lifecycle/zeroize
- Documented building blocks
- SRAM/RO/bistable PUF source abstraction; at least two physically independent sources; Enrollment helper data with BCH/LDPC-style fuzzy extractor boundary; Aging/temperature compensation and confidence scoring
- Delivery boundary
- Evaluation / IP scope
- Evidence scope
- Evaluation package
- Architecture targets · not measurements
- 256-bit derived root key; <1e-6 reconstruction failure target after ECC; zero stored root secret.
Evaluation packageKnow the release.
Know the release.
Know what it establishes.
Canonical technology and its architecture/integration role are recorded. The offered delivery is confirmed against the exact release before licensing.
Source basis: Bible v7.42 IP-2081. This is a controlled-portfolio summary, not a fresh execution of the chip qualification flow.
Release-specific qualification
Physical entropy, uniqueness and stability require measured silicon characterization.
Canonical record: P3 / REPRESENTATIVE ARCHITECTURE RTL — concrete integration specification and synthesizable RTL shell/representative datapath only; all frequency, throughput, power, area, jitter and standards-superiority figures remain architecture targets until the required evidence hierarchy closes. Analog/custom production claims require transistor-level/custom-layout, extracted PVT/Monte-Carlo and silicon characterization.
A PATH THAT FITS THE PROJECT
Build with Garmo-PUF-Core.
Technical scope, rights, support and release configuration are agreed before delivery.
production
Named-design production license
Agree deployment or design rights, deliverables and support.
Discuss this scopecustom
Node binding or derivative integration
Define the customer-specific work and acceptance criteria.
Discuss this scopeKeep exploring.
Security & trust
KENBE Authority Guard
Checks memory request domain/authority permissions.
RTL + modelsIP-4017 · Source / reference evidence
Security & trust
KENBE Certified-Crypto Boundary
Boundary/control contract to qualified encryption/authentication macros without toy cryptography.
RTL + modelsIP-4018 · Source / reference evidence
Security & trust
KENBE Epoch / Version Guard
Rejects stale epoch/version operations under the KENBE transaction contract.
RTL + modelsIP-4019 · Source / reference evidence
Your next big idea.
Let’s build it together.
Start with a chip, a software release or a single IP block.
CANONICAL EVIDENCE RECORD · IP-2081How evidence priority is determined ↗
Source documented
A concrete source or implementation record exists; the selected evidence does not establish complete qualification.
Source: Bible 7.42 VERIFIED V29 · Bible v7.42 IP-2081.
Record integrity and qualification boundary
Retained exact-release source reference; no new table locator was inferred.
Evidence ranking for evaluation prioritization; not a probability or certification.