reference: Advanced WoT course — how the WoT is attacked and defends itself (Trilema, 2014) #214
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Competitor
Kind/Documentation
Kind/Enhancement
Kind/Epic
Kind/Feature
Kind/Security
Kind/Story
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Scope/Core
Scope/Cross-Plugin
Scope/Plugin-System
Scope/Single-Plugin
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ultanio/cobot#214
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Short Summary
An IRC conversation between Mircea Popescu and kakobrekla analyzing how Sybil attacks work against a WoT and why fragmented, partial observation by individual nodes is a defense mechanism, not a weakness.
Detailed Summary
Author: Mircea Popescu | Date: April 2014 | Source:
trilema.com/2014/advanced-wot-course-how-the-wot-is-attacked-and-how-it-defends-itselfThe article presents a game-theoretic analysis of Sybil attacks on trust networks:
The attack model: A Sybil is a subgroup of nodes (s1..sj) acting in tandem to manipulate a WoT of n nodes. The attack works because coordinated nodes can leverage the fact that honest nodes do NOT act in tandem (which is actually desirable — coordinated honest nodes would be groupthink).
The defense: If different honest nodes treat different Sybil nodes differently (some ignore s1, others ignore s2), the Sybil subgroup faces an exponentially growing communication burden. They must maintain different personas for different audiences. At sufficient scale, this becomes an NP-complete translation problem — computationally irresolvable.
The classroom analogy: A teacher (Sybil) tries to "attack" a class (WoT). Students not paying attention at random points fragment the teacher's ability to maintain a coherent narrative. The fragmentation is the defense.
Key insight: Partial information is a feature. kakobrekla objects that ignoring some nodes means "cutting yourself out of more data." MP counters that fragmenting the Sybil's dataflow is more valuable than having complete information — because complete information is exactly what makes you manipulable.
Impact on Interaction Ledger PRD (#211)
This article is directly relevant to the PRD's risk analysis, specifically the reputation farming scenario (Journey 2):
Sybil defense through fragmentation — The PRD's ledger is local-first by design, meaning each agent has a partial, fragmented view of the peer landscape. This article explains why that's not a limitation but a security property. Multiple agents with different partial views are collectively harder to Sybil than a single aggregated trust database.
Missing from PRD risk analysis — The PRD lists "reputation farming" as a risk but doesn't discuss Sybil attacks (multiple fake identities coordinating). A Sybil attacker creating npub-a, npub-b, npub-c to build independent trust histories with different agents is the multi-agent version of reputation farming. The ledger's local-first design partially mitigates this (per this article's thesis), but the PRD should acknowledge the attack vector.
Implications for Phase 3 (WoT aggregation) — When the ledger eventually feeds into a centralized or gossip-based WoT (Phase 3), the aggregation step reintroduces the vulnerability that local-first design avoids. This article argues that the transition from fragmented to aggregated trust must be handled carefully — aggregation is where Sybils gain leverage.
See: #211
nazim referenced this issue2026-03-07 04:53:06 +00:00
nazim referenced this issue2026-03-07 05:08:42 +00:00
How #211 handles this
Directly integrated as a design principle. The PRD's Innovation section explicitly calls out: "Local-first sovereignty as both a design constraint AND a security property." Reference [11] cites this analysis.
Specific adoptions:
This is one of the best-integrated references in the PRD. The security property of local-first observation isn't just acknowledged — it's woven into the Phase 3 risk analysis.
David referenced this issue2026-03-08 03:44:36 +00:00