ΨNet (PsiNet) is a hybrid decentralized AI context protocol designed to enable AI agents to own, share, and verify conversation history across systems securely.
- Purpose: Direct agent-to-agent communication
- Benefits:
- Low latency for real-time context sharing
- Reduced central points of failure
- Scalable mesh topology
- Use Cases:
- Live context synchronization between AI agents
- Direct handoff of conversation threads
- Real-time collaboration sessions
- Purpose: Content-addressed distributed storage
- Benefits:
- Immutable content addressing (CID-based)
- Distributed file storage and retrieval
- Built-in deduplication
- Global content availability
- Use Cases:
- Storing large context graphs
- Versioned context snapshots
- Distributed caching of conversation trees
- Purpose: Immutable audit trail and ownership verification
- Benefits:
- Tamper-proof transaction history
- Decentralized consensus
- Smart contract capabilities for access control
- Use Cases:
- Recording context ownership transfers
- Timestamped proof of context creation
- Capability token management
- Access permission enforcement
- Purpose: Permanent, immutable storage
- Benefits:
- Pay-once, store-forever model
- Cryptographic proof of storage
- Long-term archival guarantees
- Use Cases:
- Permanent archival of critical context chains
- Historical conversation preservation
- Legal/compliance requirements for AI interactions
- Training data provenance
- Purpose: Self-sovereign identity for AI agents and users
- Technical Details:
- Ed25519 elliptic curve cryptography
- High-performance signature verification
- Small signature size (64 bytes)
- Fast key generation
- Benefits:
- No central authority required
- Cryptographically verifiable identity
- Interoperable across systems
- Use Cases:
- AI agent authentication
- User identity management
- Cross-platform identity portability
- Purpose: Fine-grained permissions management
- Model: Object-capability security model
- Benefits:
- Principle of least privilege
- Delegatable permissions
- Revocable access tokens
- No ambient authority
- Use Cases:
- Selective context sharing
- Time-limited access grants
- Hierarchical permission delegation
- Third-party auditor access
- Purpose: Privacy-preserving verification
- Benefits:
- Prove facts without revealing data
- Verify context properties without disclosure
- Privacy-preserving audits
- Use Cases:
- Prove context ownership without revealing content
- Verify conversation occurred without exposing details
- Compliance checks on encrypted data
- Privacy-preserving reputation systems
- Structure: Graph-based conversation representation
- Nodes: Individual messages, context states
- Edges: Relationships, references, dependencies
- Encryption:
- End-to-end encryption by default
- Per-graph or per-node encryption keys
- Key management via capability tokens
- Benefits:
- Preserves conversation structure
- Efficient partial context sharing
- Enables graph traversal queries
- Privacy protection
- Use Cases:
- Multi-agent conversation threads
- Branching conversation histories
- Context dependency tracking
- Selective revelation of conversation paths
- Purpose: Eventual consistency in distributed context
- Technical Approach:
- Operation-based or state-based CRDTs
- Automatic conflict resolution
- Commutative, associative operations
- Benefits:
- No coordination needed for updates
- Guaranteed convergence
- Offline-first capabilities
- Resilient to network partitions
- Use Cases:
- Merging parallel conversation branches
- Synchronizing context across multiple agents
- Offline context updates
- Collaborative context building
1. AI Agent Creation
└─> Generate Ed25519 DID
└─> Register identity on blockchain
└─> Obtain capability tokens
2. Context Creation
└─> Create encrypted context graph node
└─> Generate content hash (CID)
└─> Store on IPFS
└─> Record ownership on blockchain
└─> Archive critical contexts to Arweave
3. Context Sharing
└─> Generate capability token with permissions
└─> Share via P2P or IPFS reference
└─> Recipient verifies sender DID
└─> Recipient uses capability to decrypt
└─> CRDT merge if needed
4. Context Verification
└─> Check blockchain for ownership proof
└─> Verify Ed25519 signatures
└─> Use zero-knowledge proofs for privacy verification
└─> Validate content integrity via CID
- End-to-end encryption of context graphs
- Capability-based access control
- Zero-knowledge proofs for privacy
- Content-addressed storage (IPFS CIDs)
- Blockchain audit trail
- Cryptographic signatures (Ed25519)
- Arweave permanent storage proofs
- Distributed P2P network
- IPFS content replication
- Multiple blockchain nodes
- Arweave permanent availability
- DID-based identity
- Ed25519 signature verification
- Capability token validation
- Fine-grained capability tokens
- Smart contract enforcement
- Delegatable permissions
- IPFS: Distributed across network
- Blockchain: Only metadata/proofs, not full content
- Arweave: Permanent but selective archival
- P2P: Ephemeral/cached data
- P2P mesh reduces central bottlenecks
- IPFS DHT for content discovery
- Blockchain sharding potential
- CRDT enables offline operations
- Ed25519: Fast signature operations
- Zero-knowledge proofs: Verification cheaper than proof generation
- CRDT: Local-first, async convergence
- Public Context: Stored unencrypted on IPFS/Arweave
- Semi-Private: Encrypted, shared with capability tokens
- Private: Encrypted, only owner has access
- Provable-Private: Zero-knowledge proofs allow verification without disclosure
- Data minimization (only necessary metadata on blockchain)
- Selective disclosure via capabilities
- Anonymous verification via ZK proofs
- User control over data sharing
AI agents maintain continuous context when moving between platforms (ChatGPT → Claude → Gemini)
Multiple AI agents collaborate on a task with shared, synchronized context
Users prove an AI interaction occurred without revealing the conversation
AI agents can buy/sell/trade valuable context while maintaining provenance
Organizations audit AI interactions while respecting privacy
Users maintain lifetime AI conversation history they truly own
| Challenge | Solution |
|---|---|
| Key Management | Hierarchical deterministic keys from DID |
| Network Partitions | CRDT eventual consistency |
| Large Context Size | Chunking + IPFS content addressing |
| Blockchain Costs | Only metadata on-chain, bulk storage off-chain |
| Privacy vs Verification | Zero-knowledge proofs |
| Spam/Abuse | Capability-based permissions + reputation |
| Legacy System Integration | DID-compatible adapters |
- Context Compression: Semantic compression for long conversations
- Context Search: Encrypted search over distributed contexts
- Federated Learning: Train models on encrypted context graphs
- Cross-Chain Bridges: Multi-blockchain support
- Context Analytics: Privacy-preserving analytics via ZK proofs
- Version Control: Git-like branching for conversation histories
- Context Templates: Reusable context patterns
- Incentive Layer: Token economics for context sharing/storage
ΨNet represents a novel approach to AI context management by combining:
- Decentralization (P2P, IPFS, blockchain)
- Security (encryption, DIDs, signatures)
- Privacy (zero-knowledge proofs, capabilities)
- Consistency (CRDTs)
- Permanence (Arweave)
This hybrid architecture enables AI agents to have portable, verifiable, and secure conversation histories that they (and their users) truly own, addressing critical needs in the evolving AI ecosystem.