<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">Am 01.10.2026 um 15:50 schrieb Tom
Mitchell:<br>
</div>
<blockquote type="cite"
cite="mid:CAAMy4URM-Vc7aTRmgpHjYZo2PVzoZ9n36KEqAP_jcP7eFYuZMw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto"><br>
</div>
<div><br>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr" class="gmail_attr">On Wed, Sep 30, 2026 at
23:57 Jens Weber via cryptography <<a
href="mailto:cryptography@metzdowd.com"
moz-do-not-send="true" class="moz-txt-link-freetext">cryptography@metzdowd.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"
dir="auto">
<div>
<p> </p>
<p class="MsoNormal" style="line-height:normal"><span
lang="EN-GB"
style="font-family:"Times New Roman",serif">Hello,</span></p>
<p class="MsoNormal" style="line-height:normal"><span
lang="EN-GB"
style="font-family:"Times New Roman",serif">I
am currently developing the concept for a project
called <b
style="font-family:"Times New Roman",serif">NOX</b>. It is
still at an early architectural stage. Before
fundamental technical decisions are made, I would like
to ask people with substantially more experience in
cryptography and decentralized systems for critical
feedback.</span></p>
<p class="MsoNormal" style="line-height:normal"><span
lang="EN-GB"
style="font-family:"Times New Roman",serif">I
am the initiator of the concept, but I am not a
cryptographer. For that reason, I am interested not
only in how such an architecture could be implemented,
but first in a more fundamental question: <b
style="font-family:"Times New Roman",serif">Is what I am
envisioning technically and cryptographically
realistic at all?</b></span></p>
<p class="MsoNormal" style="line-height:normal"><span
lang="EN-GB"
style="font-family:"Times New Roman",serif">The
basic idea behind NOX is an international trust,
identity and authorization infrastructure that could
connect independent institutions without creating a
central database containing everyone's sensitive
information.</span></p>
<p class="MsoNormal" style="line-height:normal"><span
lang="EN-GB"
style="font-family:"Times New Roman",serif">The
underlying data could remain where it belongs
professionally — for example, with hospitals, public
authorities, universities or other responsible
institutions. NOX would operate in the background to
verify identities and institutional identities,
enforce authorization, provide cryptographic
provenance, and maintain tamper-evident and auditable
histories.</span></p>
<p class="MsoNormal" style="line-height:normal"><span
lang="EN-GB"
style="font-family:"Times New Roman",serif">One
fundamental requirement of the concept is:</span></p>
<p class="MsoNormal" style="line-height:normal"><b><span
lang="EN-GB"
style="font-family:"Times New Roman",serif">There must be no
universal master key.</span></b><span lang="EN-GB"
style="font-family:"Times New Roman",serif"></span></p>
<p class="MsoNormal" style="line-height:normal" dir="auto"><span
lang="EN-GB"
style="font-family:"Times New Roman",serif">Neither
the operator, a government, an administrator, an
investor, nor even the founder of NOX should possess a
key capable of bypassing the security and
authorization structure of the entire system.</span></p>
</div>
</blockquote>
<div dir="auto">…</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"
dir="auto">
<div>
<p class="MsoNormal" style="line-height:normal"><span
lang="EN-GB"
style="font-family:"Times New Roman",serif">The
sensitive records themselves should not simply be
placed on a public blockchain.</span></p>
<p class="MsoNormal" style="line-height:normal"><span
lang="EN-GB"
style="font-family:"Times New Roman",serif">NOX
may also contain a <b
style="font-family:"Times New Roman",serif">completely
separate economic layer</b>.</span></p>
<p class="MsoNormal" style="line-height:normal" dir="auto"><span
style="font-family:"Times New Roman",serif">….</span><br>
</p>
<p class="MsoNormal" style="line-height:normal"><b><span
lang="EN-GB"
style="font-family:"Times New Roman",serif">Money or token
ownership must never buy data rights.</span></b><span
lang="EN-GB"
style="font-family:"Times New Roman",serif"></span></p>
<p class="MsoNormal" style="line-height:normal" dir="auto"><span
lang="EN-GB"
style="font-family:"Times New Roman",serif">Ownership
of NOX tokens must not grant access to personal data,
medical records, personnel records, identities,
institutional credentials, permissions, or privileged
functions of the protected</span></p>
</div>
</blockquote>
<div dir="auto"><br>
…</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"
dir="auto">
<div>
<p class="MsoNormal" style="line-height:normal" dir="auto"><span
lang="EN-GB"
style="font-family:"Times New Roman",serif"></span></p>
</div>
</blockquote>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"
dir="auto">
<div>
<p class="MsoNormal" style="line-height:normal" dir="auto"><span
lang="EN-GB"
style="font-family:"Times New Roman",serif">Another
part of the concept is artificial intelligence. AI
could operate in the background to identify
contradictions, unusual events, possible manipulation,
suspicious access patterns </span></p>
</div>
</blockquote>
<div dir="auto"><br>
</div>
<div dir="auto">A quick read of your outline … it all depends
on contract law not technology.</div>
<div dir="auto">With multiple international borders any nation
could change law and mess with the system parts that depend
on law.</div>
<div dir="auto"><br>
</div>
<div dir="auto">AI (even SI ) is not magic and must see
essentially the entire system to train the AI.</div>
<div dir="auto">There is no data on day one to train the AI. </div>
<div dir="auto"><br>
</div>
<div dir="auto">My first thought is to assume a magical set of
cryptographic tools and map all the parts and link each with
an annotation MCxx (magical cryptography exchange xx). Thus
map all data flow or links. Emergency digital medical
information as outlined seems impossible. Each link has a
key that must be durable, https is not durable. </div>
<div dir="auto"><br>
</div>
<div dir="auto">Then look at the structure and identify attack
targets and vectors. </div>
<div dir="auto">Since it must be financially self supporting,
there are payments even tax liability requiring audit
visibility.</div>
<div dir="auto"><br>
</div>
<div dir="auto"><b
style="font-size:inherit;background-color:rgba(0,0,0,0);border-color:rgb(0,0,0);color:rgb(0,0,0)"><span
style="font-family:"times new roman",serif;background-color:rgba(0,0,0,0);border-color:rgb(0,0,0);color:rgb(0,0,0)">“Money
or token ownership must never buy data rights.”</span></b></div>
<div dir="auto"><b
style="font-size:inherit;background-color:rgba(0,0,0,0);border-color:rgb(0,0,0);color:rgb(0,0,0)"><span
style="font-family:"times new roman",serif;background-color:rgba(0,0,0,0);border-color:rgb(0,0,0);color:rgb(0,0,0)">How
to have money in a system that has no applicability to
what money was invented for?<br>
<br>
</span></b>
<p><span>Thank you – this is exactly the kind of critical
feedback I was looking for.</span></p>
<p><span>Your suggestion to first map the complete system
and temporarily treat the required cryptographic
mechanisms as “magical cryptography exchanges” is
particularly useful. I think this could help separate
the conceptual requirements from premature decisions
about specific technologies.</span></p>
<p><span>One clarification regarding money: when I wrote
that “money or token ownership must never buy data
rights,” I did not mean that money should have no
function within NOX. Professional services, integrations
or other legitimate services could be paid for. What I
want to prevent is the purchase of authorization to
somebody else's protected data merely through wealth or
token ownership.</span></p>
<p><span>The same distinction applies to AI. My intention is
not to create one central AI that sees or trains on all
personal information in the system. Ideally, AI
functions would operate only within narrowly authorized
contexts and should not require a global view of all
sensitive data.</span></p>
<p><span>I am particularly interested in your comment that
the emergency medical information model “seems
impossible.”</span></p>
<p><strong><span>Is the fundamental problem, in your view,
long-term key management and recovery, or do you
believe that any emergency-access mechanism will
inevitably introduce a master-key-like trust point or
backdoor?</span></strong></p>
<p><span>That distinction would be extremely useful for me
in deciding whether this part of the concept needs to be
redesigned completely.</span></p>
<p><span>Thank you for taking the time to look at it.</span></p>
<p><span>Best regards,</span><br>
<span>F. Ronecker</span><br>
<span>Concept & Vision: NOX</span></p>
<br>
<b
style="font-size:inherit;background-color:rgba(0,0,0,0);border-color:rgb(0,0,0);color:rgb(0,0,0)"><span
style="font-family:"times new roman",serif;background-color:rgba(0,0,0,0);border-color:rgb(0,0,0);color:rgb(0,0,0)"><br>
</span></b></div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"
dir="auto">
<div>
<p class="MsoNormal" style="line-height:normal" dir="auto"><span
lang="EN-GB"
style="font-family:"Times New Roman",serif"></span></p>
</div>
</blockquote>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
The cryptography mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cryptography@metzdowd.com">cryptography@metzdowd.com</a>
<a class="moz-txt-link-freetext" href="https://www.metzdowd.com/mailman/listinfo/cryptography">https://www.metzdowd.com/mailman/listinfo/cryptography</a>
</pre>
</blockquote>
</body>
</html>