Public Institutions & Research

Open questions

Two design decisions are open: who operates the transparency log and how verification time is evidenced. Two questions about the record are open as well: how a relying party confirms what an entry refers to, and how far a reviewer can rely on a reason code alone.

  • Subject confirmation: how a relying party confirms what an entry refers to.
  • Transparency log operation: who operates it, and under which key.
  • Time evidence, and how far a reviewer can rely on a coded outcome.
Read the protocolPropose a question

Institutions

The fields the questions belong to

Each open question falls within cryptography, data protection or market infrastructure.

  • Public institutions

    Bodies working on market infrastructure and on how confidential financial evidence can be checked across institutions.

  • Universities

    Groups in applied cryptography, data protection and finance, where the subject-reference question sits.

  • Research centers

    Centers working on cryptographic protocols and key management, where the transparency-log question sits.

  • Innovation hubs and public funding programs

    Programs that fund applied work on financial infrastructure and could host a study of one open question.

Research themes

None of the questions needs an issuer's evidence

The material behind a NAV or a valuation belongs to its holder, who need not share it. These four questions concern the record a verification leaves behind, the reference, the log, the time and the reason code. None of them needs access to an issuer's documents.

  • Subject confirmation

    The subject reference is a salted digest the issuer can open. No check in version 0.1.0 reads that opening, so confirming the subject of an entry and managing salts across a series are open.

  • Transparency log operation

    Who operates a transparency log, under which key, and what a successor key states about earlier records when that key rotates. Version 0.1.0 reserves the check and never requests it.

  • Time evidence

    An issuer's key is judged as of a point in time. Version 0.1.0 takes that time from the operator, and how it could be evidenced, and by which authority, is open.

  • Coded outcomes

    How far a reviewer can rely on a reason code without seeing the evidence behind it. The catalog states a consequence for each code, and how much that statement can carry is open.

Research

Proposing a question

Write to the maintainer with the question and the group that would take it up.

Propose a question