HN Showcase
Back to browse
GitHub Repository

High-performance, streaming-first container format with per-block codec polymorphism and robust data recoverability. Reference implementation in Rust.

29 starsRust

6cy v0.3.0 – A streaming-first binary archive format

by yihac1·Feb 20, 2026·1 point·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidBig BrainNiche GemWizardry

Self-describing archive blocks with mandatory CRC32 and no fallback tricks.

Strengths
  • •Purposeful constraints eliminate silent corruption and ambiguity entirely — corruption fails loudly.
  • •UUID-primary codec identity and forward-scannable format enable partial recovery and plugin safety.
  • •Thoughtful v0.3.0 redesign (84-byte headers, explicit block types) shows serious iteration discipline.
Weaknesses
  • •Early-stage project (v0.3.0) with niche use case; adoption unknown, no production track record.
  • •Solves a specific problem (corruption safety) that existing formats partially address; unclear real-world win over ZIP/TAR.
Target Audience

Systems engineers, archival tools developers, storage engineers

Similar To

ZIP · TAR · 7z

Post Description

Hi HN — I made this.

Been messing around with a small archive format called 6cy. Not trying to replace zip or anything, mostly just exploring what happens if you make the format a lot stricter.

Every block describes itself. Checksums are always there. Codecs are UUIDs. If decoding can’t proceed cleanly, it just errors out. No fallback tricks.

The whole point was to avoid ambiguity and make corruption obvious instead of silent.

It’s still rough and evolving. Happy to hear thoughts.

Similar Projects