Application Registration

Objective: To declare a new app within the developer’s namespace and generate its globally unique identifier.

App Registry is “Zero-Knowledge”. It only knows Public Keys and Endpoints. It cannot see user’s or database content.

Prerequisites

A verified developer account (from Developer Identity & Namespace Registration).
Access to the Master Private Key.

The Protocol Workflow

Manifest Creation: The developer creates an app manifest defining the project:

{
  "version": "1.0",
  "data": {
    "owner_namespace": "alice",
    "project_slug": "business_app",
    "display_name": "Business App",
    "description": "A decentralized business app",
    "timestamp": 1705412400,
  },
  "signature": "a28ce01ec0f851...",
  "public_key_hint": "key_id_8812"
}

Signing: The developer hashes the manifest data and signs it with their Master Private Key. The signature is set in the signature field.
Submission: The payload (Manifest data + Signature) is sent to the App Registry.
Cryptographic Validation: The App Registry looks up the Public Key for alice (stored in Developer Identity & Namespace Registration) and verifies the signature. This proves the request came from the real namespace owner.
RDAID Generation: If valid, the registry generates the Reverse Domain AppID (RDAID): org.omiappreg.alice.business_app.7f8a9d
Outcome: The App Registry now acts as the “Source of Truth” for this ID, but has zero services attached to it yet.

Developer Identity & Namespace Registration Provisioning the Trust Anchor (Auth)