See the market. Know your reward tier.

No public action is required

There is no connect or claim button. Once an administrator starts the global timer, each boundary reads the chain and records its result automatically.

1. Step 01

   An administrator starts one global timer

   MarketDrop stays parked at 15:00 until an authenticated administrator starts the persistent clock; each active window then lasts exactly 15 minutes.

   • The original start timestamp anchors every future boundary, so refreshes and deployments cannot shift the cadence.
   • Each active window receives one drop cycle ID derived from its actual start time.
   • A durable claim prevents two runs from owning the same window. Reaching zero queues one cycle, then the timer immediately begins the next countdown.
2. Step 02

   The rules are frozen for that drop cycle

   The active configuration is copied into an immutable manifest before balances or prices are calculated.

   • The manifest fixes the MARKETDROP contract, chain policy, reward tiers, batch limits, and the approved asset list.
   • It also fixes every asset contract, price pair, approved quote token, and stock-token display multiplier used by the run.
   • A later settings change applies to a future drop cycle; it cannot silently rewrite a calculation already in progress.
3. Step 03

   Every positive holder is counted

   The system builds one complete census of positive MARKETDROP balances instead of asking visitors to connect or submit a wallet.

   • The Robinhood Chain RPC confirms chain 4663 and establishes a finalized snapshot target.
   • Blockscout is paginated until all distinct positive-balance holders are returned, and its indexed head must remain within the permitted distance of the RPC head.
   • Zero balances are excluded. All remaining raw balances are added together to create the qualifying supply for that same census.
4. Step 04

   Each wallet receives one reward tier

   A wallet's positive MARKETDROP balance is compared with the qualifying supply captured in the same census.

   • The share percentage is calculated with high precision before any tier is selected.
   • Each lower boundary is inclusive and each upper boundary is exclusive, so a wallet can resolve to only one tier.
   • The wallet address, raw balance, percentage, tier, and snapshot block are persisted together as evidence.

   Active tier policy

   Under 1%

   $0.20 basket$0.01 per slot

5. Step 05

   All 20 assets are validated and priced

   Ten memecoins and ten stock tokens are checked by contract address; ticker text alone is never trusted.

   • Onchain metadata supplies token decimals and, for stock tokens, the multiplier used to convert between displayed and contract units.
   • DexScreener candidates must be on Robinhood Chain, match the exact base contract, report a positive USD price and liquidity, and use the frozen pair or an approved quote contract.
   • A quote that fails policy is recorded as rejected. That asset pauses for the drop cycle rather than receiving a guessed or substituted price.
6. Step 06

   The tier basket becomes token quantities

   The tier's USD target is divided equally across all 20 configured asset slots, then each slot is converted at its persisted drop cycle price.

   • The number of configured slots stays fixed even when an asset pauses, so a failed slot is not redistributed to the others.
   • For each payable slot, its USD amount is divided by the selected price, adjusted for any display multiplier, and converted into the token's smallest onchain unit.
   • The result is rounded down to a whole raw unit. Any rounding remainder is stored as dust, and an amount below one raw unit is skipped.
7. Step 07

   Funding, simulation, and replay checks run

   A calculated reward line is not treated as delivered until the treasury and contract checks pass for that exact frozen manifest.

   • For every asset, the system compares required units with the treasury balance and the distributor allowance; a shortfall pauses that asset.
   • Recipients are sorted and split into deterministic batches. Each batch has a stable identity derived from the drop cycle, asset, recipient range, and manifest.
   • Every batch is simulated first. Onchain replay protection and the expected receipt event prevent the same batch from being accepted twice.
8. Step 08

   The complete result is recorded

   MarketDrop preserves what happened—even when the outcome is partial—rather than replacing missing evidence with sample data.

   • The frozen manifest, holder census, selected and rejected quotes, calculations, treasury checks, batches, and transaction states are stored by drop cycle.
   • A resumed run reads those persisted records and continues from known state instead of silently regenerating completed work.
   • Drop history shows persisted outcomes. A tier is a target calculation, while actual delivery still depends on every required check succeeding.