TEST CORPUS & COMPATIBILITY

QuantumSafe Asset Assurance
QS-AA-2026.07

Connector coverage is network-specific and must declare data-source freshness and finality.

COMPATIBILITY MANIFEST

Every result is bound to an exact version and environment.

DimensionCurrent public statementPublication rule
Input / artifact formatsCSV/XLSX import-export, Wallet signature adapters, Blockchain explorer/API connectorsDeclared in public profile
Runtime / platformProject-specificMust be fixed in the evaluation manifest
Cryptographic profileVersioned project profileNo blanket PQC support claim
Evidence outputJSON/CSV/PDF or product-specific artifactMust include profile ID and test time
Independent assessmentNot published unless explicitly linkedPublication gate remains open

REFERENCE TEST CORPUS

Product-specific acceptance scenarios.

01

Address syntax per network

02

Challenge expiry and replay

03

Signature proof verification

04

Transaction finality handling

05

Screening-source traceability

REQUIRED MANIFEST FIELDS

  • Product and public-profile ID
  • Component, firmware, SDK and API versions
  • Operating system, runtime, browser or appliance version
  • Algorithm/profile identifiers and parameter sets
  • Input corpus checksum and expected result
  • Tester, timestamp, environment and evidence links

KNOWN BOUNDARY

Connector coverage is network-specific and must declare data-source freshness and finality.

No audit-firm validation or sanctions-data certification is published.

CLOSE THE GATE

QuantumSafe Asset Assurance

Run the evaluation pack, publish the manifest and map every support claim to evidence.