Milestone 5 – Multi-Token Prediction Support + Token Onboarding Module
Milestone 5 – Multi-Token Prediction Support + Token Onboarding Module
All features in this milestone must operate using the exact same hybrid oracle logic, engine mechanics, and result resolution system as the existing BTC Up/Down prediction game. This milestone is subject to the full scope outlined in the document titled “PULSE FINAL MILESTONES 4–6” referenced in Upwork chat.
⸻
- Multi-Token Prediction Support (Top 10 Cryptos)
Overview:
Users must be able to select which crypto token they want to predict the price movement of (e.g., BTC, ETH, SOL, etc.). All price locking, matching, and resolution must follow the BTC hybrid oracle engine exactly. This is a replication of the BTC game logic for each supported token — only the underlying price feed and token context changes.
⸻
User Side – Prediction Flow:
• Add dropdown or carousel labeled: “Choose Token to Predict”
• Default: BTC
• Options: BTC, ETH, SOL, DOGE, AVAX, LINK, XRP, MATIC, TON, BNB
• Upon token selection, user sees:
• Live price for selected token
• Timer (10–60s)
• Up / Down buttons
• Match with user or HouseBot
• Price is locked based on hybrid oracle (same structure as BTC)
⸻
Admin Panel – Prediction Token Settings:
• Add/Remove tokens (via symbol or Pyth alias)
• Toggle prediction ON/OFF for any token
• Set default token (shown on load)
• View token-specific stats: volume, win/loss, usage
Tech Requirements:
• Use Pyth alias (e.g., Crypto.ETH/USD) or Chainlink feed
• Reuse price.service.ts from BTC setup
• Add selectedPredictionToken param to:
• createGame() payload
• Game DB schema
• Result logic
• UI dynamically updates to reflect selected token (price, ticker, icon)
This milestone is subject to the full scope outlined in the document titled “PULSE FINAL MILESTONES 4–6” referenced in Upwork chat
⸻
- Prediction Game Logic Must Be Identical to BTC Engine
All multi-token prediction games must:
• Use the same hybrid oracle model as BTC (Pyth-based with internal fallback logic)
• Follow identical match, fee, and resolution structure
• Work seamlessly with P2P and HouseBot
• Match timing (10–60s), fee logic, win/loss rules
• Be toggleable in Admin Panel with full stat tracking
⸻
- Token Onboarding Module
Purpose: Allow users to BET using their own SPL tokens on Pulse.
⸻
Admin Functionality:
• Manually add new tokens:
• Token Name, Symbol, SPL Address, Logo (optional)
• Treasury Wallet Address (for initial liquidity)
• Set parameters per token:
• Min/Max Bet Amounts
• Platform Fee %
• Enable/Disable toggle
• Include in:
• Referral Bonus Eligibility (Y/N)
• Ambassador Commissions (Y/N)
• Token Dashboard with:
• Total Bet Volume
• Wins / Losses
• Net Revenue
• Treasury Wallet Balance
• Fees Collected
• Reorder, Edit, or Remove tokens at any time
⚠ This module is strictly for enabling betting with the newly added token. Once approved and live, users can stake that token in prediction games using the exact same BTC game engine.
⸻
User-Side: Creator Submission Portal – “Add Your Token to Pulse”
• Access via /launch-token or modal in token dropdown
• User must submit:
• Token Name, Symbol, SPL Address
• Project Description
• Logo (optional), Telegram/Website/X link
• Submission Requirements:
• Pay submission fee (1–3 SOL, editable by admin)
• Transfer 500,000+ tokens to Pulse treasury (editable by admin)
• Admin notified upon submission → manual review → if approved, token is enabled for betting and appears in the dropdown
⸻
- Universal Token Standards
All supported tokens (BeTyche, RADBRO, SOL, ETH, user-submitted) must meet:
User Side:
• Seamless token selection in-game
• UI updates dynamically (balance, price, ticker, fees)
• Full support for:
• Betting + gameplay
• P2P and HouseBot
• Referral/bonus logic
• Ambassador tracking
Admin Panel:
• Each token includes:
• Visibility in all dashboards (volume, revenue, win/loss)
• Treasury management
• Configurable bet limits and platform fees
• Breakdown in referral, ambassador, and user history panels
System-Level Enforcement:
• All prediction games must follow identical logic and engine structure
• No hard-coded exclusions or token-specific deviations allowed
• All new tokens must be fully compatible with:
• Matchmaking
• Hybrid oracle resolution
• Admin controls
• Referral/ambassador payout systems
Milestoe 6:
2–3 Week Light Post-Launch Support & UI/UX Polish
Scope of Work:
• Live Monitoring: Continuously observe the live Pulse platform for stability, API response times, and wallet performance
• Bug Resolution: Address any post-launch bugs related to gameplay, staking, matchmaking, price locking, or token display
• Wallet & API Support: Fix wallet integration errors or issues with Pyth/Chainlink feeds or third-party dependencies
• Urgent Patching: Be on-call to implement critical hotfixes for uptime or game-breaking issues
• UI/UX Polish:
• Final pass on visual alignment, mobile responsiveness, and animation smoothness
• Clean up text styling, padding/margin inconsistencies, and token dropdown behavior
• Ensure consistent glow effects, icon rendering, and aesthetic alignment with Pulse’s branding
• No New Features: This is strictly a support and polish milestone — no new features are expected or in scope
• Final Sign-Off: Pulse will provide written confirmation once the support window is complete and all issues resolved
Clause:
This milestone is subject to the full scope outlined in the document titled “PULSE FINAL MILESTONES 4–6”, as referenced in Upwork chat.
Milestone 5 – Multi-Token Prediction Support + Token Onboarding Module
Milestone 5 – Multi-Token Prediction Support + Token Onboarding Module
All features in this milestone must operate using the exact same hybrid oracle logic, engine mechanics, and result resolution system as the existing BTC Up/Down prediction game. This milestone is subject to the full scope outlined in the document titled “PULSE FINAL MILESTONES 4–6” referenced in Upwork chat.
⸻
Overview:
Users must be able to select which crypto token they want to predict the price movement of (e.g., BTC, ETH, SOL, etc.). All price locking, matching, and resolution must follow the BTC hybrid oracle engine exactly. This is a replication of the BTC game logic for each supported token — only the underlying price feed and token context changes.
⸻
User Side – Prediction Flow:
• Add dropdown or carousel labeled: “Choose Token to Predict”
• Default: BTC
• Options: BTC, ETH, SOL, DOGE, AVAX, LINK, XRP, MATIC, TON, BNB
• Upon token selection, user sees:
• Live price for selected token
• Timer (10–60s)
• Up / Down buttons
• Match with user or HouseBot
• Price is locked based on hybrid oracle (same structure as BTC)
⸻
Admin Panel – Prediction Token Settings:
• Add/Remove tokens (via symbol or Pyth alias)
• Toggle prediction ON/OFF for any token
• Set default token (shown on load)
• View token-specific stats: volume, win/loss, usage
Tech Requirements:
• Use Pyth alias (e.g., Crypto.ETH/USD) or Chainlink feed
• Reuse price.service.ts from BTC setup
• Add selectedPredictionToken param to:
• createGame() payload
• Game DB schema
• Result logic
• UI dynamically updates to reflect selected token (price, ticker, icon)
This milestone is subject to the full scope outlined in the document titled “PULSE FINAL MILESTONES 4–6” referenced in Upwork chat
⸻
All multi-token prediction games must:
• Use the same hybrid oracle model as BTC (Pyth-based with internal fallback logic)
• Follow identical match, fee, and resolution structure
• Work seamlessly with P2P and HouseBot
• Match timing (10–60s), fee logic, win/loss rules
• Be toggleable in Admin Panel with full stat tracking
⸻
Purpose: Allow users to BET using their own SPL tokens on Pulse.
⸻
Admin Functionality:
• Manually add new tokens:
• Token Name, Symbol, SPL Address, Logo (optional)
• Treasury Wallet Address (for initial liquidity)
• Set parameters per token:
• Min/Max Bet Amounts
• Platform Fee %
• Enable/Disable toggle
• Include in:
• Referral Bonus Eligibility (Y/N)
• Ambassador Commissions (Y/N)
• Token Dashboard with:
• Total Bet Volume
• Wins / Losses
• Net Revenue
• Treasury Wallet Balance
• Fees Collected
• Reorder, Edit, or Remove tokens at any time
⚠ This module is strictly for enabling betting with the newly added token. Once approved and live, users can stake that token in prediction games using the exact same BTC game engine.
⸻
User-Side: Creator Submission Portal – “Add Your Token to Pulse”
• Access via /launch-token or modal in token dropdown
• User must submit:
• Token Name, Symbol, SPL Address
• Project Description
• Logo (optional), Telegram/Website/X link
• Submission Requirements:
• Pay submission fee (1–3 SOL, editable by admin)
• Transfer 500,000+ tokens to Pulse treasury (editable by admin)
• Admin notified upon submission → manual review → if approved, token is enabled for betting and appears in the dropdown
⸻
All supported tokens (BeTyche, RADBRO, SOL, ETH, user-submitted) must meet:
User Side:
• Seamless token selection in-game
• UI updates dynamically (balance, price, ticker, fees)
• Full support for:
• Betting + gameplay
• P2P and HouseBot
• Referral/bonus logic
• Ambassador tracking
Admin Panel:
• Each token includes:
• Visibility in all dashboards (volume, revenue, win/loss)
• Treasury management
• Configurable bet limits and platform fees
• Breakdown in referral, ambassador, and user history panels
System-Level Enforcement:
• All prediction games must follow identical logic and engine structure
• No hard-coded exclusions or token-specific deviations allowed
• All new tokens must be fully compatible with:
• Matchmaking
• Hybrid oracle resolution
• Admin controls
• Referral/ambassador payout systems
Milestoe 6:
2–3 Week Light Post-Launch Support & UI/UX Polish
Scope of Work:
• Live Monitoring: Continuously observe the live Pulse platform for stability, API response times, and wallet performance
• Bug Resolution: Address any post-launch bugs related to gameplay, staking, matchmaking, price locking, or token display
• Wallet & API Support: Fix wallet integration errors or issues with Pyth/Chainlink feeds or third-party dependencies
• Urgent Patching: Be on-call to implement critical hotfixes for uptime or game-breaking issues
• UI/UX Polish:
• Final pass on visual alignment, mobile responsiveness, and animation smoothness
• Clean up text styling, padding/margin inconsistencies, and token dropdown behavior
• Ensure consistent glow effects, icon rendering, and aesthetic alignment with Pulse’s branding
• No New Features: This is strictly a support and polish milestone — no new features are expected or in scope
• Final Sign-Off: Pulse will provide written confirmation once the support window is complete and all issues resolved
Clause:
This milestone is subject to the full scope outlined in the document titled “PULSE FINAL MILESTONES 4–6”, as referenced in Upwork chat.