I have a metaprotocol on nostr/cashu idea for deterministic randomness with an authoritative source if it's where helpful.
For the past three years, we have been developing nostr:npub1kd3nlw09ufkgmts2kaf0x8m4mq57exn6l8rz50v5ngyr2h3j5cfswdsdth , an open-source educational game that teaches Bitcoin and Lightning through play.
Presented at nearly 30 Bitcoin conferences worldwide, it has educated thousands of people by turning Lightning payments into a fun, hands-on experience. The game’s design, infrastructure, and integrations have been refined through years of feedback from the Bitcoin community, resulting in a polished and reliable platform.
However, conferences only reach a limited audience. Millions of people, especially in regions with financial repression or no access to meetups, still lack opportunities to learn about Bitcoin and freedom technologies. Our goal is to bring this experience to them.
The next phase of Chain Duel will evolve it into a global online multiplayer platform built on NOSTR for identity and coordination, and on the Lightning Network for real-time, censorship-resistant microtransactions. It will combine gameplay, education, and open-source tools to make learning Bitcoin accessible to anyone with an internet connection.
Discussion
Can I know more details? 🙏 it might be useful
https://github.com/EthnTuttle/manastr
https://github.com/EthnTuttle/kirk
I spent some time with claude on these two projects trying to get a PoC working. If you explore there, some of the docs might be useful. the kirk one I worked on most recently. Check the .kiro/specs/cashu-nostr-game-protocol folder in kirk and the .claude folder in manastr.
If none of the makes sense, we can hop on a call and I can try to explain. The core premise is below:
the unblinded signature from a cashu mint (using BDHKE) cannot be biased by the "player" or the "game master". The player creates a seed for the randomness and provides a blinded message to the GM. The GM signs with a specific key and returns a "blinded signature". The player now unblinds it, removing any bias or information linkage the GM had. Given the final unblinded message, the original seed, and the signing keys of the GM. Since the GM is the arbiter of the rules, it's the only one that has the knowledge to validate the token proofs. The 32bytes of data that represent the unblinded signature can be decoded as a source of randomness for gaming. The simplest would be using 32 bytes to decode to old D&D encounter tables.
Thank you for taking interest!