QNSP
Start building free
Why QNSP
The Quantum ImperativeWhy QNSPPQC Migration GuideCompetitive AnalysisVet PQC Vendors
Platform
Platform ArchitectureCapabilitiesUse Cases by IndustryKnowledge BaseBlogResearch
Trust
Trust HubCompliance MappingNIST ACVP ConformancePerformance BenchmarksEntropy ChainAlgorithm CatalogSystem Status
Developers
Developer HubUse CasesAI Assistants (MCP)
PricingContactStart building free

Key Encapsulation

BIKE

Bit Flipping Key Encapsulation

non-FIPScode-based3 parameter setsQNSP tier: default+provider: liboqsalso called: Bit-Flipping KEM
Code-based KEM finalist (round 4 of NIST PQC standardisation) using QC-MDPC codes. Available in liboqs for QNSP customers seeking additional code-based alternatives.

Mechanism

How it works

BIKE uses Quasi-Cyclic Moderate Density Parity Check (QC-MDPC) codes. Decryption involves iterative bit-flipping decoders. Three parameter sets target NIST security categories 1, 3, and 5.

Parameter Sets

3 variants shipped

Each variant trades security category against key, ciphertext, or signature size. QNSP exposes all variants via the @cuilabs/liboqs-native binding; tenant crypto-policy determines which are allowed.

VariantNIST LevelPublic KeySecret KeyCiphertextNote
BIKE-L1L11,541 B5,223 B1,573 B
BIKE-L3L33,083 B10,105 B3,115 B
BIKE-L5L55,122 B16,494 B5,154 B

NIST ACVP

Conformance evidence

QNSP runs the official NIST ACVP test vectors against every shipped algorithm. Live evidence + SHA-3-256 tamper digest at /verify/conformance.

@noble/post-quantum
non-addressable
Pure-JavaScript reference; cross-verification secondary on Maximum + Government tiers.
@cuilabs/liboqs-native
non-addressable
Native-C primary production engine. Runs across every QNSP backend service.
Not selected for FIPS standardisation; no NIST ACVP vectors.
View live ACVP evidence →

Use Cases

When to use it

  • Customer workloads requiring code-based alternatives beyond HQC
  • Research and migration analysis

Trade-offs

What you give up, what you get

  • Secret keys are larger than HQC at equivalent security levels
  • Not on the NIST PQC standardisation path — defer to HQC unless specific needs

FAQ

BIKE — frequently asked questions

Concise, source-of-truth answers to the questions buyers and engineers ask most about this algorithm.

What is BIKE?

BIKE (Bit Flipping Key Encapsulation) is a code based post-quantum key encapsulation mechanism. It is designed to resist attacks from both classical and quantum computers, and QNSP ships 3 of its parameter sets. It is also known as Bit-Flipping KEM.

Is BIKE NIST-standardized?

BIKE is not a finalized NIST FIPS standard. QNSP ships it as a non-FIPS post-quantum option, typically to add an independent cryptographic assumption (code based) alongside the FIPS-standardized ML-KEM and ML-DSA for defence-in-depth.

What is BIKE used for?

On QNSP, BIKE is used for Customer workloads requiring code-based alternatives beyond HQC; Research and migration analysis. It is available from the default crypto-policy tier upward via the liboqs provider.

References

Primary sources