Four cryptographic curves engineered for maximum security — including Post-Quantum resistance. Ready today, protected tomorrow.
Each transaction chooses its own curve. The security level follows the use case — not a one-size-fits-all compromise.
Fastest signature verification in production — 3x faster than secp256k1. EdDSA with 128-bit security. The default curve for all ATSHI operations.
Default · SpeedThe Ethereum/Bitcoin curve. Native MetaMask signing, EVM wallet compatibility, and seamless cross-chain operations via the JSON-RPC gateway.
EVM · BitcoinRequired by FIDO2/WebAuthn and W3C DID. Native to Apple Secure Enclave and Android Keystore. Passwordless authentication and mobile identity.
WebAuthn · MobileNIST FIPS 206 post-quantum standard. Lattice-based signatures resistant to quantum computers. Compact signatures, future-proof by design.
Post-QuantumSignature aggregation — combine thousands of signatures into one. Essential for zkBridge zero-knowledge proofs and Ethereum 2.0 compatibility.
zkBridge · Aggregation192-bit security level required by eIDAS 2.0 qualified signatures, NATO, and high-assurance government systems. The highest classical security tier.
eIDAS 2.0 · EnterpriseEach transaction can use a different curve. The Keychain derives the right key for the right use case automatically.
On Ethereum or Bitcoin, everything uses the same curve. On ATSHI, each transaction chooses its own curve based on its use case. A payment uses Ed25519 for speed. A WebAuthn login uses P-256 for mobile compatibility. A bridge operation uses secp256k1 for EVM compatibility. An eIDAS signature uses P-384 for regulatory compliance. A cross-chain proof uses BLS12-381 for aggregation. A long-term secret uses Falcon-512 for quantum resistance. Six curves, one keychain, zero compromise.
Ed25519 — fast verification for high-frequency sensor data and lightweight devices.
P-256 — native to Apple Secure Enclave, Android Keystore, FIDO2 passwordless auth.
secp256k1 — MetaMask, Ethereum, Bitcoin compatibility. BLS12-381 for zkBridge aggregation.
P-384 for eIDAS 2.0 qualified signatures. Falcon-512 for post-quantum protection.
Every identity on ATSHI has its own Transaction Chain. Each transaction within that chain can use a different curve. The Keychain derives service-specific keys with the right curve via the derivation path. The curve follows the data criticality, not the other way around.
| Feature | Ethereum | Solana | QAN Platform | ATSHI |
|---|---|---|---|---|
| Curves available | 1 (secp256k1) | 1 (Ed25519) | 1 (CRYSTALS-Dilithium) | 6 curves |
| Post-quantum | No | No | Yes (Dilithium) | Yes (Falcon-512) |
| Multi-curve | No | No | No | Yes — per chain |
| Curve per service | No | No | No | Yes (TC + Keychain) |
| FIPS compliant | No | No | No | Yes (NIST P256) |
| Adaptive security | No — same curve for all | No — same curve for all | No — PQ only | Yes — criticality-based |
Four curves, one keychain. Choose the right cryptography for compliance, compatibility, or post-quantum resistance.