Address syntax per network
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.
| Dimension | Current public statement | Publication rule |
|---|---|---|
| Input / artifact formats | CSV/XLSX import-export, Wallet signature adapters, Blockchain explorer/API connectors | Declared in public profile |
| Runtime / platform | Project-specific | Must be fixed in the evaluation manifest |
| Cryptographic profile | Versioned project profile | No blanket PQC support claim |
| Evidence output | JSON/CSV/PDF or product-specific artifact | Must include profile ID and test time |
| Independent assessment | Not published unless explicitly linked | Publication gate remains open |
REFERENCE TEST CORPUS
Product-specific acceptance scenarios.
Challenge expiry and replay
Signature proof verification
Transaction finality handling
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.
