MMY download link: what bnp & gz select

The install link takes two parameters. Each one selects something, and together they decide the file name you receive.

The link used on this site is bnp=muvt with gz=2rwkt. Open the install link

What bnp selects

bnp picks the app listing. The value muvt points at one listing, which carries the app name, the icon, the artwork and the host the file is fetched from. A different bnp value would show a different listing. This site only uses the one that was measured.

What gz selects

gz picks the channel file. With gz set to 2rwkt, the served file name becomes mmy.2rwkt.apk. Without gz, the same listing serves the plain file, mmy.apk. The token in the file name is the channel marker, not a version. Version 2.2.5 comes from inside the package, and it is identical in both files.

That is why the button on every page of this site keeps both parameters. Drop gz and the host serves the other file, which is measured and recorded on the second file page but is not the file this record's hash describes.

Why the file name carries the token

The channel token lets the vendor tell installs apart after the fact. A small channel record inside the APK repeats the app id and the version and carries an AppsFlyer source marker, so the file that arrives is not byte-identical to the plain file even though the version label matches. The token in the file name is the visible half of that arrangement. The roughly 95 KB size gap is the invisible half.

A browser can still rename the download. Chrome appends a number when a file of the same name already exists, and some managers add .bin. The token survives a rename only if you keep it. The byte count and the hash survive regardless, which is why they are the checks this site asks for.

Where the bytes come from

The listing page itself is a shell. It does not contain the APK. When the download starts, the file host answers, and the measured download was redirected once to a CDN hostname before the bytes arrived. The redirect is normal for a file served this way; what matters is the file at the end of it.

A redirect is also why the file name you see in the browser can differ from the name on the host. Compare bytes, not names. 20,954,528 bytes with the recorded SHA-256 is the channel file, whatever the browser called it.

What the link does not carry

No identifier for you is added by this site. The two parameters select a listing and a channel file, and that is all they do. The host on the other end sees the request and logs what it logs; this site does not see that log and does not add to it.