# Detailed Rules ## **Box Generation and Numbering** A Box is the basic participation unit in MintBox. Box generation and numbering follow these rules: * **Box Price**: the total value of Tokenized Interest in each Box (measured at Sale Valuation) is the same and equals the Box Price, for example $10. * **Number of Boxes**: each MintBox has a fixed number of Boxes. The number N is determined by Sale Valuation and Box Price: N = Sale Valuation / Box Price. * **Box contents**: each Box contains only one card's Tokenized Interest. The quantity may differ, but the value of the Tokenized Interest inside each Box equals the Box Price. For example:
Box No.Corresponding Card / Tokenized InterestIssue Price ($)QuantityBox Total Value ($)
12022-23 MUSEUM COLL UCL JULIAN ALVAREZ EMERALD 1/111010
22023-24 IMMACULATE ARDA GULER HERALDED MAT-PLATINUM 1/10.110010
32023-24 IMMACULATE ANTOINE SEMENYO PLATINUM 1/10.52010
* **Box numbering**: each Box has a natural-number ID from 1 to N. The ordering is **pre-set and disclosed by the platform during the Preview phase**. * **Box finder**: before MintBox starts, the platform publishes the complete Box list. You can enter a Box number on the MintBox details page to look up its contents, or download the full Box list as a CSV file for verification. ## **Commitment and Ticket Issuance** After the Participation phase begins, you commit USDC, and the system issues the corresponding number of Tickets at the same time. A Ticket is the only entry that lets you participate in that MintBox draw. Each Ticket independently enters the final draw and ranking for Box allocation. The rules are: * **Commitment unit**: the commitment amount must be an integer multiple of the Box Price. For example, if the Box Price is $10, the commitment amount must be a multiple of $10, such as $10, $20, $50, or $110. * **Ticket issuance**: for each full Box Price committed, the system automatically issues 1 Ticket. Each Ticket independently participates in the later draw. For example, committing $100 gives you 10 Tickets. * **Ticket number**: each Ticket is a 4-digit number, such as 3827, randomly generated by the system when the user completes the commitment and displayed immediately. * **Ticket generation time**: each Ticket also records its generation time. This timestamp serves as the tie-breaker within the same hit group (see "Same-group ranking rule" below). After committing, you can immediately view all Ticket numbers, quantities, and generation times for that MintBox in the "My Tickets" module. ## **Draw and Allocation** After the Participation phase ends, MintBox enters the Result phase. The platform completes Draw Factor generation, digit-by-digit matching between Tickets and the Draw Factor, Ticket ranking, and Box allocation, in that order. The rules are as follows. ### **(1) Draw Factor Generation** The Draw Factor is generated from a public and verifiable off-chain data source. At the current stage, the platform uses the following rules: * **Data source**: the Binance BTC/USDC spot price at a specified moment. The timestamp is disclosed in advance during the Preview phase. **This ensures that no one can know the result before that moment, and that everyone can independently verify the result after that moment.** * **Extraction method**: take the Binance BTC/USDC spot price at the specified moment, rounded to two decimals. Extract the tens digit, ones digit, first decimal digit, and second decimal digit, then concatenate these four digits in order into a 4-digit Draw Factor. Example: ``` BTC price: 107,795.60 Tens digit: 9 Ones digit: 5 First decimal digit: 6 Second decimal digit: 0 Draw Factor: 9560 ``` ### **(2) Digit-by-Digit Matching of Ticket Numbers** Each Ticket is compared with the Draw Factor digit by digit. A digit counts as a hit only when the number in the same position is exactly the same. More hits means a higher winning tier. Example: ``` Draw Factor: 9 5 6 0 Ticket: 3 5 6 0 Match: ✗ ✓ ✓ ✓ Hits: 3/4 ``` Based on the number of hits, all Tickets are placed into five groups, in the following priority order: ``` 4/4 > 3/4 > 2/4 > 1/4 > 0/4 ``` ### **(3) Ticket Ranking** All Tickets are ranked in two steps: First, rank by number of hits. More hits means a higher rank. The system ranks Tickets in the order of 4/4, 3/4, 2/4, 1/4, and 0/4. Second, rank by commitment time within the same group. If multiple Tickets have the same number of hits, earlier commitment time ranks higher. ### **(4) Box Allocation** After Ticket ranking is complete, the platform maps Tickets to Box numbers one by one in ranking order. The rules are: * If the MintBox has N Boxes, then Tickets ranked 1 through N receive the corresponding Box numbers in order. The #1 ranked Ticket receives Box #1, the #2 ranked Ticket receives Box #2, and so on. * Tickets ranked after N are considered not winning. The corresponding commitment amount becomes available to claim, and users may claim it manually after results are published. ## **Referral Boost** To encourage sharing and community building, the platform introduces the Lucky Digit mechanism as a referral boost during participation. ### **(1) What Lucky Digit Means** In the digit-by-digit matching mechanism, every digit of a Ticket number normally needs to exactly match the corresponding digit of the Draw Factor to count as a hit. When a digit is upgraded to a Lucky Digit, that digit no longer needs to match: any number from 0 to 9 counts as a hit, equivalent to a 100% hit rate for that digit. Example: ``` Scenario 1: regular user (0 Lucky Digit) Draw Factor: 9 5 6 0 Ticket: 3 5 6 0 Result: ✗ ✓ ✓ ✓ → 3/4 hits Scenario 2: invited 2 friends (2 Lucky Digits) Draw Factor: 9 5 6 0 Ticket: 3 7 6 0 Result: ★ ★ ✓ ✓ → 4/4 hits (2 Lucky Digits + 2 exact hits) ``` ### **(2) How to Get Lucky Digits** * For each Invitee who **successfully participates in the current MintBox and has a cumulative commitment in that MintBox greater than 100 USDC**, the inviter receives 1 Lucky Digit (the exact threshold follows the rules of that MintBox). * Lucky Digits are awarded only to the inviter. The Invitee does not receive Lucky Digits for being invited. * Lucky Digits do not create new Tickets and do not change the total number of Boxes in the MintBox. They only affect the hit result of existing Tickets. ### **(3) How Lucky Digits Are Used** * **Ticket-by-ticket use**: Lucky Digits are applied in the order that Tickets were generated. The system fills the first Ticket first, then moves to the next Ticket. * **Fixed unlock order**: for each Ticket, Lucky Digits unlock in the order of the 1st digit → 2nd digit → 3rd digit. The 4th digit always remains an exact-match digit and is never upgraded to a Lucky Digit. * **Per-Ticket cap**: each Ticket can have at most 3 Lucky Digits, leaving at least 1 digit (the 4th digit) as an exact-match digit. * **No total cap**: there is no cap on the number of invitees, and no total cap on the number of Lucky Digits a user can earn, except as limited by the number of Tickets the user has. ## **Fairness and Verifiability** To ensure that every MintBox draw result is fair, open, and verifiable, the platform makes complete arrangements at both the mechanism-design and information-disclosure levels. ### **(1) Mechanism Design** * **Public and verifiable data source**: the Draw Factor is generated entirely from the Binance BTC/USDC spot price, a public, objective, third-party data source. The price is public to the whole market, and anyone can query it at the specified moment and recompute the result. * **Generation rules disclosed in advance**: key parameters such as the Draw Factor source and exact timestamp are disclosed during the Preview phase, ensuring that the rules are determined before participation starts and cannot be changed afterward. * **Simple and transparent matching rules**: Ticket numbers are matched against the Draw Factor through digit-by-digit comparison, then ranked by number of hits and commitment time. This is a purely rule-based process with no manual intervention, and all users can recompute it. * **Box list disclosed in advance**: the Tokenized Interest type and quantity corresponding to each Box number are determined and disclosed during the Preview phase, preventing any ex post adjustment. ### **(2) Information Disclosure** To support independent verification by users, the platform discloses relevant information at three points: #### Preview * The complete Box list, including each Box number and the type and quantity of Tokenized Interest inside it. * Draw Factor generation rule: BTC price source and timestamp. #### Participation * The number of Tickets the user receives, specific Ticket numbers, and Ticket generation times. * The Ticket numbers and Ticket generation times of all participating users, updated hourly. #### Result * The 4-digit Draw Factor for the MintBox. * The complete draw and allocation results table. Based on the disclosed information, you can independently verify the result after the draw and confirm that there is no black-box mechanism, and that the allocation result follows the principles of fairness and randomness: 1. Obtain the BTC/USDC spot price at the specified moment from Binance or another public data source. 2. Recompute the Draw Factor according to the disclosed rules. 3. Match the Draw Factor against the public Ticket list digit by digit. 4. Reproduce the full hit, ranking, and allocation results. 5. Confirm that Box numbers were not modified before or after the draw. 6. Confirm that all Ticket numbers and Ticket generation times were not modified before or after the draw. This verification process does not require any extra authorization or data from the platform, making the fairness truly verifiable. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.market.cards/mintbox/detailed-rules.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.