HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
pickhardt
escrovery
JavaScript2019–2019
pickhardt / escrovery

escrovery

Escrovery - Decentralized Account Recovery With Escrowed Payments

Finance & Commerce
Explore on GitHubRead Hacker News discussions
2Distinct people
3Mentions
0Explicit recommenders
13GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Escrovery - Decentralized Account Recovery With Escrowed Payments

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 hour3 dated mentions

Observed mentions: 2019-07-09 18:24:20 UTC to 2019-07-10 19:33:50 UTC.

012019-07-09 18:00:00 UTC to 2019-07-09 19:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJul 9, 18:002019-07-09 19:00:00 UTC to 2019-07-09 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-09 20:00:00 UTC to 2019-07-09 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-09 21:00:00 UTC to 2019-07-09 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-09 22:00:00 UTC to 2019-07-09 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-09 23:00:00 UTC to 2019-07-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 00:00:00 UTC to 2019-07-10 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 01:00:00 UTC to 2019-07-10 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 02:00:00 UTC to 2019-07-10 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 03:00:00 UTC to 2019-07-10 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 04:00:00 UTC to 2019-07-10 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 05:00:00 UTC to 2019-07-10 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 06:00:00 UTC to 2019-07-10 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 10, 06:002019-07-10 07:00:00 UTC to 2019-07-10 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 08:00:00 UTC to 2019-07-10 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 09:00:00 UTC to 2019-07-10 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 10:00:00 UTC to 2019-07-10 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 11:00:00 UTC to 2019-07-10 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 12:00:00 UTC to 2019-07-10 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 13:00:00 UTC to 2019-07-10 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 14:00:00 UTC to 2019-07-10 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 15:00:00 UTC to 2019-07-10 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 16:00:00 UTC to 2019-07-10 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 17:00:00 UTC to 2019-07-10 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-10 18:00:00 UTC to 2019-07-10 19:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2019-07-10 19:00:00 UTC to 2019-07-10 20:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 10, 19:00

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
Jul 9, 18:002019-07-09 18:00:00 UTC2019-07-09 19:00:00 UTC110
Jul 9, 19:002019-07-09 19:00:00 UTC2019-07-09 20:00:00 UTC000
Jul 9, 20:002019-07-09 20:00:00 UTC2019-07-09 21:00:00 UTC000
Jul 9, 21:002019-07-09 21:00:00 UTC2019-07-09 22:00:00 UTC000
Jul 9, 22:002019-07-09 22:00:00 UTC2019-07-09 23:00:00 UTC000
Jul 9, 23:002019-07-09 23:00:00 UTC2019-07-10 00:00:00 UTC000
Jul 10, 00:002019-07-10 00:00:00 UTC2019-07-10 01:00:00 UTC000
Jul 10, 01:002019-07-10 01:00:00 UTC2019-07-10 02:00:00 UTC000
Jul 10, 02:002019-07-10 02:00:00 UTC2019-07-10 03:00:00 UTC000
Jul 10, 03:002019-07-10 03:00:00 UTC2019-07-10 04:00:00 UTC000
Jul 10, 04:002019-07-10 04:00:00 UTC2019-07-10 05:00:00 UTC000
Jul 10, 05:002019-07-10 05:00:00 UTC2019-07-10 06:00:00 UTC000
Jul 10, 06:002019-07-10 06:00:00 UTC2019-07-10 07:00:00 UTC000
Jul 10, 07:002019-07-10 07:00:00 UTC2019-07-10 08:00:00 UTC000
Jul 10, 08:002019-07-10 08:00:00 UTC2019-07-10 09:00:00 UTC000
Jul 10, 09:002019-07-10 09:00:00 UTC2019-07-10 10:00:00 UTC000
Jul 10, 10:002019-07-10 10:00:00 UTC2019-07-10 11:00:00 UTC000
Jul 10, 11:002019-07-10 11:00:00 UTC2019-07-10 12:00:00 UTC000
Jul 10, 12:002019-07-10 12:00:00 UTC2019-07-10 13:00:00 UTC000
Jul 10, 13:002019-07-10 13:00:00 UTC2019-07-10 14:00:00 UTC000
Jul 10, 14:002019-07-10 14:00:00 UTC2019-07-10 15:00:00 UTC000
Jul 10, 15:002019-07-10 15:00:00 UTC2019-07-10 16:00:00 UTC000
Jul 10, 16:002019-07-10 16:00:00 UTC2019-07-10 17:00:00 UTC000
Jul 10, 17:002019-07-10 17:00:00 UTC2019-07-10 18:00:00 UTC000
Jul 10, 18:002019-07-10 18:00:00 UTC2019-07-10 19:00:00 UTC110
Jul 10, 19:002019-07-10 19:00:00 UTC2019-07-10 20:00:00 UTC101

What Hacker News says

3 sources
jrpt·Jul 10, 2019Submission

Tell HN: I came up with an interesting way to do decentralized account recovery

Thought I'd share this with the HN community. Link to the Escrovery paper: https://github.com/pickhardt/escrovery/blob/master/escrovery... I came up with an interesting way to do totally decentralized account recovery. Why might this be useful? Suppose you have some account on Bitcoin, Ethereum, etc and you lose your secret key. Worse, you also lose (or never had) any way to recover it. Escrovery gives you a way to recover it, and without simply using a centralized service like Coinbase or needing secret shares from k of n friends. This could also be used as a recovery method with self-sovereign identities. The way it works it using escrowed payments to deter malicious recovery attempts. Any user may make an Escrovery challenge to recover any account by first placing an amount of money in escrow. If the original account owner responds to
Read the rest
the challenge in a certain amount of time, they earn the escrow. Otherwise, the challenger takes ownership of the account and recovers their escrow. The main limitation is that it requires users to be regularly active in checking for challenges to their account. For some use cases, this would be fine. For others, perhaps it wouldn't work.
131 points · Open discussion

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.