Resources
Additional resources for working with MetaMUI Crypto Primitives.
Documentation
Getting Started
API Documentation
Integration
Technical Resources
Performance
Security
Migration
Code Examples
Basic Operations
# Hashing
from metamui_crypto import SHA256, Blake3
sha_hash = SHA256.hash(b"data")
blake_hash = Blake3.hash(b"data")
# Encryption
from metamui_crypto import ChaCha20Poly1305
key = ChaCha20Poly1305.generate_key()
ciphertext, nonce = ChaCha20Poly1305.encrypt(b"secret", key)
# Signatures
from metamui_crypto import Ed25519
keypair = Ed25519.generate_keypair()
signature = Ed25519.sign(b"message", keypair.private_key)
Advanced Patterns
# Hybrid encryption
from metamui_crypto import MLKem768, ChaCha20Poly1305
def hybrid_encrypt(data: bytes, recipient_public_key: bytes):
# Post-quantum KEM
ciphertext, shared_secret = MLKem768.encapsulate(recipient_public_key)
# Use shared secret for symmetric encryption
encrypted = ChaCha20Poly1305.encrypt(data, shared_secret[:32])
return {
'kem_ciphertext': ciphertext,
'encrypted_data': encrypted
}
Tools and Utilities
Command Line Tools
# Generate keypair
metamui-crypto keygen --algorithm ed25519 --output mykey
# Sign file
metamui-crypto sign --key mykey.priv --file document.pdf
# Encrypt file
metamui-crypto encrypt --algorithm chacha20 --file secret.txt
Development Tools
External Resources
Standards and Specifications
Research Papers
- Kyber: A CCA-secure module-lattice-based KEM
- Dilithium: A lattice-based digital signature scheme
- Falcon: Fast-Fourier lattice-based compact signatures
Community
Frequently Asked Questions
General
Q: Why pure implementations? A: Pure implementations ensure consistent behavior across platforms, eliminate supply chain risks, and make security auditing easier.
Q: Which algorithms should I use? A: For new applications, we recommend:
- Encryption: ChaCha20-Poly1305
- Signatures: Ed25519 (or Dilithium for post-quantum)
- Hashing: Blake3
- Key Exchange: X25519 + ML-KEM-768 (hybrid)
Security
Q: Are the implementations constant-time? A: Yes, all secret-dependent operations are implemented using constant-time algorithms to prevent timing attacks.
Q: How is memory cleared? A: Sensitive data is automatically cleared using platform-specific secure clearing functions.
Performance
Q: How does performance compare to native libraries? A: Our pure implementations are optimized and typically achieve 70-90% of native library performance, with some algorithms matching or exceeding native performance.
Compatibility
Q: Can I use this with existing systems? A: Yes, all algorithms follow standard specifications and are compatible with other compliant implementations.
Support
Commercial Support
For enterprise support, custom implementations, or licensing inquiries:
- Email: license@metamui.id
- Website: sovereignwallet.network
Community Support
License
MetaMUI Crypto Primitives is dual-licensed:
- BSL 1.1: For open source use
- Commercial License: For proprietary applications
See LICENSE for details.