Return Identity, Communication, and Applications Back to Users

WoWo vs Traditional Nostr Clients

WoWo is not just a simple Nostr client, but a product-level reconstruction of decentralized communication.

WoWo Not a Nostr Client
But a Productized Implementation of the Next-Generation Communication Network
      

WoWo

This page explains WoWo’s core capabilities in the shortest way possible: identity controlled by users, messages distributed through Relays, security completed locally, and the ecosystem expanded through plugins.

WoWo = Private-Key Identity + Relay Network + Scalable Application Platform

Identity Layer
Public Key = User ID
Private Key = Login Credential
No Phone Number Required

Network Layer
Multiple Relays in Parallel
Decentralized
Censorship Resistant

Security Layer
End-to-End Encryption
Local Signing

Sync Layer
Multi-Device Sync
Offline Recovery

Extension Layer
Plugin System
Bot Automation
Super App

How It Works

WoWo implements decentralized communication based on an event model.PlatformNo Traditional Accounts，The client locally generates key pairs，Messages circulate in the form of events，Relay Responsible for forwarding，Verification and decryption are ultimately completed by the receiving side。

WoWo implements decentralized communication based on an event model.

Users obtain identity through locally generated keys:
Public Key = User ID
Private Key = Login Credential

Communication Steps:
Generate Event → Sign with Private Key → Encrypt Content → Send to Relay → Receiver Verifies Signature → Local Decryption

Features:
No Registration Required
Identity Cannot Be Frozen
Data is Portable
Users Fully Control Their Accounts

WoWo Architecture Diagram

WoWo adopts a layered architecture from applications to encryption. Each layer can evolve independently, supporting both rapid product iteration and long-term stability of protocols and SDKs.

Application Layer: Chat UI / Plugin UI
SDK Layer: State Management / Sync Logic
Protocol Layer: Event Model / Permission Model
Network Layer: Relay Network
Encryption Layer: Signature / E2EE

Feature: Modular Decoupling and Scalability

Nostr Event Mapping

WoWo does not reinvent the underlying event structure, but builds a product-layer experience on top of the existing Nostr model. Understanding field mapping helps implement plugins, bots, and multi-device synchronization.

pubkey = User ID
kind = Type
content = Content
sig = Signature
created_at = Timestamp

Protocol Layer

The protocol layer unifies identity, messaging, Relay, encryption, and plugins into a scalable framework, ensuring WoWo can evolve without breaking compatibility.

identity protocol
message protocol
relay protocol
crypto protocol
plugin protocol

Database

The local database supports offline browsing, fast search, draft preservation, and message indexing. It is not just a cache, but part of the WoWo user experience.

users
messages
conversations
keys
plugins
indexes

Group Chat Mechanism

WoWo group chats do not rely on a single central server, but are built around roles, permissions, and group keys. Key rotation can be triggered when group membership changes, ensuring stronger forward secrecy.

Roles: owner admin member
Permissions: invite remove members modify permissions
Group Keys: Dynamic Rotation

Plugin System

The plugin system upgrades WoWo from a messaging tool into an application platform. Plugins can extend the UI, process event streams, integrate external services, and implement automation.

Plugins Can Listen to Event Streams
Extend UI
Implement Automated Workflows
Build a Super App Ecosystem

Bot Protocol

Bots can be regarded as special identity entities. They can monitor messages, automatically reply, execute commands, integrate AI, or connect to external task systems.

bot = Special Identity
Listen to Messages
Auto Reply
Execute Commands

WoWo Network Architecture

WoWo does not rely on the public Nostr Relay network, but builds its own distributed node system to ensure stability, performance, and user experience. Decentralization does not mean relying on public networks, but avoiding single points of control at the architectural level.

WoWo Relay Architecture

Self-Built Node Network
Globally Distributed Deployment
High Availability Load Balancing

Multi-Node Client Connections
Automatically Select Optimal Nodes
Automatic Failover

Data Synchronization Strategy
Multi-Node Redundancy
Prevent Data Loss

Core Concept
Decentralization ≠ Using Public Relays
But Avoiding Single-Point Control + Providing Independent Network Capability

