Signature-size model
TEST CORPUS & COMPATIBILITY
QuantumSafe Web3 Migration Lab
QS-W3-2026.07
Chain-specific assumptions must be supplied and reviewed; no universal runtime claim.
COMPATIBILITY MANIFEST
Every result is bound to an exact version and environment.
| Dimension | Current public statement | Publication rule |
|---|---|---|
| Input / artifact formats | JSON profile catalogue, Transaction calculator, Contract-analysis manifest | 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.
Fee and throughput sensitivity
Wallet/address coexistence
Verifier success/failure vectors
Activation and rollback scenario
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
Chain-specific assumptions must be supplied and reviewed; no universal runtime claim.
Research output is not a production blockchain security assessment.
CLOSE THE GATE
QuantumSafe Web3 Migration Lab
Run the evaluation pack, publish the manifest and map every support claim to evidence.
