<aside> 🙂 Eternal Privacy Playgrounds
1 - Why your game needs hidden information
2 - An ontology of hidden information mechanics
3 - An ontology of trustless privacy techniques
4 - Knitting our ontologies together
</aside>
Can we build a bridge?
In 2023, applied cryptographers and game designers are facing a single problem, from opposite sides of a gaping chasm. The gulf between their design spaces is enormous. It’s really hard to translate the needs and capabilities of each role across the divide. Relatively few people are well-versed in both sophisticated game mechanics and the suite of cryptographic privacy-enhancing technologies - that, let’s not forget, was largely sponsored to solve problems in DeFi rather than, say, hiding player inventories in onchain games.
These cryptographic primitives do make relatively simple mechanisms possible, such as Dark Forest’s fog of war, or Battleship. However, there’s a rich world of hidden information mechanics that these don’t account for.
This leaves us in a problematic scenario where game studios have limited visibility on which sorts of hidden information mechanic are possible. Consequently, studios are designing games from the ground up in a way that doesn’t require them. This does enable games to reach production, but only those that are inherently constrained in their ability to handle secret information that’s baked into the world (as opposed to hiding in the skulls of human players).
Baking hidden information into autonomous game worlds is really important, for three reasons:
Let’s see if we can build that bridge.