<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>GCN.ONE Blog</title>
		<link>https://www.gcn.one/blog/</link>
		<atom:link href="https://www.gcn.one/blog/feed.xml" rel="self" type="application/rss+xml" />
		<description>Notes on zero-knowledge storage, client-side encryption and verifiable infrastructure from the team building GCN.ONE.</description>
		<language>en</language>
		<lastBuildDate>Mon, 27 Jul 2026 09:00:00 +0000</lastBuildDate>

		<item>
			<title>Why we judge businesses by how they deliver</title>
			<link>https://www.gcn.one/blog/posts/why-we-judge-businesses-by-how-they-deliver.html</link>
			<guid isPermaLink="true">https://www.gcn.one/blog/posts/why-we-judge-businesses-by-how-they-deliver.html</guid>
			<pubDate>Mon, 27 Jul 2026 09:00:00 +0000</pubDate>
			<description>Long before anyone reads the first page of a contract, they have formed an opinion about the organisation that sent it. Why the way sensitive information arrives became part of the message — and the design decision that follows from it.</description>
		</item>

		<item>
			<title>What “zero-knowledge” actually means — and what it doesn’t</title>
			<link>https://www.gcn.one/blog/posts/what-zero-knowledge-actually-means.html</link>
			<guid isPermaLink="true">https://www.gcn.one/blog/posts/what-zero-knowledge-actually-means.html</guid>
			<pubDate>Thu, 16 Jul 2026 09:00:00 +0000</pubDate>
			<description>The phrase gets attached to products that still hold a copy of your key. Here is the concrete test we hold ourselves to: what a full dump of our database would reveal to an attacker who also owns every disk in the cluster.</description>
		</item>

		<item>
			<title>How your files are encrypted before they leave the browser</title>
			<link>https://www.gcn.one/blog/posts/how-your-files-are-encrypted.html</link>
			<guid isPermaLink="true">https://www.gcn.one/blog/posts/how-your-files-are-encrypted.html</guid>
			<pubDate>Thu, 09 Jul 2026 09:00:00 +0000</pubDate>
			<description>A walk through the upload pipeline: deriving keys with Argon2id, sealing content in 8 MiB XSalsa20-Poly1305 segments, and why the encrypted bytes travel straight to a storage node instead of through our API.</description>
		</item>

		<item>
			<title>Why we publish a tamper-evident audit log</title>
			<link>https://www.gcn.one/blog/posts/why-we-publish-a-tamper-evident-audit-log.html</link>
			<guid isPermaLink="true">https://www.gcn.one/blog/posts/why-we-publish-a-tamper-evident-audit-log.html</guid>
			<pubDate>Thu, 02 Jul 2026 09:00:00 +0000</pubDate>
			<description>Encryption stops us from reading your files. It does nothing to stop us from quietly rewriting the record of who touched them. So we chained the log with BLAKE3, anchored the roots to Bitcoin, and shipped the verifier as a separate program.</description>
		</item>

		<item>
			<title>What GCN.ONE is, and why we built it</title>
			<link>https://www.gcn.one/blog/posts/what-gcn-one-is-and-why-we-built-it.html</link>
			<guid isPermaLink="true">https://www.gcn.one/blog/posts/what-gcn-one-is-and-why-we-built-it.html</guid>
			<pubDate>Thu, 25 Jun 2026 09:00:00 +0000</pubDate>
			<description>The no-jargon introduction, written for the people who sign the contracts: what the service does, what a business would use it for, and the one question — who holds the keys? — that separates it from ordinary cloud storage.</description>
		</item>

	</channel>
</rss>
