Why FUZD? In many games, hidden-information mechanics are crucial. A common solution is commit+reveal where players commit their action first and reveals later when nobody can backtrack This offer compelling social dynamics to share intel and collaborate!We are so fond of this mechanism that we use it in all our games so far: "Tug of War" etherplay.io/blog/our-first… "Conquest.eth" @conquest_eth "Duel In The Dark": devfolio.co/projects/duel-… "Daily And Deadly": ethglobal.com/showcase/daily… "Stratagems" @stratagems_ethThe issue is that in many commit+reveal setup, players need to execute the reveal at inconvenient time Solution: provide a service that will reveal the action on their behalf What about secrecy though? Enter FUZD: 🔺 it performs the reveal 🔺 but does not know its contentHow does FUZD maintain secrecy❓ 🔺It's a modular system with one executor and one decryptor. 🔺Using @drand_loe time-lock encryption, players encrypt their data in the client and send it to FUZD 🔺FUZD can then only decrypt and execute it when the time comes.Want to integrate FUZD into your game or app❓ 🔺Check out our website for more details (docs is a work in progress) fuzd.dev 🔺Also, see @jollyroger_eth's FUZD branch for integration examples. github.com/wighawag/jolly… 🔺 Or check our latest game @stratagems_eth
