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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 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: 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

3 sources
> Yes it is. The more people with coins actively minting in the system, the higher the difficulty of getting chosen. I'm well aware. But eventually a large validator will get chosen--it's not difficult to get chosen, it's rare. The fact that PoS folks call this "difficulty" does not make it so. > If you really want to keep discussing this with me, read through the WHOLE of https://github.com/fresheneesz/validatedProofOfStake and show me a full attack on it. Given your proposed solution is checkpoints from a centralized trusted entity, you're giving up decentralization. Sure, your solution works. If you don't trust the source of the checkpoint, you're back to square one--it no longer works. And if you're willing to give up decentralization, may I suggest you just store all transactions in Postgres? You don't need a blockchain if you're ju
Read the rest
st going to trust a centralized entity. I'm not going to give your design a free audit. If there's some way this isn't centralized, feel free to explain, otherwise, this isn't relevant--I think we can assume that PoS is being discussed in the context of decentralized, trustless models. > If you're not a detractor, than how about just trying to learn instead of insulting the intelligence of people who have actually worked on solutions to these problems? I haven't insulted your intelligence. You're probably a smart guy. Which is probably why you're overconfident in your solution: smart people aren't used to being wrong, so you aren't taking the time to actually grok the attack I've already proposed, or why the only working solution you've actually proposed depends on centralization. I did question your credibility to make claims here, because it's pretty clear you either don't understand the attack proposed by On Stake and Consensus, or you don't understand decentralization, which are both fundamental prerequisites to this discussion. The time constraints defense is literally in the paper, and the checkpoints solution you've proposed is just proof of authority by a different name. If you choose to feel insulted by someone saying you're wrong, that's your prerogative.
In Cryptocurrency Blockchains Don’t Need to Be Energy Intensive
> "Difficulty" isn't a thing in PoS Yes it is. The more people with coins actively minting in the system, the higher the difficulty of getting chosen. Please do more research. If you really want to keep discussing this with me, read through the WHOLE of https://github.com/fresheneesz/validatedProofOfStake and show me a full attack on it. > FWIW, I'm not a PoS detractor. You could have fooled me. But it sounds like you're saying you believe in Vitalik, and anyone else on the internet (ie me) must be idiots who can't understand solutions to these problems. Yet, you're not putting in the effort to understand the solutions out there. PoS protocols are more complex than PoW - there are more edge cases to shore up. So telling me you can "trivially" get around any particular solution ignores the fact that solutions work together. They aren't iso
Read the rest
lated. So slow down and actually try to understand a protocol holistically before attacking it. If you're not a detractor, than how about just trying to learn instead of insulting the intelligence of people who have actually worked on solutions to these problems?
In Cryptocurrency Blockchains Don’t Need to Be Energy Intensive
> 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.