HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
minio
highwayhash
Go2018–2018
minio / highwayhash

highwayhash

Native Go version of HighwayHash with optimized assembly implementations on Intel and ARM. Able to process over 10 GB/sec on a single core on Intel CPUs - https://en.wikipedia.org/wiki/HighwayHash

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

What to know before exploring

What it is

Native Go version of HighwayHash with optimized assembly implementations on Intel and ARM. Able to process over 10 GB/sec on a single core on Intel CPUs - https://en.wikipedia.org/wiki/HighwayHash

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 3-hour interval2 dated mentions

Observed mentions: 2018-01-10 03:45:22 UTC to 2018-01-12 11:52:24 UTC.

012018-01-10 03:00:00 UTC to 2018-01-10 06:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJan 10, 03:002018-01-10 06:00:00 UTC to 2018-01-10 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-10 09:00:00 UTC to 2018-01-10 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-10 12:00:00 UTC to 2018-01-10 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-10 15:00:00 UTC to 2018-01-10 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-10 18:00:00 UTC to 2018-01-10 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-10 21:00:00 UTC to 2018-01-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-11 00:00:00 UTC to 2018-01-11 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-11 03:00:00 UTC to 2018-01-11 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-11 06:00:00 UTC to 2018-01-11 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 11, 06:002018-01-11 09:00:00 UTC to 2018-01-11 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-11 12:00:00 UTC to 2018-01-11 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-11 15:00:00 UTC to 2018-01-11 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-11 18:00:00 UTC to 2018-01-11 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-11 21:00:00 UTC to 2018-01-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-12 00:00:00 UTC to 2018-01-12 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-12 03:00:00 UTC to 2018-01-12 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-12 06:00:00 UTC to 2018-01-12 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-12 09:00:00 UTC to 2018-01-12 12:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 12, 09: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
Jan 10, 03:002018-01-10 03:00:00 UTC2018-01-10 06:00:00 UTC110
Jan 10, 06:002018-01-10 06:00:00 UTC2018-01-10 09:00:00 UTC000
Jan 10, 09:002018-01-10 09:00:00 UTC2018-01-10 12:00:00 UTC000
Jan 10, 12:002018-01-10 12:00:00 UTC2018-01-10 15:00:00 UTC000
Jan 10, 15:002018-01-10 15:00:00 UTC2018-01-10 18:00:00 UTC000
Jan 10, 18:002018-01-10 18:00:00 UTC2018-01-10 21:00:00 UTC000
Jan 10, 21:002018-01-10 21:00:00 UTC2018-01-11 00:00:00 UTC000
Jan 11, 00:002018-01-11 00:00:00 UTC2018-01-11 03:00:00 UTC000
Jan 11, 03:002018-01-11 03:00:00 UTC2018-01-11 06:00:00 UTC000
Jan 11, 06:002018-01-11 06:00:00 UTC2018-01-11 09:00:00 UTC000
Jan 11, 09:002018-01-11 09:00:00 UTC2018-01-11 12:00:00 UTC000
Jan 11, 12:002018-01-11 12:00:00 UTC2018-01-11 15:00:00 UTC000
Jan 11, 15:002018-01-11 15:00:00 UTC2018-01-11 18:00:00 UTC000
Jan 11, 18:002018-01-11 18:00:00 UTC2018-01-11 21:00:00 UTC000
Jan 11, 21:002018-01-11 21:00:00 UTC2018-01-12 00:00:00 UTC000
Jan 12, 00:002018-01-12 00:00:00 UTC2018-01-12 03:00:00 UTC000
Jan 12, 03:002018-01-12 03:00:00 UTC2018-01-12 06:00:00 UTC000
Jan 12, 06:002018-01-12 06:00:00 UTC2018-01-12 09:00:00 UTC000
Jan 12, 09:002018-01-12 09:00:00 UTC2018-01-12 12:00:00 UTC101

What Hacker News says

2 sources
HighwayHash is a new and very fast pseudo-random-function (PRF) developed by Jyrki Alakuijala, Bill Cox and Jan Wassenberg from Google research. The algorithm takes a 256-bit key and computes 64-, 128- or 256-bit hash values of given messages. HighwayHash can be used to prevent hash-flooding attacks or authenticate short-lived messages. Additionally it can be used as a fingerprinting function. Note that HighwayHash is not a general purpose cryptographic hash function (such as Blake2b, SHA-3 or SHA-2) and should not be used if strong collision resistance is required. At Minio we have developed a native Golang repository for HighwayHash with optimized assembly implementations for both Intel and ARM platforms. We will switch over the bit rot protection that is currently relying on the Blake2b algorithm to HighwayHash. Google repo: https://gi
Read the rest
In HighwayHash: Fast hashing at over 10 GB/s per core in Golang

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.