<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Description of the Operational Mechanics of a Basel Regulated Banking System · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1204.1583/</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/1204.1583/feed.xml" rel="self" type="application/rss+xml" /><item><title>Description of the Operational Mechanics of a Basel Regulated Banking System — mentioned by neffy</title><link>https://news.ycombinator.com/item?id=32497307</link><guid isPermaLink="false">urn:hackerpapers:mention:1204.1583:32497307</guid><pubDate>Wed, 17 Aug 2022 14:59:23 GMT</pubDate><description>&lt;p&gt;This is banking centric, but does have worked examples that may be useful. https://arxiv.org/abs/1204.1583 Above and beyond other reasons, double entry book keeping has some very nice error detection properties (the original reason for its invention) that actually make it quite nice to use as a basis for this kind of software, as it provides a way to catch some bugs very quickly.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1204.1583/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>q-fin.GN</category></item></channel></rss>
