Key Management

Key management is a necessary component of the protocol, as to allow any member of a cluster to participate on their relevant side of an OT circuit. This is additionally important in the context of non-interactive processing -- where a client is not directly initiating the computation, but rather the protocol has prompted it, by virtue of task management or other functions.

RDF Schema

:Key a rdfs:Class;    rdfs:label "a key object".:KeyShare a rdfs:Class;    rdfs:label "a share corresponding to a key".:OfKey a rdfs:Property;    rdfs:domain :Key;    rdfs:range :KeyShare.:Format a rdfs:Property;    rdfs:domain :literal;    rdfs:range :Key.:PublicData a rdfs:Property;    rdfs:domain rdfs:Literal;    rdfs:range :Key.:Protocol a rdfs:Property;    rdfs:domain :literal;    rdfs:range :Key.:KeyData a rdfs:Property;    rdfs:domain rdfs:Literal;    rdfs:range :KeyShare.

Because the distinct sections of data are effectively controlled and encrypted by the relevant keyholders, provided keyshare owners are not one and the same, the key never will exist combined on a single device, but further, even if keyshare owners are one and the same, their meaningful online use would still be reflected in the global hypergraph mutation and thus cannot be used to forge state.

The Protocol reference property is multi-purpose -- because it is a Literal, it may refer to a known protocol that is baked into the node software, or, if all parties are inclined to engage, can refer to an executable File reference which can contain an OT circuit, so as to enable additional MPC protocols not inherent to network function.