AIMer Security API
Side-channel claim limit. Nothing on this page claims constant-time behaviour or side-channel resistance for any target: the side-channel harness covers nothing (finding A48) and no measurement exists. The Rust and C cores are designed for constant time and unmeasured; managed runtimes (JIT, GC, bounds checks) make no timing claim. Where this page names constant-time or side-channel techniques, in prose or in code, they are design intent or recommendations, not measured properties.
Version: 1.0.0
Last Updated: 2025-01-02
Security Classification: MPC-based Signature
Author: MetaMUI Security Team
Overview
AIMer is a Korean signature scheme based on MPC-in-the-head paradigm, offering quantum resistance through symmetric primitives.
- Algorithm Family: MPC-in-the-head signature
- Security Levels:
- 128f: 128-bit (fast variant)
- 192f: 192-bit (fast variant)
- 256f: 256-bit (fast variant)
- Origin: Korean Post-Quantum Cryptography Competition
Security Warnings ⚠️
- MPC-based: Uses multiparty computation techniques
- Symmetric Primitives: Security based on AES
- Large Signatures: Larger than lattice-based schemes
- Simple Implementation: Easier to implement securely
API Functions
Standard signature API with MPC-based construction.
Security Analysis
Threat Model: AIMer Threat Model
The comprehensive threat analysis covers:
- Algorithm-specific attack vectors
- Implementation vulnerabilities
- Side-channel considerations
- Quantum resistance analysis (where applicable)
- Deployment recommendations
For complete security analysis and risk assessment, see the dedicated threat model documentation.