MuviPe · Per-ticket affiliate program
Every ticket a user buys opens its own referral tree. It holds 363 positions, fills in a fixed order, and closes when the last one lands.
Source:
Affiliate_Program_Structure_of_Individual_Ticket.pdf — 4
pages, 14 diagrams.
This page restates that document. Section 7 is commentary and is
marked as such.
What a ticket owner sits on top of.
A ticket owner — call them X — sits above three direct positions. Each of those opens three more, and so on for five levels. Nothing about the tree is elastic: it is the same 363 seats for every ticket, and the ticket closes when all of them are filled.
Level 1 is mandatory. Positions 1, 2 and 3 must all be filled before the commission cycle unlocks. The document is explicit that they need not come from X — they can be referred by X or by the people who referred X, further up the tree. Either way, all three must land.
Not top to bottom. Left spine first, then sideways.
This is the part the source document spends nine diagrams on, and the part that is hardest to hold in your head. Positions are not filled level by level. The algorithm drives straight down the left edge first, comes back for the centre, comes back again for the right, and only then starts filling the sides.
All three branches move together, one seat each, so the fill order runs straight through the position numbers: 1, 2, 3, 4, 5 … up to 363. The diagram below is the whole thing as one tree, hanging off the ticket owner X, with every position carrying its number — so it can be checked against the source node for node. The source splits it into three stacked diagrams only because 243 seats will not fit on a page.
The tree is wider than the screen — it pans along while playing, or use Fit width →
| Stage | Steps | Positions | Seats | What fills |
|---|---|---|---|---|
| 1 · Mandatory 3 | 0 | 1–3 | 3 | The three direct positions |
| 2 · Fastest Five | 1–4 | 4–15 | 12 | Straight down the left edge |
| 3 · Left positions | 5–12 | 16–39 | 24 | Centre-left, then right-left |
| 4 · Side by side | 13–120 | 40–363 | 324 | Everything remaining, level 3 → 4 → 5 |
Why the numbers jump in threes.
The three branches under X are never filled one after another — they advance together, one seat each. So every step of the fill order consumes exactly three position numbers, and a branch only ever owns numbers of one residue.
If k is the step number within a branch (0 to 120), the global position is 3k + branch. Branch 1 owns 1, 4, 7, 10…; branch 2 owns 2, 5, 8, 11…; branch 3 owns 3, 6, 9, 12…. Each branch is a 121-seat subtree, and 3 × 121 = 363.
| Step k | Path from branch root | Branch 1 | Branch 2 | Branch 3 |
|---|---|---|---|---|
| 0 | — (root) | 1 | 2 | 3 |
| 1 | L | 4 | 5 | 6 |
| 2 | L·L | 7 | 8 | 9 |
| 3 | L·L·L | 10 | 11 | 12 |
| 4 | L·L·L·L | 13 | 14 | 15 |
| 5 | C | 16 | 17 | 18 |
| ⋮ | ⋮ | ⋮ | ⋮ | ⋮ |
| 120 | R·R·R·R | 361 | 362 | 363 |
The bonus, and the one thing that takes it away.
Fastest Five is an extra bonus on top of the normal commission. It is awarded for one specific chain: a branch root and the four positions directly below it down the left edge — for branch 1, that is 1 → 4 → 7 → 10 → 13.
The condition is not just that the chain fills. The document says the bonus applies when those left positions are done "only by the owner referred" — every seat in the chain has to come from X's own referrals. One outsider anywhere in the five and the chain no longer qualifies.
Page 4 of the source, restated.
A ticket created through a producer, or bought with no referral link at all, is created under the company. New registrations then stack under the company from there.
A ticket that wants to register is set to a left position, at random.
"so it will break fastest five achievement of others (which helps the users to speed up)"
On register, check whether the same user is registering again.
On register, check whether the ticket's full cycle is already complete.
A user who has completed a full cycle waits 1–2 months before buying a new ticket for the same content.
"this will help us to promote more content were user will move on to other content"
One number in the app is already this tree.
The expanded ticket panel already reports Members 125/363 — that 363 is this structure, and the counter is progress toward closing the ticket.
It used to report Fast Five 2/9, which had no basis here — nine corresponds to nothing in the Fastest Five structure. It now reads 2/3: the bonus needs the left spine under each of the three mandatory positions, so three chains have to land. The name still comes from the depth of a chain, which is five positions.
Worth flagging that the source defines the condition for the bonus but never a progress metric, so the denominator is a reading rather than a quotation. Three is the count the condition is phrased around; the finer alternative is 12, the seats in stage 2 — a 3 only moves when a whole five-deep chain completes.
View Tree Details is the natural home for a live version of Figure 2.
Commentary — these are gaps I found, not statements from the source.
The source says "the commission will be split accordingly to each person" and that Fastest Five earns "extra bonus". There is no rate, no split table, no bonus amount, and no statement of who is paid when a position fills. The entire payout side is undefined, which means the tree can be built but the earnings cannot.
Page 1 numbers positions by level: level 2 is 4–12, level 3 is 13–39, level 4 is 40–120. Pages 2 to 4 number them by fill order, where 13 is the deepest seat of branch 1's left spine and 40 sits at level 3. Same tree, same totals, incompatible labels. This page uses the fill-order scheme throughout, because that is the one the detailed diagrams use — but anyone implementing from both pages will get it wrong.
Placing unreferred tickets into random left positions is said to "break fastest five achievement of others", and then, in the same sentence, to help users "speed up". Breaking a bonus and accelerating the people chasing it are opposite effects. This is the one rule whose intent cannot be recovered from the text, and it needs a decision before it can be coded.
What happens to a position filled by someone the owner did not refer — who is credited? What does "check same user was registering" do when it matches: reject, or place elsewhere? Is the cooldown 1 month or 2, and what starts the clock? None of these are answered.