diff --git a/TEMPLATE.md b/TEMPLATE.md index 860c2f47..5d0c6ad8 100644 --- a/TEMPLATE.md +++ b/TEMPLATE.md @@ -1,67 +1,203 @@ -# vApp Submission: [Your Project Name] +# Samba-SocialTicket vApp Proposal -## Verification -```yaml -github_username: "your-username" -discord_id: "123456789012345678" -timestamp: "2025-01-15" -``` - -## Developer -- **Name**: Your Name -- **GitHub**: @your-username -- **Discord**: username#1234 -- **Experience**: Brief background +## Project Information -## Project +**Project Name:** Samba-SocialTicket +**Category:** social +**GitHub Username:** [pichanesantana-cloud] +**Discord ID:** [@r3nato7732] +**Team Size:** 3 (Developer) -### Name & Category -- **Project**: Your vApp Name -- **Category**: identity/defi/social/gaming/infrastructure/other +## Project Overview ### Description -What problem does your vApp solve? What does it do? - -### SL Integration -How will you use Soundness Layer? What specific SL features? - -## Technical - -### Architecture -High-level system design and approach - -### Stack -- **Frontend**: React/Vue/etc -- **Backend**: Rust/Node.js/Python/etc -- **Blockchain**: SL + others -- **Storage**: Database/WALRUS/IPFS/etc - -### Features -1. Core feature 1 -2. Core feature 2 -3. Core feature 3 - -## Timeline +Samba-SocialTicket is a decentralized social ticketing platform that leverages blockchain technology to create transparent, secure, and community-driven event management. The platform enables users to create, distribute, and manage event tickets while building social reputation through verified attendance and community interactions. + +### Key Features +- **Decentralized Event Creation:** Users can create events with smart contract-backed tickets +- **Social Verification:** Attendance verification through community consensus and cryptographic proofs +- **Reputation System:** Build and maintain social reputation based on event history and community interactions +- **NFT Ticketing:** Each ticket is an NFT with unique properties and transferability rules +- **Community Governance:** Event organizers and attendees participate in dispute resolution + +## Technical Architecture + +### Core Components + +#### 1. Smart Contracts (Move Language) +```move +// Simplified contract structure +module samba_tickets::event_manager { + struct Event has key, store { + id: UID, + creator: address, + title: String, + description: String, + max_capacity: u64, + ticket_price: u64, + event_date: u64, + is_active: bool, + } + + struct Ticket has key, store { + id: UID, + event_id: ID, + owner: address, + attendance_verified: bool, + transfer_count: u8, + } + + struct UserReputation has key { + id: UID, + user: address, + events_attended: u64, + events_created: u64, + reputation_score: u64, + } +} +``` -### PoC (2-4 weeks) -- [ ] Basic functionality -- [ ] SL integration -- [ ] Simple UI +#### 2. Soundness Layer Integration -### MVP (4-8 weeks) -- [ ] Full features -- [ ] Production ready -- [ ] User testing +**Data Storage:** +Utilizaremos o Walrus para armazenamento de dados off-chain, onde os usuários podem submeter requests ao Soundness Layer chamando a função new_proof no smart contract Move -## Innovation -What makes this unique? Why will people use it? +**Proof Submission:** +- Event metadata stored on Walrus +- Attendance proofs submitted via blob ID to Soundness Layer +- Zero-knowledge proofs for privacy-preserving reputation calculations -## Contact -Preferred contact method and where you'll share updates. +**Technical Integration Points:** +1. **Event Metadata Storage:** Large event data (images, descriptions, media) stored on Walrus +2. **Attendance Verification:** ZK proofs submitted to Soundness Layer for attendance verification +3. **Reputation Calculations:** Privacy-preserving reputation scoring using zero-knowledge proofs +4. **Data Integrity:** All event and ticket data verified through Soundness Layer's verification system +### Architecture Flow +``` +User Creates Event → Store metadata on Walrus → Deploy Move contract on Sui + ↓ +Ticket Purchase → NFT Minting → Store transaction proof on Soundness Layer + ↓ +Event Attendance → ZK Proof Generation → Submit to Soundness Layer + ↓ +Reputation Update → Privacy-preserving calculation → Update on-chain reputation +``` -**Checklist before submitting:** -- [ ] All fields completed -- [ ] GitHub username matches PR author -- [ ] SL integration explained -- [ ] Timeline is realistic +## Development Roadmap + +### Phase 1: Foundation (Weeks 1-4) +- [x] Basic project structure setup +- [x] Git repository initialization +- [ ] Move smart contracts development +- [ ] Soundness Layer CLI integration +- [ ] Basic event creation functionality + +### Phase 2: Core Features (Weeks 5-8) +- [ ] NFT ticketing system implementation +- [ ] Walrus integration for metadata storage +- [ ] ZK proof generation for attendance +- [ ] Basic reputation system +- [ ] Frontend development (React/Next.js) + +### Phase 3: Advanced Features (Weeks 9-12) +- [ ] Community governance mechanisms +- [ ] Advanced reputation algorithms +- [ ] Mobile-responsive design +- [ ] Payment integration +- [ ] Testing and optimization + +### Phase 4: Testnet Deployment (Weeks 13-16) +- [ ] Soundness Layer testnet deployment +- [ ] Comprehensive testing +- [ ] User feedback integration +- [ ] Performance optimization +- [ ] Security auditing + +## Business Model & Impact + +### Target Market +- Event organizers (concerts, conferences, workshops) +- Community builders and social groups +- Verification-required events (professional conferences, exclusive gatherings) + +### Social Impact +- **Transparency:** All ticket sales and transfers are publicly verifiable +- **Anti-Fraud:** Blockchain-based tickets prevent counterfeiting +- **Community Building:** Reputation system encourages positive community participation +- **Decentralization:** Reduces dependency on centralized ticketing monopolies + +## Technical Specifications + +### Frontend +- **Framework:** React/Next.js +- **Styling:** Tailwind CSS +- **Wallet Integration:** Sui Wallet, Ethos Wallet +- **State Management:** Zustand + +### Backend/Blockchain +- **Smart Contracts:** Move language on Sui Network +- **Data Storage:** Walrus Protocol via Soundness Layer +- **Verification:** Zero-Knowledge Proofs +- **Authentication:** Sui Wallet signatures + +### Infrastructure +- **Hosting:** Vercel/Netlify for frontend +- **IPFS:** Backup metadata storage +- **API:** Node.js/Express for auxiliary services + +## Proof of Concept Features + +### MVP (Minimum Viable Product) +1. Create simple events with basic information +2. Mint NFT tickets with unique identifiers +3. Verify ticket ownership on-chain +4. Basic attendance marking system +5. Simple reputation display + +### Soundness Layer Specific Features +- Event metadata storage on Walrus +- ZK proof submission for attendance verification +- Privacy-preserving reputation calculations +- Blob ID-based proof verification + +## Testing Strategy + +1. **Unit Tests:** Smart contract functionality testing +2. **Integration Tests:** Soundness Layer interaction testing +3. **User Acceptance Tests:** Community-driven testing +4. **Security Audits:** Smart contract security review +5. **Performance Tests:** Scalability and gas optimization + +## Resources Needed + +### Technical Resources +- Sui testnet tokens for smart contract deployment +- Soundness Layer testnet access +- Development tools and frameworks + +### Community Resources +- Beta testers from event management communities +- Feedback from Web3 social platform users +- Integration partners for initial events + +## Success Metrics + +- **Technical:** Successful deployment and interaction with Soundness Layer +- **Usage:** 10+ test events created during testnet phase +- **Community:** 50+ active beta testers +- **Performance:** <2s transaction confirmation times +- **Security:** Zero critical vulnerabilities in security audit + +## Long-term Vision + +Samba-SocialTicket aims to become the leading decentralized social ticketing platform, leveraging Soundness Layer's verification capabilities to create a trust-first ecosystem for event management. Our goal is to democratize event access while maintaining security and transparency through blockchain technology. + +## Additional Information + +**Repository:** https://github.com/pichanesantana-cloud/Samba-SocialTicket +**Demo:** [I'm resuming my programming studies, and now with this opportunity to build at SUI, I'm very excited. +I'm from Brazil, and Brazil's first bootcamp is taking place here. +My team and I started building this project. +We'd like to join the team and build even more.] +**Contact:** [pichane.santana@gmail.com] diff --git a/submissions/social/pichane-cloud.md b/submissions/social/pichane-cloud.md new file mode 100644 index 00000000..5d0c6ad8 --- /dev/null +++ b/submissions/social/pichane-cloud.md @@ -0,0 +1,203 @@ +# Samba-SocialTicket vApp Proposal + +## Project Information + +**Project Name:** Samba-SocialTicket +**Category:** social +**GitHub Username:** [pichanesantana-cloud] +**Discord ID:** [@r3nato7732] +**Team Size:** 3 (Developer) + +## Project Overview + +### Description +Samba-SocialTicket is a decentralized social ticketing platform that leverages blockchain technology to create transparent, secure, and community-driven event management. The platform enables users to create, distribute, and manage event tickets while building social reputation through verified attendance and community interactions. + +### Key Features +- **Decentralized Event Creation:** Users can create events with smart contract-backed tickets +- **Social Verification:** Attendance verification through community consensus and cryptographic proofs +- **Reputation System:** Build and maintain social reputation based on event history and community interactions +- **NFT Ticketing:** Each ticket is an NFT with unique properties and transferability rules +- **Community Governance:** Event organizers and attendees participate in dispute resolution + +## Technical Architecture + +### Core Components + +#### 1. Smart Contracts (Move Language) +```move +// Simplified contract structure +module samba_tickets::event_manager { + struct Event has key, store { + id: UID, + creator: address, + title: String, + description: String, + max_capacity: u64, + ticket_price: u64, + event_date: u64, + is_active: bool, + } + + struct Ticket has key, store { + id: UID, + event_id: ID, + owner: address, + attendance_verified: bool, + transfer_count: u8, + } + + struct UserReputation has key { + id: UID, + user: address, + events_attended: u64, + events_created: u64, + reputation_score: u64, + } +} +``` + +#### 2. Soundness Layer Integration + +**Data Storage:** +Utilizaremos o Walrus para armazenamento de dados off-chain, onde os usuários podem submeter requests ao Soundness Layer chamando a função new_proof no smart contract Move + +**Proof Submission:** +- Event metadata stored on Walrus +- Attendance proofs submitted via blob ID to Soundness Layer +- Zero-knowledge proofs for privacy-preserving reputation calculations + +**Technical Integration Points:** +1. **Event Metadata Storage:** Large event data (images, descriptions, media) stored on Walrus +2. **Attendance Verification:** ZK proofs submitted to Soundness Layer for attendance verification +3. **Reputation Calculations:** Privacy-preserving reputation scoring using zero-knowledge proofs +4. **Data Integrity:** All event and ticket data verified through Soundness Layer's verification system + +### Architecture Flow +``` +User Creates Event → Store metadata on Walrus → Deploy Move contract on Sui + ↓ +Ticket Purchase → NFT Minting → Store transaction proof on Soundness Layer + ↓ +Event Attendance → ZK Proof Generation → Submit to Soundness Layer + ↓ +Reputation Update → Privacy-preserving calculation → Update on-chain reputation +``` + +## Development Roadmap + +### Phase 1: Foundation (Weeks 1-4) +- [x] Basic project structure setup +- [x] Git repository initialization +- [ ] Move smart contracts development +- [ ] Soundness Layer CLI integration +- [ ] Basic event creation functionality + +### Phase 2: Core Features (Weeks 5-8) +- [ ] NFT ticketing system implementation +- [ ] Walrus integration for metadata storage +- [ ] ZK proof generation for attendance +- [ ] Basic reputation system +- [ ] Frontend development (React/Next.js) + +### Phase 3: Advanced Features (Weeks 9-12) +- [ ] Community governance mechanisms +- [ ] Advanced reputation algorithms +- [ ] Mobile-responsive design +- [ ] Payment integration +- [ ] Testing and optimization + +### Phase 4: Testnet Deployment (Weeks 13-16) +- [ ] Soundness Layer testnet deployment +- [ ] Comprehensive testing +- [ ] User feedback integration +- [ ] Performance optimization +- [ ] Security auditing + +## Business Model & Impact + +### Target Market +- Event organizers (concerts, conferences, workshops) +- Community builders and social groups +- Verification-required events (professional conferences, exclusive gatherings) + +### Social Impact +- **Transparency:** All ticket sales and transfers are publicly verifiable +- **Anti-Fraud:** Blockchain-based tickets prevent counterfeiting +- **Community Building:** Reputation system encourages positive community participation +- **Decentralization:** Reduces dependency on centralized ticketing monopolies + +## Technical Specifications + +### Frontend +- **Framework:** React/Next.js +- **Styling:** Tailwind CSS +- **Wallet Integration:** Sui Wallet, Ethos Wallet +- **State Management:** Zustand + +### Backend/Blockchain +- **Smart Contracts:** Move language on Sui Network +- **Data Storage:** Walrus Protocol via Soundness Layer +- **Verification:** Zero-Knowledge Proofs +- **Authentication:** Sui Wallet signatures + +### Infrastructure +- **Hosting:** Vercel/Netlify for frontend +- **IPFS:** Backup metadata storage +- **API:** Node.js/Express for auxiliary services + +## Proof of Concept Features + +### MVP (Minimum Viable Product) +1. Create simple events with basic information +2. Mint NFT tickets with unique identifiers +3. Verify ticket ownership on-chain +4. Basic attendance marking system +5. Simple reputation display + +### Soundness Layer Specific Features +- Event metadata storage on Walrus +- ZK proof submission for attendance verification +- Privacy-preserving reputation calculations +- Blob ID-based proof verification + +## Testing Strategy + +1. **Unit Tests:** Smart contract functionality testing +2. **Integration Tests:** Soundness Layer interaction testing +3. **User Acceptance Tests:** Community-driven testing +4. **Security Audits:** Smart contract security review +5. **Performance Tests:** Scalability and gas optimization + +## Resources Needed + +### Technical Resources +- Sui testnet tokens for smart contract deployment +- Soundness Layer testnet access +- Development tools and frameworks + +### Community Resources +- Beta testers from event management communities +- Feedback from Web3 social platform users +- Integration partners for initial events + +## Success Metrics + +- **Technical:** Successful deployment and interaction with Soundness Layer +- **Usage:** 10+ test events created during testnet phase +- **Community:** 50+ active beta testers +- **Performance:** <2s transaction confirmation times +- **Security:** Zero critical vulnerabilities in security audit + +## Long-term Vision + +Samba-SocialTicket aims to become the leading decentralized social ticketing platform, leveraging Soundness Layer's verification capabilities to create a trust-first ecosystem for event management. Our goal is to democratize event access while maintaining security and transparency through blockchain technology. + +## Additional Information + +**Repository:** https://github.com/pichanesantana-cloud/Samba-SocialTicket +**Demo:** [I'm resuming my programming studies, and now with this opportunity to build at SUI, I'm very excited. +I'm from Brazil, and Brazil's first bootcamp is taking place here. +My team and I started building this project. +We'd like to join the team and build even more.] +**Contact:** [pichane.santana@gmail.com]