Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

20 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Walrus Events: Privacy-Preserving Event Infrastructure for Web3

Hackathon Project: This is a submission for the Walrus Haulout Hackathon Demo Video: Watch our presentation

🌟 Vision

Walrus Events explores privacy-preserving event infrastructure for Web3, aiming to provide user-controlled and verifiable event experiences.

πŸš€ Overview

This project experiments with putting users in control of their event data through decentralized storage, zero-knowledge proofs, and blockchain-based verification. The platform attempts to ensure users maintain ownership of their event data while exploring privacy and interoperability concepts.

πŸ”‘ Key Features

πŸ›οΈ User Data Control

  • Data Ownership Experiments: Exploring user control over event data
  • Decentralized Storage: Testing data storage on Walrus network with cryptographic proofs
  • Reputation Portability: Investigating blockchain-based credentials for cross-platform use

πŸ”’ Privacy Exploration

  • Zero-Knowledge Proofs: Experimenting with verification without revealing personal information
  • End-to-End Encryption: Testing encryption methods for user data storage
  • Differential Privacy: Exploring statistical analysis while protecting individual privacy

🧠 Research Systems

  • Markov Chain Analysis: Testing behavior state modeling for reputation systems
  • Federated Learning: Experimenting with personalized recommendations without data collection
  • Privacy-Preserving Discovery: Researching event matching without exposing preferences

⛓️ Web3 Integration

  • Blockchain Verification: Testing on-chain credential verification
  • Decentralized Infrastructure: Exploring censorship resistance through distribution
  • Smart Contract Compliance: Experimenting with programmable privacy rules

πŸ—οΈ Architecture

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                    Frontend Layer                            β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”   β”‚
β”‚  β”‚ React/Vue + TypeScript + Tailwind CSS              β”‚   β”‚
β”‚  β”‚ β€’ Client-side encryption                            β”‚   β”‚
β”‚  β”‚ β€’ ZK proof generation                               β”‚   β”‚
β”‚  β”‚ β€’ Local preference management                       β”‚   β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β”‚
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                    API Layer                                β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”   β”‚
β”‚  β”‚ FastAPI + Python                                    β”‚   β”‚
β”‚  β”‚ β€’ Event discovery API                               β”‚   β”‚
β”‚  β”‚ β€’ ZK verification service                          β”‚   β”‚
β”‚  β”‚ β€’ Reputation calculation (Rust - on-chain)         β”‚   β”‚
β”‚  β”‚ β€’ Seal integration (VDF + mixnet)                  β”‚   β”‚
β”‚  β”‚ β€’ Event discovery engine (collaborative filtering) β”‚   β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β”‚
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                Blockchain Layer (Sui Network)              β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”   β”‚
β”‚  β”‚ Smart Contracts:                                    β”‚   β”‚
β”‚  β”‚ β€’ EventOwnership                                   β”‚   β”‚
β”‚  β”‚ β€’ TicketNFT                                        β”‚   β”‚
β”‚  β”‚ β€’ ReputationCredential                             β”‚   β”‚
β”‚  β”‚ β€’ ComplianceBadge                                   β”‚   β”‚
β”‚  β”‚ β€’ Governance                                       β”‚   β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β”‚
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                Storage & Privacy Layer                     β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”‚
β”‚  β”‚   Walrus     β”‚  β”‚  Seal Network    β”‚  β”‚   IPFS      β”‚  β”‚
β”‚  β”‚ Storage      β”‚  β”‚ (Privacy Layer)  β”‚  β”‚ (Optional)  β”‚  β”‚
β”‚  β”‚ β€’ Encrypted  β”‚  β”‚ β€’ VDF Protection β”‚  β”‚ β€’ Metadata  β”‚  β”‚
β”‚  β”‚   Events     β”‚  β”‚ β€’ Mixnet         β”‚  β”‚ β€’ Public    β”‚  β”‚
β”‚  β”‚ β€’ User Data  β”‚  β”‚ β€’ ZK Accelerationβ”‚  β”‚   Resources β”‚  β”‚
β”‚  β”‚ β€’ Media      β”‚  β”‚                  β”‚  β”‚             β”‚  β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β”‚
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚              Infrastructure Layer                           β”‚
β”‚  PostgreSQL (Metadata) β”‚ Redis (Cache) β”‚ Kafka (Events)   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

