Meaning
Memory usage profile for the volatile and non-volatile storage required to store keys and execute signing operations of a specific hash-based signature scheme. The sphincs+ memory footprint determines if a post-quantum algorithm can run on resource-constrained devices like smart cards or embedded sensors. It includes space for the secret key, the public key, the auxiliary randomness and the temporary workspace.
Static Requirement
Key sizes for this algorithm are notably larger than those used in traditional digital signatures. A sphincs+ memory footprint must accommodate public keys that often reach several kilobytes. Storing these keys in permanent memory reduces the available space for other application code.
Runtime Allocation
Generating a signature requires the creation of many intermediate hash values. The sphincs+ memory footprint expands during these calculations as the processor traverses the multi-level tree structure. Testing the peak usage during a prototype run ensures that the system does not crash from a stack overflow under production loads.
Efficiency here is mandatory.
Optimization Tradeoff
Reducing the memory usage often leads to slower execution speeds as the system recomputes values. Balancing the sphincs+ memory footprint against the signing time is a difficult task for systems integration. Verification of the demonstrated rate in a laboratory setting confirms if the algorithm fits within the hardware capacity of the final product.