This project aims to make syncing with games more straightforward and accessible to the average game developer and provides a better UX to the user, limiting exposure to risk and mitigating annoying popups.
We will expose additional functionality at the RPC layer to govern pre-authenticated message signing and improve the general UX with inpage dialogues for whenever they are required to avoid the window/gamer losing focus.
Delegated message signing works as follows:
- The wallet presents the user with a structured plaintext message or equivalent interface for signing with the EIP-191 signature scheme (string prefixed with \x19Ethereum Signed Message:\n). The message MUST incorporate the wallets Ethereum address, the delegated Ethereum address, domain requesting the signing, version of the message, a code to associate responsibilities, a chain identifier chain-id, uri for scoping, nonce acceptable to the server, and issued-at timestamp.
- The controlling wallet (A) signs the message (A)
- The delegated Wallet (B) signs future messages containing the controlling Wallet (A's) delegation
- Any verifier can verify that Wallet B is the signer of the second message, they can also verify the contained delegation was signed by Wallet A and perform any additional metadata checks to test for any disqualifying criteria (presented after session expiry etc...)
- Build the extension and manually install
$ cd extension && yarn run install && yarn run build
- Go to chrome://extensions and enable dev mode
- Click
Load unpackedand select the./distdir
- Start the examples dev server
$ cd example && yarn run install && yarn run dev