Skip to main content
MoonTools
All tools

STAY CURIOUS. BUILD SOMETHING.

See you on the moon.

Explore the toolkit
MoonstersMoonTools

The Moonsters utility suite for local planning, previews, creator drafts, and future production integrations.

A universe of possibility. Built together.

Suite

All toolsDashboardCreator StudioAdmin

Utilities

AuctionsSendSnapshotRevoke

Trust

TermsPrivacyRiskFairness

Most tools remain local previews or read-only mainnet services. Public real-value transactions remain disabled. The separately gated MoonMonth devnet test uses sponsor-paid transactions with valueless assets.

HomeRaffleAuctionsSendTools
OverviewFree entryPrize calendarMy ticketsWinnersArchiveFairness

MoonMonth preview — no public entry

The sample calendar and historical receipts are browser-local. Paid entry is retired. Only the separately gated, sponsor-funded devnet console can record valueless test entries.

Raffle Design Preview

This page documents the preserved production design. The currently running MoonMonth interface is browser-local preview software, not a deployed on-chain raffle.

1. Intended ticket record model

A future production deployment is designed to store each purchase as a contiguous one-based ticket range [ticket_start, ticket_end_exclusive). This local build keeps preview ranges only in browser storage.

2. Intended randomness provider

The preserved Anchor design targets Switchboard On-Demand VRF for a production draw. This build does not request a VRF value or create a public randomness transaction.

3. Winner-selection formula

The planned on-chain formula is winning_ticket = (random_value % total_tickets_sold) + 1. The local preview can demonstrate this rule, but its values are not authoritative or independently verifiable.

4. Planned no-replacement handling

The production design would walk forward from a collision until it finds an unwon ticket. The logic is documented so a deployed program and public data can be audited later.

5. Planned prize escrow

A live deployment would require NFT, SPL-token, or SOL prizes to be escrowed before paid entry opens. This preview does not custody assets or create escrow accounts.

6. Planned cancellation and refunds

The preserved program design includes cancellation and buyer refunds. Local preview refunds only update the browser’s saved demo state and do not move USDC.

What a live verification flow would require

  1. A deployed raffle program and configured public RPC endpoint.
  2. A real Switchboard randomness request and reveal transaction.
  3. Published purchase receipts and the finalized draw transaction.
  4. Recomputing winning_ticket = (random_value % total_tickets_sold) + 1 from those public records.

Local preview receipts cannot be opened in Solana Explorer and must not be treated as proof of a ticket, draw, payment, prize, or entitlement.