RPS Labs
  • 👋Welcome to RPS Labs
  • 📋Table of Contents
  • Overview
    • 💡What we do
  • ✌️Using Lotto SDK
    • For Users
      • Case Studies
    • For Developers
      • 💸Pricing
      • 🧰SDK Docs
        • Getting Started
        • UI Components
        • Hooks
      • 💻API Docs
        • Raffle info
        • Users
        • Pot
      • 📃Smart Contracts
        • RPS Raffle
        • RPS Router
        • Configurable Raffle Parameters
        • Fund Management
        • Deployment Guide
        • Security Considerations
      • ⛓️Supported Chains
  • RESOURCES
    • 🙋‍♂️Contact & Social Links
    • ❓FAQ
    • 🖌️Brand Assets
  • COMING SOON
    • DailyGM!
    • Hypercluster
Powered by GitBook
On this page
  • Overview
  • RPS: The Raffle Engine
  • RPSRouter: User-Focused Entry Point
  1. Using Lotto SDK
  2. For Developers

Smart Contracts

Overview

This integration comprises several on-chain components, each designed to serve a specific function within the raffle ecosystem:

RPS: The Raffle Engine

The RPS Raffle contract is the heart of the raffle system. It serves multiple functions:

  • Ticket Generation: Dynamically creates tickets for participants entering the raffle.

  • Raffle Fund Management: Securely holds the funds accumulated during the raffle.

  • Raffle Information: Maintains a comprehensive record of the raffle, including the details of each draw, participating tickets, and payouts.

RPSRouter: User-Focused Entry Point

The RPSRouter acts as a streamlined entry point for end-users. This contract is stateless and has a dual-purpose architecture:

  • Protocol Integration: Designed to interact with the client's native smart contract, thereby facilitating seamless engagement for users on your platform.

  • Raffle Interactions: Simultaneously calls the RPS raffle contract to ensure that users can engage with your dapp and receive tickets, all in a single transaction.

The functions detailed in this documentation serve as baseline examples. Our smart contracts can be customized to meet the unique requirements of each client. Therefore, the architecture and functions may vary in actual implementations.

Last updated 1 year ago

✌️
📃