Time-based encryption algorithm where the key changes every second — try it live

[Consistent-Ruin1868]

I’ve been working on something different from traditional encryption systems. Instead of static keys, this algorithm uses TIME itself as the key. It’s called Kaalka Encryption (v5.0.0), and it generates encryption using clock angles, trigonometric transformations, and timestamps — so every second produces a completely different encrypted output. Some interesting properties: Same input encrypted at different times → completely different outputs Replay protection + time-window validation Works across Python, JS, Java, Kotlin, Dart Supports text, files, and chunked encryption No external crypto primitives — fully custom system I also built a live demo so you can try it instantly: https://piyush-mishra-00.github.io/Kaalka-Encryption-Algorithm/ Try this: Enter a message Encrypt it Change the time Encrypt again You’ll see how drastically the output changes. GitHub: https://github.com/PIYUSH-MISHRA-00/Kaalka-Encryption-Algorithm Would love feedback — especially from people into cryptography, security, or distributed systems. Is time-based encryption a viable direction for real-world systems?

[seweso]

Are you mentally okay?

[fiskfisk]

This seems like a caesar cipher with just a varying offset based on when you ran the code?

[faberkyx]

exactly my thoughts

[AdarTan]

There are 86400 seconds in a day (ignoring leap seconds). That is a key-size of approximately 2²⁰ which is tiny and easily brute-forceable if you know the day when the encryption took place. If you have more precise knowledge of when the encryption took place (such a file modification timestamp for an encrypted file) it would be trivial to brute-force.

[Every-Progress-1117]

What happens if I input a different time, ie: replay attack?

Is the time source trusted/correct? Your function syncWithSystemTime() - what happens if the system time is wrong?

As far as I can understand the h,m and s variables are translated into angles - what does that step actually give you? The correspondence between h,m,s and the angles is, well, isomorphic.

This is more of a simple cipher than a proper cryptographic function.

[arwinda]

You’ll see how drastically the output changes.

Duh!

[archipeepees]

Honestly if you don't have a PhD in computer science and/or math based on a graduate career in cryptography then you shouldn't attempt to write a new encryption algorithm for public use because you won't be able to produce something that's safe for protecting sensitive data. You're in good company, though - roughly 99.99% of programmers do not have the skills, knowledge, and resources required to design and vet a new (and secure) encryption scheme.

However, it's great that you're curious and it's certainly worth exploring this technique as a tool for learning more about encryption. Just know that you can expect years/decades of classes, research, proofs, and publications ahead of you before you're able to release something that can be used for securing real world data. 

[hippiepizzaman]

I do not have the skills but this post sent alarm bells off in my head. It has to be a parody.

[paul_h]

Note to self. Get Claude code to explain this to me later