Advantages
Lower Latency
More Stable Connections
More Controllable Service Quality
Better User Experience

End-to-End Encryption

WoWo emphasizes content privacy by default. Message content is encrypted on the sender side, Relays cannot read it, and only the intended receiver can decrypt it.

Sender Encrypts
Relay Cannot Read
Receiver Decrypts
Privacy Guaranteed

Login Flow

Login does not rely on password databases, but on challenge-response signatures. The client proves identity ownership through private-key signatures, while servers or Relays only perform verification.

Server Challenge
Client Signature
Verify Signature
Login Completed

Group Key Rotation

When group members join, leave, or permissions change, WoWo can generate and distribute new group keys to reduce risks caused by long-term exposure of old keys.

Member Changes
Generate New Group Key
Redistribute
Ensure Forward Secrecy

Message Sharding

For large text, large attachments, or weak network conditions, messages can be split into multiple chunks for parallel transmission and reassembled on the client side to improve stability and success rate.

Large Files Split into Chunks
Parallel Transmission
Client Reassembly

Offline Cache

Offline caching is not simply saving chat history, but a user-experience protection mechanism for weak network conditions, including local databases, incremental synchronization, and eviction strategies.

Local Database
Incremental Synchronization
LRU Cleanup Strategy
Available in Weak Networks

Performance Optimization

WoWo optimizes performance across networking, storage, rendering, and encryption, aiming to achieve lower latency and smoother interactions while maintaining security.

Batch Events
Parallel Relays
Local Indexing
Virtual Lists
Low-Latency Experience

Advantages Comparison

Compared to traditional encrypted social products, WoWo emphasizes the combined advantages of 'identity sovereignty + decentralized distribution + scalable ecosystem' rather than just being a secure chat tool.

Product Story

Traditional social products are built on account systems and centralized servers, where user identities and data are controlled by platforms. WoWo redesigns this logic from the ground up, allowing users to regain control over identity and communication.

Past
Platforms Create Accounts
Platforms Store Data
Platforms Control Communication

WoWo
Users Generate Private Keys
Users Control Identity
Network Handles Transmission
Clients Handle Experience

Transformation
From Platform-Centric → User-Centric
From Account Systems → Key Systems
From Products → Infrastructure

WoWo vs Telegram / Signal / Matrix

WoWo is not just a secure communication tool, but a system-level product with networking, identity, and ecosystem capabilities.

Conclusion
WoWo = Communication Network + Identity System + Application Platform
Not Just a Single Chat Tool
    

Token / Points Model

WoWo has designed a points-based incentive system as the foundation for future Tokens, driving user growth and ecosystem development.

Points Mechanism
Users Register with Referrer Binding
Both Parties Receive Points Rewards

Acquisition Methods
Invite Users
Active Usage
Create Content
Participate in Ecosystem

Points Utility
Upgrade User Levels
Unlock Features
Participate in Future Governance

Token Design
Points Serve as the Distribution Foundation for Future Tokens
Converted Based on Contribution Ratio

Core Value
Early Users Receive Incentives
Form a Growth Flywheel
Bind User Relationship Networks

Goal
Through Incentive Mechanisms
Accelerate Network Effects
Promote Ecosystem Expansion

Why WoWo Does Not Depend on Nostr Relays

Many decentralized projects simply connect to public Relays, but this does not truly solve performance, stability, and user experience problems. From the beginning, WoWo chose to build its own network system to maximize both usability and decentralization.

Core Viewpoint
Decentralized ≠ Using Public Networks
Decentralization = No Single-Point Control + Independent Scalability + Controllable Experience

Why Not Use Public Relays
Uncontrollable (Inconsistent Node Quality)
Unstable (Random Connection Fluctuations)
Cannot Be Optimized (Unable to Tune for Product Experience)

WoWo's Approach
Self-Built Global Node Network
Dynamically Schedule Optimal Connections
Multi-Node Redundancy Synchronization
Automatic Failover

Results
Lower Latency
More Stable Communication
More Consistent User Experience

Core Difference
Nostr Clients: Depend on External Networks
WoWo: Owns Its Own Communication Infrastructure