HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
TCNCoalition
TCN
Rust2020–2020
TCNCoalition / TCN

TCN

Specification and reference implementation of the TCN Protocol for decentralized, privacy-preserving contact tracing.

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

What to know before exploring

What it is

Specification and reference implementation of the TCN Protocol for decentralized, privacy-preserving contact tracing.

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

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 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 day5 dated mentions

Observed mentions: 2020-04-10 03:19:04 UTC to 2020-05-05 10:15:31 UTC.

012020-04-10 00:00:00 UTC to 2020-04-11 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 102020-04-11 00:00:00 UTC to 2020-04-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-12 00:00:00 UTC to 2020-04-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-13 00:00:00 UTC to 2020-04-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-14 00:00:00 UTC to 2020-04-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-15 00:00:00 UTC to 2020-04-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-16 00:00:00 UTC to 2020-04-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-17 00:00:00 UTC to 2020-04-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-18 00:00:00 UTC to 2020-04-19 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-04-19 00:00:00 UTC to 2020-04-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-20 00:00:00 UTC to 2020-04-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-21 00:00:00 UTC to 2020-04-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-22 00:00:00 UTC to 2020-04-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 222020-04-23 00:00:00 UTC to 2020-04-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-24 00:00:00 UTC to 2020-04-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-25 00:00:00 UTC to 2020-04-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-26 00:00:00 UTC to 2020-04-27 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-04-27 00:00:00 UTC to 2020-04-28 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-04-28 00:00:00 UTC to 2020-04-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-29 00:00:00 UTC to 2020-04-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-30 00:00:00 UTC to 2020-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-05-01 00:00:00 UTC to 2020-05-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-05-02 00:00:00 UTC to 2020-05-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-05-03 00:00:00 UTC to 2020-05-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-05-04 00:00:00 UTC to 2020-05-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-05-05 00:00:00 UTC to 2020-05-06 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 5

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
Apr 102020-04-10 00:00:00 UTC2020-04-11 00:00:00 UTC101
Apr 112020-04-11 00:00:00 UTC2020-04-12 00:00:00 UTC000
Apr 122020-04-12 00:00:00 UTC2020-04-13 00:00:00 UTC000
Apr 132020-04-13 00:00:00 UTC2020-04-14 00:00:00 UTC000
Apr 142020-04-14 00:00:00 UTC2020-04-15 00:00:00 UTC000
Apr 152020-04-15 00:00:00 UTC2020-04-16 00:00:00 UTC000
Apr 162020-04-16 00:00:00 UTC2020-04-17 00:00:00 UTC000
Apr 172020-04-17 00:00:00 UTC2020-04-18 00:00:00 UTC000
Apr 182020-04-18 00:00:00 UTC2020-04-19 00:00:00 UTC101
Apr 192020-04-19 00:00:00 UTC2020-04-20 00:00:00 UTC000
Apr 202020-04-20 00:00:00 UTC2020-04-21 00:00:00 UTC000
Apr 212020-04-21 00:00:00 UTC2020-04-22 00:00:00 UTC000
Apr 222020-04-22 00:00:00 UTC2020-04-23 00:00:00 UTC000
Apr 232020-04-23 00:00:00 UTC2020-04-24 00:00:00 UTC000
Apr 242020-04-24 00:00:00 UTC2020-04-25 00:00:00 UTC000
Apr 252020-04-25 00:00:00 UTC2020-04-26 00:00:00 UTC000
Apr 262020-04-26 00:00:00 UTC2020-04-27 00:00:00 UTC101
Apr 272020-04-27 00:00:00 UTC2020-04-28 00:00:00 UTC101
Apr 282020-04-28 00:00:00 UTC2020-04-29 00:00:00 UTC000
Apr 292020-04-29 00:00:00 UTC2020-04-30 00:00:00 UTC000
Apr 302020-04-30 00:00:00 UTC2020-05-01 00:00:00 UTC000
May 12020-05-01 00:00:00 UTC2020-05-02 00:00:00 UTC000
May 22020-05-02 00:00:00 UTC2020-05-03 00:00:00 UTC000
May 32020-05-03 00:00:00 UTC2020-05-04 00:00:00 UTC000
May 42020-05-04 00:00:00 UTC2020-05-05 00:00:00 UTC000
May 52020-05-05 00:00:00 UTC2020-05-06 00:00:00 UTC101

What Hacker News says

5 sources
For those interested, the DP-3T papers can be found on their GitHub (https://github.com/DP-3T/documents). Apple has also published a preliminary specification of their protocol (https://www.apple.com/covid19/contacttracing/) if you'd like to compare. I'd like to mention the TCN Protocol here (https://github.com/TCNCoalition/TCN), another very similar specification. I bring it up because the readme goes into quite a bit of (easily understandable!) detail regarding the trust assumptions of such a protocol and associated rationale. Ultimately I think Apple and Google are right to omit record upload and authentication concerns from the base protocol. The low level implementation should be as interoperable and generalized as possible in order to facilitate immediate uptake and maximum reusability. Higher level concerns such as who to trust and
Read the rest
how to interact with users can be handled by the various app implementations.
In Germany flips to Apple-Google approach on smartphone contact tracing
> like contact tracing APIs, however well-intentioned they may be I share many of the concerns you've expressed, but worrying about the contract tracing API that was recently put forward is (hopefully) unwarranted. A faithful implementation of the joint spec published by Apple and Google would preserve your anonymity until and unless you published your secret keys. Moreover, the overall design is cryptographically sound (unless I missed something recently?) and appears to be decentralized (at least in principle) so in theory you won't have to trust the behavior of any binary blobs unless you choose to do so. For more insight into the design (and security) of such systems, you might take a look at the TCN protocol (https://github.com/TCNCoalition/TCN) or the DP-3T protocol (https://github.com/DP-3T/documents).
In Japan to subsidize 100% of salaries at small companies
This article makes good points about the challenges involved in encouraging widespread application adoption in the face of recent mistrust of tech companies. It will likely require strong and clear messaging from authorities -- backed up by experts and the facts -- to persuade large enough percentages of national populations to adopt contact tracing apps for them to be effective. From what I've seen and read so far, I like the sound of the approach that Covid Watch[1] is taking. It's backed by reputable institutions, is open source (alleviating potential security and trust concerns from software experts), and does include healthcare agencies in the verification loop when cases are reported. Although some technologists might argue for fully decentralized solutions, I'd argue that ensuring that a healthcare agency is in-the-loop is importan
Read the rest
t to avoid accidental and/or malignant false positive self-reports from users. DP-3T[2] also appears trustworthy and has a similar protocol design as far as I understand it. TCN[3] appears to be a good community rallying point for a number of these projects. And be careful of PEPP-PT: it looks potentially troublesome based on this[4] thorough and well-documented investigation. Their data protection policy[5] is archived in case it's useful to refer to in future. This comic[6] is also a really nice introduction to contact tracing protocols and TCN and DP-3T's proposals. [1] - https://www.covid-watch.org/ [2] - https://github.com/DP-3T/documents [3] - https://github.com/TCNCoalition/TCN [4] - https://news.ycombinator.com/item?id=22907499 [5] - https://web.archive.org/web/*/https://www.pepp-pt.org/datens... [6] - https://ncase.me/contact-tracing/
In Contact-tracing apps have a trust problem, even if they do protect your privacy

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.