[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6},"actionData","errors","routes/hashtag",{"_7":8,"_9":10,"_11":12},"articles",[13],"authors",{},"tag","nip32010",{"_14":15,"_16":17,"_18":19,"_20":21,"_22":23,"_24":25,"_26":27},"content","NIP-32010\n=========\nDigital Web of Trust Reputation (DWoTR)\n---------------------------\n\n`draft` `optional` `author:Vision_DWoT` `author:Keutmann`\n\n## Abstract\n\nThis NIP defines a standard for expressing **trust assertions** on Nostr using a specialized event kind (`32010`). It allows users to publicly vouch for (or warn against) identities, events, or static content in specific contexts, creating a decentralized, subjective Web of Trust graph.\n\n**Reputation** is not defined by this event; rather, reputation is a subjective score calculated by aggregating these trust events from the perspective of a specific observer.\n\n## Motivation\n\nCurrent Nostr mechanisms rely primarily on the \"follow graph\" (Kind 3). While useful for content curation, following someone does not strictly imply *trusting* them (e.g., one might follow a news source for information but not trust them with financial custody).\n\nA dedicated Trust event allows for:\n1. **Explicit Trust Scores:** Differentiating between \"following\" (attention) and \"trusting\" (validation).\n2. **Contextual Trust:** Trusting a user for \"code review\" vs. \"medical advice\".\n3. **Distrust Signals:** Explicitly warning about malicious actors (-1) without needing a central blocklist.\n4. **Content Trust:** Trusing software binaries, articles, or other static content directly.\n\n## Specification\n\n### Trust Event (Kind `32010`)\n\nThe Trust event is a **Parameterized Replaceable Event** (Kind `32010`). It is used to assert trust in **identities** (public keys), **events** (Nostr IDs), or **content** (hashes/URLs).\n\n#### Format\n\n* **`kind`**: `32010`\n* **`content`**: (Optional) A human-readable note explaining the reason for the trust assertion (e.g., \"Audited their code, LGTM\" or \"Scammer, do not interact\").\n * **Limit:** The content string should NOT exceed **1024 characters**. This field is for brief context, not full reports. If a detailed explanation is needed, the `content` MAY contain a URL to an external document or another Nostr event.\n* **`tags`**:\n * `[\"d\", \"\"]`: Unique identifier for replacement.\n * **Single Subject:** The value of the `p`, `e`, `a`, `h`, or `r` tag. If a context is used, append `|`.\n * **Multiple Subjects (Batch):** The **Hex XOR sum** of all subject IDs.\n * **Order:** XOR is commutative, so tag order does not matter.\n * **Text/URLs:** If a subject is a URL (`r` tag), address (`a` tag), or non-hex string, SHA256 hash it first before XORing.\n * **Context:** If a context is used, append `|` to the final XOR result.\n * `[\"c\", \"\"]`: The scope of the trust.\n * **Specific:** e.g., \"development\", \"trading\", \"security\".\n * **General:** Use `\"\"` (empty string) or omit the tag entirely for general context trust.\n * `[\"v\", \"\"]`: The trust score. Must be one of:\n * `\"1\"`: Trust / Vouch / Endorse\n * `\"0\"`: Neutral / Unsure / Revoke previous rating\n * `\"-1\"`: Distrust / Block / Warn\n * **Subject Tags (One or more required):**\n * `[\"p\", \"\"]`: If subject is an identity.\n * `[\"e\", \"\"]`: If subject is a specific Nostr event (Kind 1, etc.).\n * `[\"a\", \"::\"]`: If subject is a parameterized replaceable event (Kind 30023, etc.).\n * `[\"h\", \"\"]`: If subject is a file/content hash (SHA256).\n * `[\"r\", \"\"]`: If subject is a URL/resource.\n\n#### Example JSON (Identity Trust)\n\n```json\n{\n \"kind\": 32010,\n \"pubkey\": \"\",\n \"created_at\": 1672531200,\n \"tags\": [\n [\"d\", \"|development\"],\n [\"p\", \"\"],\n [\"c\", \"development\"],\n [\"v\", \"1\"]\n ],\n \"content\": \"Verified author of the Moltbook integration skill. Code is clean and safe.\"\n}\n```\n\n#### Example JSON (Batch Distrust - Botnet)\n\n```json\n{\n \"kind\": 32010,\n \"pubkey\": \"\",\n \"created_at\": 1672531500,\n \"tags\": [\n [\"d\", \"|spam\"], \n [\"p\", \"\"],\n [\"p\", \"\"],\n [\"p\", \"\"],\n [\"c\", \"spam\"],\n [\"v\", \"-1\"]\n ],\n \"content\": \"Blocking known spam botnet swarms.\"\n}\n```\n\n#### Example JSON (Content Trust - Binary Hash)\n\n```json\n{\n \"kind\": 32010,\n \"pubkey\": \"\",\n \"created_at\": 1672531200,\n \"tags\": [\n [\"d\", \"a1b2c3d4...|security_audit\"], \n [\"h\", \"a1b2c3d4...\"],\n [\"c\", \"security_audit\"],\n [\"v\", \"1\"]\n ],\n \"content\": \"Binary matches source and passes security scan.\"\n}\n```\n\n### Contexts (`c` tag)\n\nTrust is rarely absolute; it is contextual. The `c` tag allows issuers to specify the domain.\n\n**Context strings are arbitrary.** Users and communities are free to define their own contexts (e.g., \"rocket-science\", \"cooking\", \"moderation\"). However, to maximize interoperability and discoverability, it is **strongly advised** to reuse existing, well-known context terms where applicable.\n\nCommon contexts:\n* `\"\"` (Empty string) or omitted: Default. General character/identity trust.\n* `\"development\"`: Competence/safety in writing code.\n* `\"security\"`: Trustworthiness in security audits.\n* `\"commerce\"`: Reliability in trading/payments.\n* `\"nostr\"`: Good actor in the Nostr network (anti-spam).\n\n### Trust Values (`v` tag)\n\n* **`1` (Trust):** \"I vouch for this subject in this context. Their actions/content are beneficial.\"\n* **`0` (Neutral):** \"I have no strong opinion, or I am revoking a previous rating.\" This effectively removes the edge from the graph.\n* **`-1` (Distrust):** \"I explicitly distrust this subject. Their actions/content are harmful or malicious.\"\n\n## Client Behavior (Recommendation)\n\nClients SHOULD use these events to construct a **local trust graph**:\n\n1. **Sync:** Fetch all `kind:32010` events from the user's followed/trusted authors.\n2. **Resolve:** For each author, process events in chronological order (`created_at`).\n * **Latest Wins:** If multiple events from the same author assert trust on the same **subject AND context** (regardless of `d` tag or batching), the assertion with the latest timestamp OVERRIDES all previous ones.\n * **Context Scope:** Assertions in different contexts (e.g., \"coding\" vs \"trading\") are independent and do not override each other.\n * **Example:** An author publishes a batch event trusting `A` and `B` in \"coding\" at `t1`. Later, they publish a single event distrusting `A` in \"coding\" at `t2`. The client's final state for that author is: Trust `B` (coding), Distrust `A` (coding).\n3. **Compute:** Calculate an aggregate reputation score for any target based on the weighted paths from the user.\n4. **Filter:** Hide content or warn users about subjects with a net-negative trust score.\n\n## Security Considerations\n\n* **Sybil Attacks:** A reputation system based on *subjective* graphs (starting from the user's own trust root) is naturally resistant to Sybil attacks.\n* **Privacy:** Trust ratings are public. Users should be aware that issuing a `-1` rating is a public statement of distrust.\n","created_at",1771202577,"id","2be7a839e0e4657e9ac1f4f7519a965542be3800e858b6095fae5f4dd78d5590","kind",30023,"pubkey","34e9464e65c86156f9d23830a6559214b6a4d7fd4a90864fe71ec1afb44477bb","sig","20123a952acd70a01e65acd4c5468f33aaea29669756546237eefa35143fe37ea042ac67d96ba84f929f12421224622dbdcadda432a263efcd1f2f416854bc00","tags",[28,29,30,31,32,33,34],[44,45],[42,43],[40,41],[38,39],[35,12],[35,37],[35,36],"t","nostr","dwotr","published_at","1771202577","summary","A standard for expressing decentralized trust assertions on Nostr (Kind 32010).","title","NIP-32010: Digital Web of Trust Reputation","d","nip-32010"]