Transform any file or text into a unique 128-character "Symph" identifier using quantum-inspired frequency encoding. Data is compressed, optionally encrypted, and stored as offset frequencies that reconstruct back to the original content.
Input Modes
📄 Text Mode
Encode text content directly — notes, messages, articles. Processed through the quantum encoding algorithm and stored as a unique Symph with metadata.
📁 File Mode
Import any file type: documents, images, audio, video, archives, executables. Read in full, processed through frequency analysis, converted to QTE format.
⚡ Direct Binary Mode (.qTb)
For large files that will typically be made public or don't require syllabic encoding, Direct Binary bypasses the QuantumByte syllabic transform entirely. Files are stored as raw binary blobs, making speed limited only by AT Protocol rate limits — orders of magnitude faster than syllabic encoding. Ideal for media, archives, and bulk data.
Metadata Fields
| Field | Purpose | Usage |
|---|
| Title | Human-readable name | Displayed in lists, searching |
| Author | Creator attribution | Ownership, publishing credits |
| Tags | Categorization | Filtering, grouping, search |
| Summary | Brief description | Preview text, overview |
| Password | 11-character key | Protects content, required for decoding |
🔬 Technical Implementation
- Frequency offset calculation algorithms
- 128-character Symph identifiers
.qTe (unprotected) or .qTp (password-protected) offset files.qTb Direct Binary — raw storage, no syllabic encoding, maximum throughput- JSON metadata store for fast retrieval
- Local blockchain registration for integrity tracking
- Optional AT Protocol sync for decentralized storage
💡 Pro Tip: Password protection uses an 11-character key that cryptographically transforms the offset data. Without the exact password, the original content cannot be reconstructed. For large public files where encoding isn't needed, use Direct Binary (.qTb) for dramatically faster upload/download.