PS.AI JOIN WAITLIST →
TECHNICAL · ARCHITECTURE

The technical
layer.

How PS.ai actually works under the hood — namespaces, non-transferable identity tokens, consent state, license envelopes, receipts, platform DNS, model registry, settlement. This is the developer and compliance-buyer view. Performers do not need to read this page to be protected by it.

THE NAMESPACE01 / 07

PS.ai operates a three-layer namespace stack covering identity, platform DNS, and settlement. The substrate is owned by PS.ai and cannot be cloned without acquiring the underlying namespace assets.

[name].id.pornstar
Performer identity namespace. All performer records live under id.pornstar as non-transferable on-chain tokens. This is a hard rule, not a convention — system-wide primitives at the apex of .pornstar are reserved and not user-mintable.
Example: lana.id.pornstar
[company].[service].pornserver
Platform DNS for AI companies, studios, agencies, and LoRA marketplaces. Each company operates a service tree under .pornserver. The pattern is strict: company segment + service segment + TLD.
Examples: company.api.pornserver · company.vault.pornserver · company.takedown.pornserver · company.webhook.pornserver · company.auth.pornserver · company.cdn.pornserver
pornstar.token
Settlement token, not a domain. 1:1 mint/burn against a chosen stablecoin (USDC, USDT, or other major stablecoin). Royalties flowing from [name].id.pornstar are settled in pornstar.token, redeemable to fiat-pegged stablecoins on demand.
Mint/burn 1:1 · Stablecoin-pegged · Royalty rail
IDENTITY-LOCK MECHANICS02 / 07

Every identity at [name].id.pornstar is a non-transferable on-chain token cryptographically bound to the performer's wallet at mint.

NON-TRANSFERABLE
The identity token rejects transfer functions at the contract level. Agencies cannot sell them. Platforms cannot seize them. Wallet compromise does not enable transfer to another wallet.
CRYPTOGRAPHICALLY LOCKED
Likeness fingerprint, consent state, license scope, and royalty endpoint are recorded on-chain and tied to the minting wallet. Platforms verify against the chain — not against an off-chain database that can be tampered with, hacked, or de-platformed.
ROYALTY-BEARING
Each consent query that resolves to a permitted-use license generates a royalty obligation, settled in pornstar.token to the bound wallet. Revenue routing is contractual, not platform-discretionary.
ATOMIC REVOCATION
Performer flips consent state from the bound wallet. New state propagates on the next platform query — no support tickets, no platform discretion, no plausible deniability for non-compliant operators.
CONSENT STATES03 / 07

Six states. Each maps to a deterministic platform action. Deny-by-default — if the namespace returns unknown, platforms must treat it as opt_out.

STATE
PLATFORM ACTION
permitted
Generation / training / use allowed within license scope.
restricted
Allowed only under the returned license envelope. Out-of-scope use is denied.
opt_out
No generation. No training. No use.
revoked
Immediately block future use. Previously-issued licenses are voided.
expired
License lapsed. Require renewed authorization before any further use.
unknown
Deny by default. Treated as opt_out.
LICENSE ENVELOPE04 / 07

When consent state is permitted or restricted, the namespace returns a signed license envelope. The envelope defines, machine-readably, what is allowed.

{
  "license_id":     "lic_...",
  "namespace":      "lana.id.pornstar",
  "holder":         "company.api.pornserver",
  "allowed_uses":   ["image_generation", "video_generation"],
  "prohibited":     ["training_new_model", "third_party_syndication"],
  "territory":      ["US", "CA", "UK"],
  "duration_start": "2026-05-15T00:00:00Z",
  "duration_end":   "2027-05-15T00:00:00Z",
  "royalty_split":  { "performer": 0.70, "platform": 0.20, "protocol": 0.10 },
  "revocable":      true,
  "status":         "active",
  "signature":      "ed25519:..."
}

Envelopes are signed at issuance. Platforms verify signatures before honoring the license. Tampering breaks the signature.

CONSENT RECEIPTS05 / 07

Every consent query produces a signed, timestamped, hashed receipt — the compliance artifact platforms hold for audit, legal review, and regulatory inquiry.

{
  "receipt_id":       "rcpt_...",
  "timestamp_utc":    "2026-05-15T00:00:00Z",
  "requester":        "studio.api.pornserver",
  "subject":          "lana.id.pornstar",
  "action_requested": "image_generation",
  "consent_result":   "permitted",
  "license_id":       "lic_...",
  "record_hash":      "sha256:...",
  "signature":        "ed25519:..."
}
.PORNSERVER SUBTREE06 / 07

Each integrating platform receives a dedicated subtree under .pornserver. Service hostnames are illustrative — platforms choose which services they operate.

[company].api.pornserver
Platform's PS.ai API endpoint for consent, license, and receipt queries.
[company].vault.pornserver
Encrypted asset vault for license-gated content.
[company].takedown.pornserver
Verified takedown intake. Performer-initiated claims route to the platform's enforcement queue.
[company].webhook.pornserver
Outbound notifications — revocation events, license changes, royalty settlements.
[company].auth.pornserver
Platform SSO and API key issuance, tied to platform identity.
[company].cdn.pornserver
Content delivery surface for license-gated assets. Edge-cached.
MODEL REGISTRY07 / 07

LoRA and fine-tune model creators register their work in the PS.ai model registry. Each registered model is a licensable asset with its own consent envelope, royalty terms, and on-chain ownership record.

A platform generating content from a registered model must clear both rights layers in a single consent query: the performer identity at [name].id.pornstar (if the model is trained on a real person) AND the model license from the registered creator. Royalties split per the license terms.

{
  "model_id":         "model_...",
  "creator":          "creator_handle.id.pornstar",
  "model_type":       "lora",
  "base_model":       "flux-dev",
  "model_hash":       "sha256:...",
  "trained_on":       ["lana.id.pornstar"],
  "license_required": true,
  "commercial_terms": { "rate": 0.02, "currency": "USDC", "min_per_use": 0.10 },
  "royalty_split":    { "performer": 0.40, "creator": 0.40, "protocol": 0.20 },
  "status":           "active"
}

Models trained on real performers are linked at the registry level. The performer's identity record is the source of truth for their consent; the model license is the source of truth for the creator's terms. Both verify in a single API call.

JOIN EARLY

Want a sandbox key
or a deeper brief?

Platforms request sandbox access. Investors request the data room. Performers reserve their name.

JOIN THE WAITLIST → ABOUT PS.AI