MyDrop24

Fairness & Transparency

MyDrop24 is an entertainment-focused commerce platform for mystery boxes with randomized item allocation. This page explains the transparency and verification method we use so you can independently confirm that reveal outcomes are generated according to a predefined process and cannot be changed after the fact.

MyDrop24 is entertainment-only and not an investment product. Do not use the Service with an expectation of profit.

1

Overview

When you purchase and reveal a mystery box, the Service allocates an item according to a randomized allocation method. We provide verification data so that users can independently reproduce the outcome computation and confirm that the reveal followed the published method.

2

What "Verifiable" Means in This Context

The verification system is designed to provide:

Commitment

We commit to a secret value before the reveal.

Determinism

The same inputs always produce the same output.

Reproducibility

You can reproduce the output after the reveal using disclosed inputs.

Non-editability after commitment

Outcomes cannot be changed after the commitment is made without detection.

3

The Inputs (Seeds) and Nonce

A typical reveal uses the following inputs:

Server Seed

A secret value generated by the Service.

Server Seed Hash

A cryptographic hash of the server seed shown before the reveal to prove the commitment.

Client Seed

A value linked to your account/session that you can refresh.

Nonce

A counter value that increments per reveal to ensure each reveal is unique.

4

The Process (High-Level)

1

Commitment (before reveal)

Before you reveal, the Service generates a server seed and displays only its hash (server seed hash). This acts as the commitment.

2

Combination (during reveal)

The Service combines the server seed, your client seed, and the nonce in a documented order and applies a standard cryptographic hashing method.

3

Mapping to an item

The hashing output is converted to an internal random value and mapped to an item according to the published distribution rules for that mystery box.

4

Disclosure (after reveal)

After the reveal, the Service discloses the server seed and the other relevant inputs so you can verify the result.

5

What You See After a Reveal

After you reveal an item, you will be able to view verification data (format may vary by UI), which typically includes:

server seed hash (pre-reveal commitment)
server seed (post-reveal disclosure)
client seed
nonce
outcome value / result identifier used by the mapping logic

6

How to Verify a Reveal

1

Confirm commitment

Compute the cryptographic hash of the disclosed server seed and confirm it matches the server seed hash shown before the reveal.

2

Recompute outcome

Combine server seed + client seed + nonce in the documented order and run the published hashing method.

3

Confirm mapping

Confirm that the recomputed output maps to the same revealed item according to the published mapping rules for that box.

Verify a Result

Enter the server seed (revealed), client seed, and nonce to calculate the outcome and verify the result.

Server Seed (Unhashed)

Client Seed

Nonce

7

Why This Matters

This approach provides transparency that:

the Service committed to a seed before reveal (cannot change later without detection),
the revealed item result is reproducible from the disclosed inputs,
each reveal is distinct due to the nonce, and
users can independently audit the outcome computation.

8

Important Clarifications

Randomized allocation determines which item is revealed.
Any Exchange (Sell-Back) value is calculated separately and may be based on market pricing references and applicable handling/fulfillment components.
Market prices fluctuate and may vary by region, size, condition, and liquidity.
Deposits and withdrawals are crypto-only. Crypto transactions are irreversible once confirmed on-chain and network fees may apply.
The Service is 18+ only.

9

Security and Abuse Prevention

To protect the integrity of the Service, we may restrict features, require verification, and/or suspend accounts if we detect:

automation/botting,
manipulation attempts,
suspicious transaction patterns,
multi-account abuse,
other policy violations.

10

Questions

If you have questions about your verification data, contact support and include:

your account email/username,
the box name,
timestamp,
server seed hash,
client seed,
nonce,
and any screenshots relevant to the issue.

Contact: [email protected]