Skip to documentation

Droptron documentation

Private launch infrastructure, explained plainly.

Droptron combines public Starknet launch contracts with STRK20 shielded balances, private transfers, private claim tickets, and wallet-owned proof generation.

Mainnet productReady walletMIT licensed

Start here

What Droptron does

Droptron is a launch and distribution desk for Starknet. Teams can create a token, run a public sale, deliver private allocations, publish private airdrops, and schedule vesting. Participants can join a launch and receive or claim tokens without publishing the wallet-to-allocation link.

For participants

Discover, participate, claim.

Browse launches publicly. Connect a privacy-capable wallet only when an action needs it.

For creators

Launch, fund, distribute.

Use a signed wallet workspace to manage contracts and private recipient delivery.

Product workflows

Four paths, one private ownership layer

Private launch participation

A public launch exposes price, schedule, and aggregate activity. Payment enters through STRK20 and the purchased allocation returns as a shielded note.

Private Disperse

A creator sends one atomic private batch to registered recipients. No public recipient manifest is placed onchain.

Private airdrop claims

Recipients receive private bearer tickets, discover them through their wallet, and redeem them into shielded token balances.

Private vesting

One campaign contains multiple immutable unlock series. Claims groups them as one schedule while each tranche remains independently redeemable.

Privacy model

Private ownership. Honest public boundaries.

Droptron does not describe a public sale as fully confidential. It protects the ownership route while leaving the market and contract state inspectable.

Private
  • Parties, token, and amount inside private transfers
  • Shielded balances and private note ownership
  • Airdrop and vesting ticket ownership
  • The link between a buyer and their allocation
Public
  • Launch price, schedule, and aggregate activity
  • Contract configuration and deployed addresses
  • Shield and unshield address, token, amount, and timing
  • Vesting schedule and claim-series terms

STRK20 integration

Integrated beyond a private transfer button

The product uses the Wallet API for capability detection, shielded balance reads, shielding, unshielding, private transfers, atomic action batches, and privacy_invoke routes into Droptron contracts.

  1. Wallet-held privacy state

    Ready discovers notes and builds proofs through its private wallet environment.

  2. Live preflight

    Droptron reads pool fees, checks private balances and recipient registration, and opens a prefilled Shield flow when required.

  3. Atomic private action

    The STRK20 pool verifies the action and calls a pool-pinned Droptron helper when public contract execution is needed.

  4. Shielded output

    Purchased or redeemed tokens return to the wallet as private notes instead of a public recipient transfer.

Architecture

Funds stay on Starknet; product context stays offchain

BrowserDroptron interface

Terms, preflights, signed creator workspace

WalletReady + STRK20

Keys, notes, proofs, private actions

StarknetPool + Droptron contracts

Verification, launches, tickets, redemption

Supabase indexes public discovery data and resumable creator drafts. Recipient manifests are removed from ordinary JSON and encrypted server-side with AES-256-GCM. Onchain contracts and wallet state remain authoritative for funds and claims.

Security controls

Every signature and fund movement has a narrow purpose

Creator access starts with a single-use, five-minute Starknet typed-data challenge bound to the site origin, chain, and wallet. Its resulting session cannot move tokens; approvals, shielding, delivery, claims, and settlement remain separate wallet-reviewed transactions.

  • Wallet-owned custodyReady retains account keys, viewing keys, private notes, and proof generation. Droptron never receives them.
  • Scoped authorizationCreator APIs verify the signed wallet session and recheck deployed ownership and funded state on Starknet before publication.
  • Limited token authorityApprovals use exact amounts and configured spenders. Pool-only helpers, factory allowlists, and allowance cleanup constrain private routes.
  • Contract accountingReentrancy locks, checked math, exact balance deltas, caps, collateral reserves, ticket burns, and atomic rollback defend value paths.

Mainnet contracts

Small, composable contract surface

STRK20 poolShielded balances, private transfers, and privacy_invoke0x040337b1af3c663e86e333bab5a4b28da8d4652a15a69beee2b677776ffe812a
Launch participationPool-pinned private purchase route0x05c1ae66fb281ca0451b570bcad29c87cfa4e34b4552aec47ed8bd0a161b995e
Distribution factoryCreates immutable claim-ticket series0x06bd6c7716abff65de60874e30f644c1dfede3f82ca087e2ccabc09544f3a2d3
Claim redemptionPool-pinned ticket redemption route0x018590ba519e985ff0ca35d8ef4132b1d3ac34605dd5c2c123e651eea08d4efe

Droptron also ships fixed-supply token, fixed/linear launch, and funded claim-series classes. Contract code and tests live in contracts/ ↗.

Mainnet evidence

Real flows, deliberately small value

These transactions exercise the product’s STRK20 paths on Starknet Mainnet. Each link opens the public transaction record; private note ownership is not revealed by the application.

Developer quickstart

Run Droptron locally

Use Node.js 20+, npm, Scarb 2.20.1, and Starknet Foundry 0.63.0.

git clone https://github.com/Femtech-web/droptron-launchpad.git
cd droptron-launchpad
npm ci
cp .env.example .env.local
npm run dev

For the Cairo package:

cd contracts
scarb build
snforge test

Public chain addresses may use NEXT_PUBLIC_ variables. Account private keys, the Supabase secret, and the recipient-manifest encryption key must remain server-only.

Operational notes

What users and integrators should know

  • Private actions pay the live STRK20 pool fee.Droptron reads it before opening the wallet and calculates token amounts using each ERC-20’s decimals.
  • New private notes need time to mature.Wait roughly 10 blocks before the next private spend or refresh.
  • Wallet approval warnings deserve review.Claim-ticket approvals are exact and tranche-scoped; verify the spender and amount rather than accepting blindly.
  • Reject an identical prompt after success.Ready has sometimes redisplayed a completed private request. Droptron guards against resubmission, but cannot dismiss a request already owned by the wallet window.
  • Small-value Mainnet only.The contracts have strong local coverage and targeted review, but no independent production audit. Do not use meaningful funds yet.