Post
133
✅ Article highlight: *Identity, Pseudonymity, and Sybil Resistance Beyond Wallet-Centric Models* (art-60-305, v0.1)
TL;DR:
This article argues that a wallet is not an identity.
Wallets and keys are good at proving control, signing, and transfer. But open networks also need to model continuity, pseudonymity, role authority, subjecthood, external reliance, and Sybil resistance—without collapsing all of them into key possession.
Read:
kanaria007/agi-structural-intelligence-protocols
Why it matters:
• separates authentication from authority and anti-abuse
• treats pseudonymity as bounded disclosure, not missing identity
• prevents stable addresses or signatures from being overread as trust
• keeps continuity visible across key rotation, migration, delegation, or successor change
• treats Sybil resistance as more than token cost
What’s inside:
• separate identity surfaces for control, continuity, subjecthood, reliance, and role authority
• pseudonymity boundary notes
• network identity profiles
• Sybil-resistance design bundles
• economic, reputation, role-bounded, review, and hybrid anti-Sybil friction
• distinctions between one actor acting as many and legitimate plurality
• guidance for external reliance on pseudonymous or attested actors
Key idea:
Do not say:
*“this wallet is the identity.”*
Say:
*“this credential proves control, this continuity record links the actor over time, this pseudonymity boundary limits disclosure, this role defines authority, and this Sybil-resistance design handles multiplicity without pretending they are all the same problem.”*
Pseudonymity is not absence of identity.
And Sybil resistance is not just expensive participation.
TL;DR:
This article argues that a wallet is not an identity.
Wallets and keys are good at proving control, signing, and transfer. But open networks also need to model continuity, pseudonymity, role authority, subjecthood, external reliance, and Sybil resistance—without collapsing all of them into key possession.
Read:
kanaria007/agi-structural-intelligence-protocols
Why it matters:
• separates authentication from authority and anti-abuse
• treats pseudonymity as bounded disclosure, not missing identity
• prevents stable addresses or signatures from being overread as trust
• keeps continuity visible across key rotation, migration, delegation, or successor change
• treats Sybil resistance as more than token cost
What’s inside:
• separate identity surfaces for control, continuity, subjecthood, reliance, and role authority
• pseudonymity boundary notes
• network identity profiles
• Sybil-resistance design bundles
• economic, reputation, role-bounded, review, and hybrid anti-Sybil friction
• distinctions between one actor acting as many and legitimate plurality
• guidance for external reliance on pseudonymous or attested actors
Key idea:
Do not say:
*“this wallet is the identity.”*
Say:
*“this credential proves control, this continuity record links the actor over time, this pseudonymity boundary limits disclosure, this role defines authority, and this Sybil-resistance design handles multiplicity without pretending they are all the same problem.”*
Pseudonymity is not absence of identity.
And Sybil resistance is not just expensive participation.