Open
Conversation
…ct (#1) * feat: Complete blockchain integration with SimpleBadge contract 🚀 Major Features Added: - Deployed SimpleBadge ERC1155 contract to Celo Alfajores (0x7Ed5CC0cf0B0532b52024a0DDa8fAE24C6F66dc3) - Real on-chain enrollment system replacing placeholder alerts - ERC1155 metadata API for course badges (/api/metadata/milestone/[tokenId]) 🔧 Smart Contract Integration: - SimpleBadge.sol contract with claim functionality - React hooks for blockchain interactions (useSimpleBadge.ts) - Wagmi/Viem integration for wallet connections - Dynamic Web3EnrollPanel for client-side blockchain interactions 🎨 UI/UX Improvements: - Enhanced enrollment UI with loading states - Real-time transaction tracking and feedback - Success/error handling with blockchain explorer links - SSR-compatible Web3 components (fixes WagmiProvider issues) 📋 API & Backend: - Metadata endpoints for NFT compliance - Course token ID mapping (desarrollo-dapps = token 1) - Environment variable configuration for contract addresses 🏗️ Infrastructure: - Hardhat compilation fixes (ESM compatibility) - Updated Providers component structure - Fixed ThemeProvider conflicts - Production-ready environment setup ✅ Verified Working: - Contract deployment and testing completed - Enrollment flow functional end-to-end - SSR/hydration issues resolved - Ready for Vercel deployment * chore: Add Vercel deployment configuration and comprehensive guide 📦 Deployment Setup: - Enhanced vercel.json with production optimizations - Security headers and CORS configuration - Regional deployment settings (cle1) - API function timeout configuration 📚 Documentation: - Complete Vercel deployment guide with step-by-step instructions - Production environment variables template - SSL and security configuration details - Troubleshooting and monitoring guides 🔧 CLI Integration: - Vercel CLI successfully installed and authenticated - Ready for deployment with proper build commands - Prisma generation included in build process ✅ Production Ready: - Environment variable templates provided - Security headers configured - Database SSL support documented - Health check endpoints configured * docs: Add deployment completion summary - Document all blockchain integration work completed - Detail Vercel deployment readiness status - Provide comprehensive next steps guide - Include success metrics and verification steps
…t on create for Category, Level, Instructor, Course, Module, Lesson
…on in admin courses API
…ess creation in progress API
…le, Course, Lesson)
…and excluding config files from compilation - Fix TypeScript error in auth middleware by converting null to undefined - Exclude Playwright and Jest configs from TypeScript compilation - Build now passes successfully locally
- Disable todos page temporarily to prevent Supabase build errors - Make academy generateStaticParams more robust with database fallbacks - Remove SSL certificate path dependency for Vercel deployment - Build now succeeds locally and should work on Vercel
- Configure SSL certificate from environment variable in Vercel - Write SSL cert to temp file for Prisma in production - Keep SSL security while making it work in serverless environment - Update DATABASE_URL to use SSL without file path dependency
…API error handling, and seed admin data
…ation for /api/admin routes and improve error handling
…int violation by deleting lessons before modules, add proper slug validation for updates, and improve slug generation with timestamp suffix to avoid duplicates
…eserved word conflict
…alidate, and redirect to list after update
…erview with delay, and show helpful success messages
- Implement dynamic token ID generation from course database IDs - Add comprehensive deployment guide (DEPLOYMENT_GUIDE.md) - Document NFT solution architecture (DYNAMIC_NFT_SOLUTION.md) - Update SimpleBadge hook to use dynamic token IDs - Enhance metadata API to fetch course data from database - Update enrollment panel with dynamic token support - Complete pre-deployment testing and verification
- Add address trimming and validation in useSimpleBadge hook - Prevent invalid addresses with trailing spaces - Add format validation (0x prefix and 42 char length) - Add deployment monitoring scripts with comprehensive features - Create deploy-and-monitor.sh for automated deployment workflow - Create monitor-deployment.sh for real-time deployment tracking - Add detailed documentation for deployment scripts
- Create PRODUCTION_STATUS.md as single source of truth (85/100 score) - Update README.md with current tech stack and features - Archive outdated production assessment docs (5 files) - Remove redundant deployment summaries (3 files) - Keep only current and essential documentation (6 core files) - Add comprehensive cleanup plan and documentation index - Improve documentation hierarchy and discoverability Files Kept (6): - README.md (updated) - PRODUCTION_STATUS.md (new) - DEPLOYMENT_GUIDE.md - DEPLOYMENT_SUMMARY.md - DYNAMIC_NFT_SOLUTION.md - scripts/README.md Files Archived (5): - PRODUCTION_READINESS_ASSESSMENT.md - PRODUCTION_READINESS_CHECKLIST.md - PRODUCTION_READINESS_UPDATE_2025.md - FUNCTIONALITY_ASSESSMENT_2025.md - HARDHAT_DEPLOYMENT_GUIDE.md Files Removed (3): - DEPLOYMENT_COMPLETE_SUMMARY.md - DEPLOYMENT_SETUP_SUMMARY.md - VERCEL_DEPLOYMENT_GUIDE.md
- Add CoursePaywall component with beautiful locked content UI - Create LessonAccessWrapper for client-side enrollment verification - Implement enrollment-verification utility for server-side checks - Integrate NFT badge verification into course lesson pages - Add three paywall states: WALLET_NOT_CONNECTED, NOT_ENROLLED, LOADING - Display enrollment benefits and direct enrollment action - Real-time verification using Wagmi hooks - Smooth hydration handling to prevent flash of content - Free enrollment with only gas fees (~-zsh.001 USD) - Complete documentation in COURSE_PAYWALL.md Features: - 🔒 Lessons locked until NFT badge claimed - ✨ Beautiful paywall UI with clear messaging - 🚀 One-click enrollment from paywall - 🔄 Real-time access updates - 📊 Verifiable on-chain enrollment - 🎯 Course overview remains public - 🛡️ Client-side verification (fast, no server load) - 📱 Mobile-friendly paywall design Benefits: - Decentralized enrollment system - No personal info required (wallet-based) - Permanent proof of enrollment - Easy to extend for paid courses - Fraud prevention through blockchain Security: Client-side verification (can add server-side later)
… dashboard - Fix CourseCurriculum to pass 0-based moduleIndex (module.index - 1) to components - Ensures consistency with CourseProgressDashboard which already uses 0-based indices - Resolves issue where completing 'module 2' showed completion for 'module 1' in UI - Both components now consistently pass 0-based indices to hooks/context - ModuleCompletionContext correctly converts 0-based to 1-based for contract calls
- Fix TypeScript error in CourseProgressDashboard: handle null smartAccountAddress - Fix TypeScript error in ModuleProgress: handle null smartAccountAddress - Fix TypeScript error in PrivyLogin: access user.email.address property correctly - Fix ESLint hook dependency warnings in useZeroDevEnrollment: - Remove unnecessary CONTRACT_ADDRESS dependencies (outer scope values) - Build now compiles successfully with no TypeScript or ESLint errors - Only remaining warning is jsx-a11y/alt-text in MdxComponents.tsx (non-blocking)
✅ Successfully deployed OptimizedSimpleBadge contract: - Contract Address: 0xf8CA094fd88F259Df35e0B8a9f38Df8f4F28F336 - Network: Celo Mainnet (Chain ID: 42220) - Gas Used: 387,804 - Deployment Cost: 0.0097 CELO (~-zsh.01 USD) - Transaction: 0xc99c36bb9543f810c9d9b51011968d1ae7faeacce3188c9145698c1633a92397 📋 Changes: - Add mainnet deployment script (deploy-optimized-mainnet.js) - Update .env.local with mainnet contract address - Save deployment details in deployments/optimized-mainnet.json - Contract verified and ready for production use 🔗 Explorer: https://celoscan.io/address/0xf8CA094fd88F259Df35e0B8a9f38Df8f4F28F336 Next steps: Update contract config to use mainnet address in production
…innet 🔧 Updated contract configuration to be network-aware: - Modified optimized-badge-config.ts to support both Alfajores (44787) and Mainnet (42220) - Added dynamic contract address resolution based on current chain ID - Updated network configurations for both networks 📝 Updated hooks to be chain-aware: - useModuleCompletion: Now uses dynamic contract config based on current chain - useSimpleBadge: Updated all read/write operations to use correct contract per chain - Added useContractConfig() helper to get current chain's contract configuration 🌐 Network support: - Alfajores (Testnet): 0x4193D2f9Bf93495d4665C485A3B8AadAF78CDf29 - Celo Mainnet: 0xf8CA094fd88F259Df35e0B8a9f38Df8f4F28F336 ✅ Frontend now automatically switches between contracts based on user's network 🚀 Ready for mainnet deployment and production use
🔧 Paymaster Configuration: - Updated paymaster.ts to support both Alfajores (44787) and Mainnet (42220) - Added network-specific paymaster configs with different gas limits - Added sponsored contract addresses for both networks: - Alfajores: 0x4193D2f9Bf93495d4665C485A3B8AadAF78CDf29 - Mainnet: 0xf8CA094fd88F259Df35e0B8a9f38Df8f4F28F336 - Added getPaymasterConfig() function for chain-specific configuration 🚀 ZeroDev Smart Account Updates: - Updated ZeroDevSmartWalletProvider to be chain-aware - Added getChainConfig() helper to support both Celo networks - Smart account creation now uses current user's connected network - Bundler and paymaster URLs adapt to current chain ID - Provider reinitializes when user switches networks 💰 Environment Variables: - Added paymaster configuration placeholders in .env.local - Support for custom paymaster addresses and service URLs - Optional configuration (ZeroDev provides defaults) ✅ Features: - Automatic network detection and paymaster selection - Sponsored transactions work on both testnet and mainnet - Users can switch networks and paymasters adapt automatically - Mainnet paymaster ready to sponsor enrollment/completion transactions 🌐 Network Support: - Alfajores: Full paymaster support for testing - Mainnet: Production-ready paymaster configuration - Seamless network switching with proper paymaster selection
🔧 Critical Fix - Contexts now query correct network contracts: 📝 EnrollmentContext: - Updated to use getOptimizedContractConfig(chainId) instead of hardcoded config - Enrollment reads and writes now use correct contract per network - Added chain ID logging for debugging - Smart account enrollment now targets mainnet contract when on mainnet 🚀 ModuleCompletionContext: - Updated both wallet and sponsored transaction methods - Module completion reads/writes now use correct contract per network - Added chain ID logging for transaction tracking - Both regular and sponsored module completion work on mainnet ✅ Key Changes: - EnrollmentContext: Uses dynamic contract based on current chain - ModuleCompletionContext: Uses dynamic contract for both transaction types - Added console logging to track which contract address is being used - Maintains backward compatibility with existing components 🌐 Network Support: - Alfajores (44787): Uses 0x4193D2f9Bf93495d4665C485A3B8AadAF78CDf29 - Mainnet (42220): Uses 0xf8CA094fd88F259Df35e0B8a9f38Df8f4F28F336 🎯 Impact: - Frontend now queries enrollment/progress from correct mainnet contract - Users on mainnet will see accurate enrollment and module completion data - Sponsored transactions target correct contract per network
✅ Mainnet-First Configuration: - Fixed Privy Provider: Changed from celoAlfajores to celo mainnet - Updated wagmi config: Only Celo mainnet supported (42220) - Contract config: All functions default to mainnet - ZeroDev provider: Forced to mainnet chain ✅ Smart Contract Integration: - OptimizedSimpleBadge deployed on mainnet: 0xf8CA094fd88F259Df35e0B8a9f38Df8f4F28F336 - All enrollment/module completion goes through mainnet contract - ERC-4337 sponsored transactions working on mainnet - Direct RPC client for guaranteed mainnet reads ✅ Key Fixes: - EnrollmentContext: Uses direct mainnet checks - ZeroDevSmartWalletProvider: Forced mainnet chain config - Contract reads: Direct to https://forno.celo.org - Explorer links: Point to celoscan.io (mainnet) ✅ Enhanced Features: - Direct mainnet read hooks (useDirectMainnetReads.ts) - Mainnet debug components for runtime verification - Comprehensive mainnet integration guide - Debug scripts for contract verification ✅ Verified Working: - Contract exists on mainnet with code - Enrollment transactions successful via ERC-4337 - Smart account enrollments recorded on-chain - All reads/writes target mainnet contract 📋 Architecture: - Production: All users → Celo Mainnet (42220) - Sponsored transactions: ZeroDev + paymaster - Contract: OptimizedSimpleBadge on mainnet - Explorer: CeloScan mainnet integration This completes the transition from testnet to production mainnet deployment.
- Updated wagmi config with proper mainnet RPC transport - Enhanced ContractAddressDebug component for better mainnet verification - Ensured all network configurations point to Celo mainnet consistently
- GET /api/courses/[slug]/enrollment-count
- POST /api/courses/[slug]/sync-enrollment (body: { address })
Everything else matches origin/main.
… sync - Add alt attribute to MDX img component - Stop creating users in sync-enrollment; require existing user and generate enrollment id
- Fetch /api/courses/[slug]/enrollment-count client-side - Feed learners into CourseHeader/EnrollPanel/Web3EnrollPanel
- Web3EnrollPanel: POST /api/courses/[slug]/sync-enrollment after success - CourseDetailClient: refetch count when enrollmentSuccess changes - Academy index: use Prisma _count to show CourseEnrollment counts
- Fetch count on mount, refetch on enroll success - Auto-sync to /api/courses/[slug]/sync-enrollment when on-chain enrolled - Provide enrollmentCount to consumers
…nd add immediate + retry DB sync from context for live counts
…rseCard fetches count client-side for list without reload
…king didSync after context sync
|
@cultureic is attempting to deploy a commit to the CeloMexico's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.