[Service] Limited Time Drop Contract Service for StarShop Frontend

[aguilar1x]

🎯 Objective

Develop a comprehensive TypeScript service layer for the Limited Time Drop Contract that manages time-sensitive product drops, access control, and exclusive offers within the StarShop marketplace.

---

🏗 Service Structure

src/shared/services/limited_time_drop/
  limited_drop.service.ts          // Main service class
  types/
    drop.types.ts                 // TypeScript interfaces
    access.types.ts               // Access control types
  utils/
    drop.utils.ts                 // Helper functions
  constants/
    drop.constants.ts             // Contract addresses, error codes

---

🗂 Requirements

1. Drop Management

• createDrop(config) - Create new limited-time drop
• getDrop(dropId) - Get drop details
• updateDrop(dropId, updates) - Update drop configuration
• cancelDrop(dropId) - Cancel active drop

2. Access Control

• checkAccess(dropId, user) - Check user access eligibility
• grantAccess(dropId, user) - Grant access to user
• revokeAccess(dropId, user) - Revoke user access
• getAccessList(dropId) - Get users with access

3. Drop Operations

• participateInDrop(dropId) - User participation
• trackParticipation(dropId) - Track participation metrics
• getDropStatus(dropId) - Get current drop status

4. Time Management

• isDropActive(dropId) - Check if drop is currently active
• getTimeRemaining(dropId) - Get remaining time
• extendDrop(dropId, duration) - Extend drop duration

---

[zintarh]

Hi @aguilar1x I would love to work on this

[armandocodecr]

Hi team 👋,

I’d love to take on the development of the TypeScript service layer for the Limited Time Drop Contract within the StarShop ecosystem.

Here’s how I’d approach it:

🧱 Modular Architecture
• Implement the full service in limited_drop.service.ts, exposing clean methods for managing drops, access control, participation, and time-based logic.
• Leverage clear typings under types/ for drops and access management to ensure consistency across the app.
• Isolate contract constants and reusable values under constants/, and extract shared logic into helper functions within utils/.

🔒 Access & Participation
• Implement granular access control via grantAccess, revokeAccess, and checkAccess, with support for access lists per drop.
• Support participation tracking and status checking (participateInDrop, getDropStatus) with proper validation.

⏱ Time-Sensitive Logic
• Integrate time utilities to check whether a drop is active, get remaining time, or extend a drop’s duration, all while keeping logic clean and reusable.

⚙️ Scalable & Maintainable Code
• Follow best practices for service composition, separation of concerns, and future extensibility for integration with smart contracts and frontend components.

Let me know if I can move forward with this — happy to deliver a clean, well-structured, and production-ready service layer. 🚀

[komyunghan]

Happy to implement this service.

I'll create src/services/limitedTimeDrop.ts covering create drop, purchase, and query remaining supply + time left. I'll add countdown logic in the hook and expose isActive, remainingSupply, and timeLeft as reactive state.

ETA: 2 days.