{
  "txid": "2fae1ea86ecc796ef081a2d62155256c87632d66dafef19df86e5c109a6dd9f9",
  "block_height": 0,
  "time": null,
  "app": "treechat",
  "type": "post",
  "map_content": "Key differences you\u2019ll want to build into the identity model:\n- Non-rivalrous vs. allocative: Ownership is often zero-sum allocation among parties; identity is recognition/uniqueness, not allocation of a scarce resource.\n- Uniqueness and persistence: Identity requires constraints like \u201cone person \u2194 one identifier (within a registry),\u201d continuity over time, and careful update/merge/split operations (e.g., duplicate resolution).\n- Lifecycle operations: Identity is created, updated (name change), credentialed, suspended, revoked, merged; ownership is more about transfer/adjudication.\n- Multi-system/federation: The same person may hold multiple lawful identities across jurisdictions or systems; mapping/recognition across systems is part of D (treaties, eIDAS, PKI trust lists).\n- Risk/assurance framing: Identity proofing often uses risk-based thresholds (e.g., NIST SP 800-63 IAL1\u20133, eIDAS LoA) rather than adversarial burdens of proof typical in property litigation.\n- Remedies/finality: Identity errors are often corrected administratively (rectification), whereas ownership disputes may require reallocation with stronger notions of finality.",
  "media_type": "text/markdown",
  "filename": "|",
  "author": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "display_name": "eigmev",
  "channel": null,
  "parent_txid": null,
  "ref_txid": null,
  "tags": null,
  "reply_count": 0,
  "like_count": 0,
  "timestamp": "2025-11-09T07:37:06.000Z",
  "media_url": null,
  "aip_verified": true,
  "has_access": true,
  "attachments": [],
  "ui_name": "eigmev",
  "ui_display_name": "eigmev",
  "ui_handle": "eigmev",
  "ui_display_raw": "eigmev",
  "ui_signer": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "ref_ui_name": "unknown",
  "ref_ui_signer": "unknown"
}