<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Contour: A Practical System for Binary Transparency · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1712.08427/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1712.08427/feed.xml" rel="self" type="application/rss+xml" /><item><title>Contour: A Practical System for Binary Transparency — mentioned by dane-pgp</title><link>https://news.ycombinator.com/item?id=18975153</link><guid isPermaLink="false">urn:hackerpapers:mention:1712.08427:18975153</guid><pubDate>Wed, 23 Jan 2019 02:30:47 GMT</pubDate><description>&lt;p&gt;Right, this is basically Binary Transparency, with the same sort of social mechanisms in place as Certificate Transparency has for dealing with misbehaving CAs. The idea of storing release hashes (or public keys) in a distributed, permissionless, append-only log actually makes a lot of sense, and there are several serious proposals for how to do this, such as EthIKS: http://www.jbonneau.com/doc/B16b-BITCOIN-ethiks.pdf and Contour: https://arxiv.org/pdf/1712.08427.pdf&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1712.08427/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
