<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>spain on krtffl.dev</title>
    <link>https://krtffl.dev/tags/spain/</link>
    <description>Recent content in spain on krtffl.dev</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© [krtffl](https://krtffl.dev)</copyright>
    <lastBuildDate>Wed, 08 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://krtffl.dev/tags/spain/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>verifactu in go: a sha-256 hash chain is spain&#39;s answer to invoice fraud</title>
      <link>https://krtffl.dev/posts/verifactu-hash-chain-go/</link>
      <pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://krtffl.dev/posts/verifactu-hash-chain-go/</guid>
      <description>&lt;p&gt;for years the spanish way to skim a business was the &lt;em&gt;software de doble uso&lt;/em&gt; — a till program with a quiet second set of books. you ring up a sale, the customer walks off with their receipt, and then, later, the invoice simply&amp;hellip; isn&amp;rsquo;t there anymore. the record gets deleted, edited, renumbered. the tax office (the aeat) shows up, asks for invoice 47, and invoice 47 was never born. good luck proving a negative.&lt;/p&gt;
&lt;p&gt;spain&amp;rsquo;s answer, live and mandatory, is delightfully low-tech and i mean that as a compliment: make every invoice cryptographically point at the one before it, so deleting number 47 leaves a hole that screams.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
