HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
firoorg
firo
C++2017–2017
firoorg / firo

firo

The privacy-focused cryptocurrency

9Distinct people
10Mentions
0Explicit recommenders
807GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The privacy-focused cryptocurrency

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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 5:03:38 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 day10 dated mentions

Observed mentions: 2017-02-17 22:48:14 UTC to 2017-03-07 09:42:18 UTC.

0123452017-02-17 00:00:00 UTC to 2017-02-18 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsFeb 172017-02-18 00:00:00 UTC to 2017-02-19 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2017-02-19 00:00:00 UTC to 2017-02-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-20 00:00:00 UTC to 2017-02-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-21 00:00:00 UTC to 2017-02-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-22 00:00:00 UTC to 2017-02-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-23 00:00:00 UTC to 2017-02-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-24 00:00:00 UTC to 2017-02-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-25 00:00:00 UTC to 2017-02-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-26 00:00:00 UTC to 2017-02-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 262017-02-27 00:00:00 UTC to 2017-02-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-28 00:00:00 UTC to 2017-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-03-01 00:00:00 UTC to 2017-03-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-03-02 00:00:00 UTC to 2017-03-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-03-03 00:00:00 UTC to 2017-03-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-03-04 00:00:00 UTC to 2017-03-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-03-05 00:00:00 UTC to 2017-03-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-03-06 00:00:00 UTC to 2017-03-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-03-07 00:00:00 UTC to 2017-03-08 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 commentsMar 7

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
Feb 172017-02-17 00:00:00 UTC2017-02-18 00:00:00 UTC202
Feb 182017-02-18 00:00:00 UTC2017-02-19 00:00:00 UTC505
Feb 192017-02-19 00:00:00 UTC2017-02-20 00:00:00 UTC000
Feb 202017-02-20 00:00:00 UTC2017-02-21 00:00:00 UTC000
Feb 212017-02-21 00:00:00 UTC2017-02-22 00:00:00 UTC000
Feb 222017-02-22 00:00:00 UTC2017-02-23 00:00:00 UTC000
Feb 232017-02-23 00:00:00 UTC2017-02-24 00:00:00 UTC000
Feb 242017-02-24 00:00:00 UTC2017-02-25 00:00:00 UTC000
Feb 252017-02-25 00:00:00 UTC2017-02-26 00:00:00 UTC000
Feb 262017-02-26 00:00:00 UTC2017-02-27 00:00:00 UTC000
Feb 272017-02-27 00:00:00 UTC2017-02-28 00:00:00 UTC000
Feb 282017-02-28 00:00:00 UTC2017-03-01 00:00:00 UTC000
Mar 12017-03-01 00:00:00 UTC2017-03-02 00:00:00 UTC000
Mar 22017-03-02 00:00:00 UTC2017-03-03 00:00:00 UTC000
Mar 32017-03-03 00:00:00 UTC2017-03-04 00:00:00 UTC000
Mar 42017-03-04 00:00:00 UTC2017-03-05 00:00:00 UTC000
Mar 52017-03-05 00:00:00 UTC2017-03-06 00:00:00 UTC000
Mar 62017-03-06 00:00:00 UTC2017-03-07 00:00:00 UTC000
Mar 72017-03-07 00:00:00 UTC2017-03-08 00:00:00 UTC303

What Hacker News says

3 sources
The error is here: https://github.com/zcoinofficial/zcoin/blob/81a667867b5d8489... and the line of code: zccoinSpend.denomination == libzerocoin::ZQ_LOVELACE; In other words, a statement with no effect. In D, such a line gives an error, not a warning: Error: == has no effect in expression You can force the statement to be accepted by casting it to void. It's really past time for languages to not accept such code any more. Legacy code needs to get fixed.
In Zcoin implementation bug enabled attacker to create over 500K Zcoins

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.