I can understand it leaving traces in your native NAND (4.x system) but what about inside emuNAND?
Scenario: I do a system transfer from my legit system (the one which is under warranty and I've actually had the touchscreen repaired before with no issue) to my Gateway system and move the NAND over to emuNAND. I boot into Gateway mode and play a ROM of a game I have already played as a legit cartridge. Because it's the same title ID, it doesn't create any weird duplicates in the play log (at least, from what I can tell)
Then I transfer it back after I'm done doing whatever I need to do in the game
From what I can tell, that's "safe", but does anyone have any evidence proving otherwise?
I'd also be curious if cards like the Sky3DS leave any traces behind either. I'm inclined to believe they wouldn't, since it's literally emulating a legit came cartridge, as long as the ROM hasn't been modified, it should be impossible to tell apart from a legit game cartridge.
Interesting. How much data did we determine is in one of those QR codes again, wasn't it like 4KB? So I can understand why it has to download more of the stuff from the server, since otherwise you'd have like 10 QR code sets to scan.
I'm inclined to think this is a multi-stage exploit, think of the Wii U browser exploits that were discovered (and subsequently patched before anyone did anything useful with them.) Cubic Ninja is just the "loading platform" if you will, because it provides the QR scanning engine, you then call the web browser somehow and exploit that. Seems weird, but from what I've read, the Gateway exploits have this multi-stage process too, where it uses the MSET exploit to load something, which loads something else, etc.
Seems nothing is simple anymore
Unrelated, AlbertoSONIC, have you compiled a .3dsx version of your decimal to binary converter yet? I'm really interested in using that, since it's actually a useful piece of homebrew.