HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
mit-dci
tangled-curl
Python2017–2018
mit-dci / tangled-curl

tangled-curl

IOTA's hash function curl is broken

5Distinct people
5Mentions
0Explicit recommenders
171GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

IOTA's hash function curl is broken

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

Observed mentions: 2017-09-11 02:38:57 UTC to 2018-01-29 14:01:59 UTC. Weeks start Monday, UTC.

0122017-09-11 00:00:00 UTC to 2017-09-18 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsSep 112017-09-18 00:00:00 UTC to 2017-09-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-25 00:00:00 UTC to 2017-10-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-10-02 00:00:00 UTC to 2017-10-09 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-10-09 00:00:00 UTC to 2017-10-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-10-16 00:00:00 UTC to 2017-10-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-10-23 00:00:00 UTC to 2017-10-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-10-30 00:00:00 UTC to 2017-11-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-11-06 00:00:00 UTC to 2017-11-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-11-13 00:00:00 UTC to 2017-11-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-11-20 00:00:00 UTC to 2017-11-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsNov 202017-11-27 00:00:00 UTC to 2017-12-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-12-04 00:00:00 UTC to 2017-12-11 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-12-11 00:00:00 UTC to 2017-12-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-12-18 00:00:00 UTC to 2017-12-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-12-25 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2018-01-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-08 00:00:00 UTC to 2018-01-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-15 00:00:00 UTC to 2018-01-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-22 00:00:00 UTC to 2018-01-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-29 00:00:00 UTC to 2018-02-05 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsJan 29

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
Sep 112017-09-11 00:00:00 UTC2017-09-18 00:00:00 UTC110
Sep 182017-09-18 00:00:00 UTC2017-09-25 00:00:00 UTC000
Sep 252017-09-25 00:00:00 UTC2017-10-02 00:00:00 UTC000
Oct 22017-10-02 00:00:00 UTC2017-10-09 00:00:00 UTC101
Oct 92017-10-09 00:00:00 UTC2017-10-16 00:00:00 UTC000
Oct 162017-10-16 00:00:00 UTC2017-10-23 00:00:00 UTC000
Oct 232017-10-23 00:00:00 UTC2017-10-30 00:00:00 UTC000
Oct 302017-10-30 00:00:00 UTC2017-11-06 00:00:00 UTC000
Nov 62017-11-06 00:00:00 UTC2017-11-13 00:00:00 UTC000
Nov 132017-11-13 00:00:00 UTC2017-11-20 00:00:00 UTC000
Nov 202017-11-20 00:00:00 UTC2017-11-27 00:00:00 UTC000
Nov 272017-11-27 00:00:00 UTC2017-12-04 00:00:00 UTC000
Dec 42017-12-04 00:00:00 UTC2017-12-11 00:00:00 UTC101
Dec 112017-12-11 00:00:00 UTC2017-12-18 00:00:00 UTC000
Dec 182017-12-18 00:00:00 UTC2017-12-25 00:00:00 UTC000
Dec 252017-12-25 00:00:00 UTC2018-01-01 00:00:00 UTC000
Jan 12018-01-01 00:00:00 UTC2018-01-08 00:00:00 UTC000
Jan 82018-01-08 00:00:00 UTC2018-01-15 00:00:00 UTC000
Jan 152018-01-15 00:00:00 UTC2018-01-22 00:00:00 UTC000
Jan 222018-01-22 00:00:00 UTC2018-01-29 00:00:00 UTC000
Jan 292018-01-29 00:00:00 UTC2018-02-05 00:00:00 UTC202

What Hacker News says

1 sources
IOTA is amateur hour. The author implemented their own hashing algo, "curl", which is used all over the place in IOTA, until recently including signing transactions. Researchers were able to produce distinct transactions with colliding signatures [1]. Depending on whether you believe the author, either they did it intentionally for the implied purpose of attacking competing forks (as they claim), or unintentionally because they're incompetent. Neither situation sounds good to me. IOTA also relies on a closed-source "coordinator" for consensus. They call it "training wheels". Who knows if their "tangle" will actually work in production. Crazy to me that people are pumping so much money into it w/o any due diligence. [1] https://github.com/mit-dci/tangled-curl/blob/master/vuln-iot...
In No Bitcoin-based protocol can handle more than 20M users per month

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.