h128.
A whole world.
A pocket-sized key.
Your film. Your archive. Your next big idea.
Keep a tiny key. Come back for the whole thing.
Your whole library.
Room left in your pocket.
A film. An archive.
A thousand small discoveries.
Fits in a message.
Fits in a margin.
Hand the key to your store.
Get the exact original back.
The original stays in a store you trust. The key identifies it; the store keeps it available.
All of this.
One little key.
A whole article. A file from your desktop.
Something too big for a message. A key that fits.
Any file type. It stays on your device.
Enable JavaScript to calculate your own key.
Fits in a message.
Points to the exact original.
This demo only makes the key. Keep the original in a store to retrieve it later. Nothing is uploaded.
One letter.
A different universe.
h128-2cf24dba5fb0a30e26e83b2ac5b9e29eh128-185f8db32271fe25f561a6fc938b2e26Leave the weight.
Take the key.
Send a film without attaching the film.
Share the key with someone who can access its store.
h128 put hello.txt
h128 get h128-2cf24dba5fb0a30e26e83b2ac5b9e29eWith the h128 CLI configured for your own authorized store. Put returns a hash; get retrieves and verifies the exact bytes.
Curious how the key works?
Small enough to fit in a prompt.
id = "h128-" + sha256(bytes).hex()[:32]
format = h128-[0-9a-f]{32}
read = GET /<id> from your own CAS
write = PUT /<id> with raw bytes to your own CASA store verifies the hash before accepting bytes. Authentication and retention belong to the store. A 128-bit digest has about 64 bits of generic collision resistance; use full SHA-256 when stronger collision protection is required.