How nepet/futhark works
Main Components
a) Core Rune Processing Engine
• Authentication Module (SHA-256)
• Restriction Parser
• Alternative Evaluator
• Encoding/Decoding Module (Base64)
b) External Interfaces
• Input Interface (for creating/deriving runes)
• Verification Interface (for validating runes)
Architectural Flow
a) Rune Creation Flow:
• Secret Input → AuthBase Generation → Restriction Addition → SHA-256 Processing → Base64 Encoding → Final Rune
b) Rune Verification Flow:
• Encoded Rune → Base64 Decoding → Auth Code Verification → Restriction Parsing → Alternative Evaluation → Verification Result
Specific Implementation Details
Project-specific elements:
a) Core Components (based on src/):
• lib.rs (main interface)
• sha256.rs (cryptographic operations)
b) Testing Components:
• test_vectors.csv
• benchmarking modules (from benches/)
Component Relationships
Key relationships:
[Input Interface] → [Restriction Parser] → [SHA-256 Module]
• ↓
[Secret Store] → [AuthBase Generator] → [Authentication Module]
• ↓
[Base64 Encoder/Decoder] ← → [Final Rune Output]
Implementation Notes
• The modular nature of the codebase (separate SHA-256 implementation)
• The benchmark capabilities (shown in benches/)
• The test vector validation system
• The extensibility for future functional checks