HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
rayanamal
timelock
C2025–2025
rayanamal / timelock

timelock

An implementation of time-lock puzzle, a decryption algorithm which prevents decryption of data until a certain amount of time passes

2Distinct people
3Mentions
0Explicit recommenders
7GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An implementation of time-lock puzzle, a decryption algorithm which prevents decryption of data until a certain amount of time passes

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week3 dated mentions

Observed mentions: 2025-03-08 19:32:31 UTC to 2025-09-10 19:58:27 UTC. Weeks start Monday, UTC.

012025-03-03 00:00:00 UTC to 2025-03-10 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 32025-03-10 00:00:00 UTC to 2025-03-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-17 00:00:00 UTC to 2025-03-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-24 00:00:00 UTC to 2025-03-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-31 00:00:00 UTC to 2025-04-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-07 00:00:00 UTC to 2025-04-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-14 00:00:00 UTC to 2025-04-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-21 00:00:00 UTC to 2025-04-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-28 00:00:00 UTC to 2025-05-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-05 00:00:00 UTC to 2025-05-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-12 00:00:00 UTC to 2025-05-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-19 00:00:00 UTC to 2025-05-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-26 00:00:00 UTC to 2025-06-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-02 00:00:00 UTC to 2025-06-09 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 22025-06-09 00:00:00 UTC to 2025-06-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-16 00:00:00 UTC to 2025-06-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-23 00:00:00 UTC to 2025-06-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-30 00:00:00 UTC to 2025-07-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-07 00:00:00 UTC to 2025-07-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-14 00:00:00 UTC to 2025-07-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-21 00:00:00 UTC to 2025-07-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-28 00:00:00 UTC to 2025-08-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-04 00:00:00 UTC to 2025-08-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-11 00:00:00 UTC to 2025-08-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-18 00:00:00 UTC to 2025-08-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-25 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-01 00:00:00 UTC to 2025-09-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-08 00:00:00 UTC to 2025-09-15 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 8

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 32025-03-03 00:00:00 UTC2025-03-10 00:00:00 UTC101
Mar 102025-03-10 00:00:00 UTC2025-03-17 00:00:00 UTC000
Mar 172025-03-17 00:00:00 UTC2025-03-24 00:00:00 UTC000
Mar 242025-03-24 00:00:00 UTC2025-03-31 00:00:00 UTC000
Mar 312025-03-31 00:00:00 UTC2025-04-07 00:00:00 UTC000
Apr 72025-04-07 00:00:00 UTC2025-04-14 00:00:00 UTC000
Apr 142025-04-14 00:00:00 UTC2025-04-21 00:00:00 UTC000
Apr 212025-04-21 00:00:00 UTC2025-04-28 00:00:00 UTC000
Apr 282025-04-28 00:00:00 UTC2025-05-05 00:00:00 UTC000
May 52025-05-05 00:00:00 UTC2025-05-12 00:00:00 UTC000
May 122025-05-12 00:00:00 UTC2025-05-19 00:00:00 UTC000
May 192025-05-19 00:00:00 UTC2025-05-26 00:00:00 UTC000
May 262025-05-26 00:00:00 UTC2025-06-02 00:00:00 UTC000
Jun 22025-06-02 00:00:00 UTC2025-06-09 00:00:00 UTC101
Jun 92025-06-09 00:00:00 UTC2025-06-16 00:00:00 UTC000
Jun 162025-06-16 00:00:00 UTC2025-06-23 00:00:00 UTC000
Jun 232025-06-23 00:00:00 UTC2025-06-30 00:00:00 UTC000
Jun 302025-06-30 00:00:00 UTC2025-07-07 00:00:00 UTC000
Jul 72025-07-07 00:00:00 UTC2025-07-14 00:00:00 UTC000
Jul 142025-07-14 00:00:00 UTC2025-07-21 00:00:00 UTC000
Jul 212025-07-21 00:00:00 UTC2025-07-28 00:00:00 UTC000
Jul 282025-07-28 00:00:00 UTC2025-08-04 00:00:00 UTC000
Aug 42025-08-04 00:00:00 UTC2025-08-11 00:00:00 UTC000
Aug 112025-08-11 00:00:00 UTC2025-08-18 00:00:00 UTC000
Aug 182025-08-18 00:00:00 UTC2025-08-25 00:00:00 UTC000
Aug 252025-08-25 00:00:00 UTC2025-09-01 00:00:00 UTC000
Sep 12025-09-01 00:00:00 UTC2025-09-08 00:00:00 UTC000
Sep 82025-09-08 00:00:00 UTC2025-09-15 00:00:00 UTC101

What Hacker News says

3 sources
There are 2 bypass-free self-restriction (or self-liberation!) solutions for the iPhone. The first is is supervised MDM. If you have a Mac you can do it yourself (though you need to learn iPhone MDM). You can also pay companies like TechLockdown, they'll give you a customized remote-controlled profile to install that is not removable at a weak moment. You can set a lock with delay. When you need to wait 6 hours to change the settings, you won't be changing your settings to allow $ADDICTIVE_APP. The second option is much more complicated and has some caveats, like an inability to update apps, but I'll explain it since nobody seem to know about it. There is a way to turn an iPhone into a dumbphone, while keeping your banking app, without a Mac, for free. Go to Settings > Screen Time: - Set up a PIN for Screen Time. You’ll be asked to provid
Read the rest
e a recovery account. Create another Apple account with a password hard to memorize, like sjhr3762962826. Write that down. - In Content Restrictions > App Store, Media, Web, & Games > Web Content, set it to Only Approved Websites. Add all the websites you need to use in your daily life. Start simple, you'll quickly discover which ones you actually need. I'll let you in on a little secret: You don't need news.ycombinator.com in your pocket. - In Content Restrictions > iTunes & App Store purchases, disallow Installing Apps. - Personally, I also delete all apps that have any sort of infinite online content (even Wikipedia). - Set up Downtime for when you are supposed to be asleep. - Set up Always Allowed for critical apps which you might need even during your usual sleep hours (Health app, WhatsApp, Google Maps, etc.) - Final step: Let a very close person (like family member) change the Screen Time PIN, and let him write it down somewhere safe. Then give the password and the PIN to the person for safekeeping. When you need to change the settings (you want to add another allowed website, you want to install a new app, etc.) ask that person to make the change. There is a way you can not rely on another person, too. I won't detail it here, but it involves timelocking the Apple account's password and the Screen Time PIN. See https://github.com/rayanamal/timelock With this setup, you can’t change the Screen Time settings yourself, and you can’t reset the PIN using “I forgot the PIN” button either.
In Why I Use a Dumbphone in 2025 (and Why You Should Too)
If you are interested in a time-lock implementation you can use today, here is one I made some 5 years ago and still using: https://github.com/rayanamal/timelock - Can time-lock (encrypt) in negligible time (almost instantaneosly) - Non-parallelizable sequential algorithm - Decrypts in constant CPU cycles (meaning CPU with 2x faster clock will decrypt 2x faster) It can only time-lock numeric data though. It's enough for me, I'm using it to encrypt PINs and root passwords for the Screen Time restriction setups of my various devices (iPhone, Linux PC). It allows me to have unbypassable restrictions while also not having to trust a friend/relative. This concept is known as a commitment device: https://en.wikipedia.org/wiki/Commitment_device
In Time-Lock Encryption

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.