norswap
norswap
The initial design had the game creator able to specify a function (contract + selector) to be used as a callback to validate that a user is able to join...
Our current scheme for private information involves committing to player hands and the card remaining in player decks (via a (to be salted) Merkle root) and then proving changes to...
This is for after the tech demo. [MUD](mud.dev) simplifies development by synchronizing the frontend and the backend easily (amongst other things). We can't really use MUD today because the game...
Blocker selection resembles [attacker selection](https://github.com/norswap/0xFable/issues/27) but with the added difficulty that each blocker must be matched to an attacker. To assign a defender, drag from the defender to the attacker...
For the tech demo, the game has to run somewhere. The long-term plan is to make it a rollup (settlement layer TBD), but in the short term, we want an...
(This will only be relevant in the far future.) Currently, game data accumulates in the game contract, with a minimal amount of cleanup done. In the future we might wish...
Currently, only the players can really meaningfully participate to a game. It would be neat to be able to replay games, or even to spectate games. Spectating, given no private...
For this, we will need to collect all errors that can be thrown by viem, wagmi (including things inherited from tanstack-query? not sure it throws its own errors), and maybe...
### What package is the feature request related to? typedoc-plugin-markdown ### Background I have an exported variable that is a deeply nested `const` object. Using `"expandObjects": true`, I get a...