πŸ”„ Data Flow Example

Step 1: Organizer Creates Event

Organizer β†’ Fill Event Form β†’ Client-side Encryption
                ↓
        Generate Encrypted Event Object
                ↓
        Upload to Walrus
                ↓
        Receive Storage Commitment
                ↓
        Anchor to Sui Smart Contract
                ↓
        Event Creation Complete βœ…

Step 2: User Discovers Events

User β†’ Local Preferences (Encrypted) β†’ Discovery API
                ↓
        Federated Recommendation: Calculate Match Score
                ↓
        ZK Proof: "These Events Match My Preferences"
                ↓
        Return Encrypted Event List
                ↓
        Local Decryption and Display

Step 3: User Attends Event

User β†’ Select Event β†’ Pay SUI Tokens
                ↓
        Mint Ticket NFT (Soulbound)
                ↓
        Generate ZK Attendance Proof
                ↓
        Present QR Code at Event
                ↓
        Gate Verification of ZK Proof
                ↓
        Entry Granted βœ…

Step 4: Reputation Accumulation

Attendance β†’ System Recording β†’ Update Reputation NFT
                ↓
        Add Achievement (Encrypted)
                ↓
        Update Merkle Tree Root
                ↓
        User Selectively Showcases Achievements
                ↓
        Use ZK Proofs for Privileges on Other Platforms

πŸ” Privacy Approach Comparison

Traditional Platform Walrus Events Research
Platform controls event data Exploring user data control
Plain text user info Testing end-to-end encryption
Platform manages verification Experimenting with zero-knowledge verification
Reputation locked to platform Investigating on-chain reputation portability
Recommendations need data collection Researching privacy-preserving recommendations
Centralized data control Testing decentralized data ownership
Opaque compliance Exploring programmable compliance

πŸ’‘ Research Areas

  1. User Data Control Experiments: Testing approaches where users maintain control over their event data
  2. Markov Chain Reputation Modeling: Researching behavior state transitions for reputation systems
  3. Differential Privacy Applications: Exploring noise addition for privacy protection in statistics
  4. Technology Integration Research: Combining Seal + Sui + Walrus for privacy and storage
  5. Zero-Knowledge Event Discovery: Investigating personalized recommendations without data collection
  6. Federated Learning Applications: Testing local computation with global model benefits
  7. Programmable Compliance: Researching compliance rules in smart contracts
  8. Decentralized Platform Architecture: Exploring censorship resistance through decentralization

🎯 Project Status

This project represents ongoing research and development in privacy-preserving event platforms. The implementation explores various technologies and approaches, with results and findings documented throughout the development process.

πŸ“¦ Current Implementation

  • Experimental System: FastAPI + Sui + Walrus + Seal integration for testing
  • Demo Scenarios: 5 interactive scenarios covering platform workflows
  • Smart Contracts: Event ownership, ticket NFTs, reputation credentials for Sui network
  • Documentation: Architecture design, API documentation, deployment guides
  • Open Source: Complete codebase available for review and contribution

πŸ“ Summary

Walrus Events explores building user-controlled event platforms through decentralized storage, zero-knowledge proofs, Markov chain analysis, differential privacy, and blockchain-based verification. The project aims to research:

  • User Data Control: Exploring user ownership of event data
  • Privacy Protection: Testing zero-knowledge verification methods
  • Reputation Systems: Investigating behavior modeling for reputation
  • Private Recommendations: Researching personalization without data collection
  • Decentralization: Testing distributed infrastructure approaches
  • Compliance Research: Exploring programmable privacy rules
  • Web3 Integration: Experimenting with on-chain verification

This represents ongoing research into privacy-preserving event platform technologies and approaches.

About

Walrus Events is building the event infrastructure for the Web3 era, providing privacy-preserving, user-sovereign, and verifiable event experiences for users!

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages