from jacobc.eth of Game7
Currently, web3 game developers are forced to choose between building a browser game with great wallet compatibility by building a webGL game (where games are laggy and graphical performance is limited), or to launch as a native desktop or mobile game with virtually no transactions and instead push all transactional activity to a separate web application. Some projects are forced to launch their own proprietary wallets to get around this problem, only to find that their wallets aren’t interoperable with other web3 sites and games, so assets remain stuck in silos.
We are seeking the best technical approach and implementation for passing through and overlaying a natively installed wallet (Ie. MetaMask or another natively installed wallet) on top of a native desktop game.
A number of existing native applications engage in the sort of overlay heavior, for example, Steam or Discord. Some have suggested that the technical approach of libraries like goverlay or MangoHUD could be replicated for these purposes.
- Any solution must be able to prevent the native game from tampering with the overlaid UI elements. If a game can potentially force the player’s private keys to consent to a transaction that the player didn’t consent to, the solution is disqualified.
- BONUS: Allow the player to hide and unhide the wallet UI layer through a hotkey interaction similar to Steam
- BONUS: Enable the game to initiate a transaction request, similar to a web3 site requesting a transaction approval from MetaMask
Please email: [email protected]