HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
fresheneesz
ValidatedProofOfStake
JavaScript2021–2021
fresheneesz / ValidatedProofOfStake

ValidatedProofOfStake

A pure proof of stake cryptocurrency consensus protocol that uses block validators and minter punishments without lock-in stake.

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

What to know before exploring

What it is

A pure proof of stake cryptocurrency consensus protocol that uses block validators and minter punishments without lock-in stake.

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:56:33 AM 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: 2021-07-06 01:58:33 UTC to 2021-07-06 20:31:10 UTC.

012021-07-06 01:00:00 UTC to 2021-07-06 02:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 6, 01:002021-07-06 02:00:00 UTC to 2021-07-06 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-06 03:00:00 UTC to 2021-07-06 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-06 04:00:00 UTC to 2021-07-06 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-06 05:00:00 UTC to 2021-07-06 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-06 06:00:00 UTC to 2021-07-06 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-06 07:00:00 UTC to 2021-07-06 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-06 08:00:00 UTC to 2021-07-06 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-06 09:00:00 UTC to 2021-07-06 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-06 10:00:00 UTC to 2021-07-06 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 6, 10:002021-07-06 11:00:00 UTC to 2021-07-06 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-06 12:00:00 UTC to 2021-07-06 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-06 13:00:00 UTC to 2021-07-06 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-06 14:00:00 UTC to 2021-07-06 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-06 15:00:00 UTC to 2021-07-06 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-06 16:00:00 UTC to 2021-07-06 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-06 17:00:00 UTC to 2021-07-06 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-06 18:00:00 UTC to 2021-07-06 19:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-07-06 19:00:00 UTC to 2021-07-06 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-06 20:00:00 UTC to 2021-07-06 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 6, 20: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 6, 01:002021-07-06 01:00:00 UTC2021-07-06 02:00:00 UTC101
Jul 6, 02:002021-07-06 02:00:00 UTC2021-07-06 03:00:00 UTC000
Jul 6, 03:002021-07-06 03:00:00 UTC2021-07-06 04:00:00 UTC000
Jul 6, 04:002021-07-06 04:00:00 UTC2021-07-06 05:00:00 UTC000
Jul 6, 05:002021-07-06 05:00:00 UTC2021-07-06 06:00:00 UTC000
Jul 6, 06:002021-07-06 06:00:00 UTC2021-07-06 07:00:00 UTC000
Jul 6, 07:002021-07-06 07:00:00 UTC2021-07-06 08:00:00 UTC000
Jul 6, 08:002021-07-06 08:00:00 UTC2021-07-06 09:00:00 UTC000
Jul 6, 09:002021-07-06 09:00:00 UTC2021-07-06 10:00:00 UTC000
Jul 6, 10:002021-07-06 10:00:00 UTC2021-07-06 11:00:00 UTC000
Jul 6, 11:002021-07-06 11:00:00 UTC2021-07-06 12:00:00 UTC000
Jul 6, 12:002021-07-06 12:00:00 UTC2021-07-06 13:00:00 UTC000
Jul 6, 13:002021-07-06 13:00:00 UTC2021-07-06 14:00:00 UTC000
Jul 6, 14:002021-07-06 14:00:00 UTC2021-07-06 15:00:00 UTC000
Jul 6, 15:002021-07-06 15:00:00 UTC2021-07-06 16:00:00 UTC000
Jul 6, 16:002021-07-06 16:00:00 UTC2021-07-06 17:00:00 UTC000
Jul 6, 17:002021-07-06 17:00:00 UTC2021-07-06 18:00:00 UTC000
Jul 6, 18:002021-07-06 18:00:00 UTC2021-07-06 19:00:00 UTC101
Jul 6, 19:002021-07-06 19:00:00 UTC2021-07-06 20:00:00 UTC000
Jul 6, 20:002021-07-06 20:00:00 UTC2021-07-06 21:00:00 UTC101

What Hacker News says

1 sources
> The fork starts from before the unstaking transaction. So what? The fork wouldn't be built on by anyone but the attacker. Any new entrant would have software that expects a blockchain being built substantially faster (or with substantially higher difficulty). > you wouldn't have to reason it out if you had read the paper I linked. I have read Peolstra's "pos.pdf" that PoS detractors incessently reference multiple times. The paper's conclusion is not correct. All the problems he presents are solvable at once (eg in this protocol: https://github.com/fresheneesz/validatedProofOfStake). He doesn't consider that hard coded checkpoints handily solve the problem of long-range revisions.
In Cryptocurrency Blockchains Don’t Need to Be Energy Intensive

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.