Resolves YES if, according to statements from pannenkoek2012 or popular consensus, the conditions for the bounty referred to in this video to be paid out have been reached before this market closes. (It doesn't matter if the money hasn't been sent yet or if it was refused or something, only that the conditions for it to be paid out were fulfilled).
May resolve NO early if the bounty is retracted.
Veritasium explores this at https://www.youtube.com/watch?v=AaZ_RSt0KP8 starting around 11:26. I believe it is conclusive evidence but the bounty creator is in denial and (from my view) being stubborn about what is clearly a very plausible explanation.
How do you resolve in the face of pannenkoek2012's stubbornness? I would argue popular consensus has already been reached on this and settled on the cosmic ray hypothesis.
@MRME pannenkoek's bounty is for a .m64 recreation. if it's cosmic ray, it's likely that this market will resolve NO at market close
@MRME In addition to what Robin said, there also isn't a community consensus that this was a cosmic ray. There are a lot of documented hardware errors in sm64, but they tend to not be very consistent with what you'd expect if they were caused by random bitflips; for example, we rarely see messed up textures or unexplained crashes, even though those are much more likely to be the result of a random bitflip than something interesting like a change in Mario's height. I think the closest thing to consensus is that this is a hardware error of some sort, and it's possible that hardware error was caused by a cosmic ray, but this is really far from being worthy of a bounty resolution. There's also nobody pannen would actually give the $1000 to; it's not like there's any clearly defined group of people who Proved A Cosmic Ray Was Responsible, that's just a known thing that rarely happens to hardware that's become more likely after decomp made software errors seem less viable
@CollinMatthews yes exactly
and to clarify what i meant in my comment, "conditions for the bounty to be claimed" may not be exactly equal to "ttc upwarp cause definitely identified"