Cubimals in Glitch are random. You don't find out which one you have until you open the box. There are two ways this could be done on a database level. The box could have a specific type of Cubimal assigned to it (probably a relational link to a table of cubimal types), which just isn't revealed to the player until the box is opened. The box could also have no reference to a cubical type at all before opening, and the act of opening a cubical box runs a process that randomly chooses a Cubimal for you.
The latter would be simpler to do from a coding point of view, but leads to a potential problem. If you buy a cubical box, then for some reason, Tiny Speck decide to add a new Cubimal to the series, your box could open to reveal a type of cubical that didn't exist until after you bought it, which would look a bit odd. And we can't have things being odd in Glitch. It would be, well... odd.
If ratios of different Cubimals in a series were changed, old boxes from before the change are simple with this 'picked on opening' method, but more complicated if they already had an assigned Cubimal type. If a rare cubical is made more rare, a box from before the change would be more likely to contain it than a box from after - *if* the type of Cubimal in the box was already set in the database.
Because Tiny Speck released a new range of Cubimals rather than adding to the existing one, either way is quite possible. Assigning the type but hiding it would be more flexible to allow for future changes, but is more complicated than is needed for current functionality.
If the type of Cubimal is set, though, what happens if the database line that contains the type of Cubimal isn't queried until you open the box? In this case, quantum physics tells us that the Cubimal will simultaneously be all possible types (and, *possibly*, dead). The quantum probability will only collapse when the database table is accessed by a SELECT statement. Until you open the box, you have all Cubimals at once.
This does raise an interesting philosophy (or physics, I'm not sure which) question. Would backing up the database act as an 'observation' of the system, collapse the probability, settling the Cubimal type permanently? If just backing up is enough, then Cubimal boxes are probably almost all set, as I'm sure Tiny Speck are careful about backing up; but maybe transaction log backups are ok, in which case they could easily stay unobserved for a day. Load balanced servers are another issue - if the SQL database is duplicated between machines, does each sync cause the Cubimals to set their form permanently?
If backups and load balancing don't collapse the wave, each unopened Cubimal box out there contains all of the Cubimals, so by buying one Cubimal box, we should get the trophy for owning the complete set.
Since a trophy does *not* appear when you hold an unopened Cubimal box, we can assume that either backing up and syncing load balanced database servers *does* count as observation of the data, or the type is picked randomly when the box is opened.
Is it possible that finding the answer to this question is the whole reason behind Glitch? Is the 'game' actually a cover? Is Tiny Speck really a quantum computing research company?
I don't have any answers, just a lot of questions that can't be answered until someone observes them.