Digital Identity

Digital twins, identity traces, data ownership, self-sovereign identity on open protocols, and the question of who controls the model of you.

Identity traces

2038498789800247665 — every outward signal is a trace of identity, measurable and modelable
2038498580294721619 — protecting one’s interests requires acting on one’s own behalf

Digital twin ownership

2038499416785723714 — a digital twin of every user already exists, built by corporations for their sales
2038499548151345612 — the central question is ownership: portable and user-controlled, or vendor-locked
2038499709971746979 — can individuals rely on corporations to preserve their traces?
2038499862745129027 — protecting digital identity demands direct action: build, store, back up, filter
2038527130989208043 — the tools for individual twin ownership do not yet exist

Building your own

My Digital Twin Starts With Claude Code — personal knowledge graph from Claude Code sessions as a digital twin foundation

Self-sovereign identity on Ethereum

Open protocols let users own identity through contracts and signatures, not corporate accounts. EIP-712 is the standard that makes off-chain consent verifiable on-chain; EIP-1271 extends the same machinery to smart contract accounts (Safes, DAOs, multisigs, ERC-4337 accounts).

EIP-712: Typed structured data hashing and signing — canonical standard for type-safe, human-readable signing
EIP-712 Typed Data — the type system for signable structured messages
EIP-712 hashStruct — core hashing algorithm
EIP-712 Domain Separator — binding signatures to chain, contract, protocol
Ethereum Signed Message Encoding — leading-byte disambiguation across message kinds
Off-Chain Signatures — the pattern EIP-712 secures
ERC-1271: Standard Signature Validation Method for Contracts — contract-owned identities signing via isValidSignature
EIP-1271 isValidSignature — the magic-value interface method in detail
Smart Account Signatures — bridging EOA and contract signers behind one verifier path
Creating a Farcaster Account by Hand — applied example: Safe custody + EIP-1271 + EIP-712 for self-sovereign Farcaster onboarding

Safe Protocol Kit (SDK layer)

The TypeScript SDK that automates the standards above into four clean stages: create a message, sign it, publish it, validate it. The practical implementation layer between theory and on-chain reality.

Safe Protocol Kit — the TypeScript SDK for interacting with Safe accounts
Safe Protocol Kit Message Signatures — the end-to-end message signing flow
EthSafeMessage — the mutable signature accumulator
Safe SigningMethod — the enum selecting between ECDSA, EIP-712, and nested-Safe signing
Safe Nested Contract Signatures — recursive EIP-1271 for Safes owned by Safes
SignMessageLib — the delegatecall target for on-chain pre-approved hashes
Safe Transaction Service — the off-chain storage backend for partial signatures

Moc AI Agents — agents that operate on your behalf
Moc Writing and Thinking — public thinking as identity construction