diff --git a/ERCS/erc-7846.md b/ERCS/erc-7846.md index 206e19496dc..6406201bc93 100644 --- a/ERCS/erc-7846.md +++ b/ERCS/erc-7846.md @@ -1,8 +1,8 @@ ---- +--- eip: 7846 -title: Wallet Connection API -description: Adds JSON-RPC method for requesting wallet connection with modular capabilities. -author: Conner Swenberg (@ilikesymmetry), Jake Moxey (@jxom), Lukas Rosario (@lukasrosario). +title: Wallet Connection API +description: Adds JSON-RPC method for requesting wallet connection with modular capabilities. +author: Conner Swenberg (@ilikesymmetry), Jake Moxey (@jxom), Lukas Rosario (@lukasrosario) discussions-to: https://ethereum-magicians.org/t/erc-7846-wallet-connection-api/22245 status: Draft type: Standards Track @@ -12,7 +12,7 @@ created: 2024-12-15 ## Abstract -This ERC introduces a new wallet connection JSON-RPC method focused on extensibility, `wallet_connect`. It leverages the modular capabilities approach defined in [ERC-5792](https://eips.ethereum.org/EIPS/eip-5792#wallet_getcapabilities) to streamline connections and authentication into a single interaction. +This ERC introduces a new wallet connection JSON-RPC method focused on extensibility, `wallet_connect`. It leverages the modular capabilities approach defined in [ERC-5792](./eip-5792.md#wallet_getcapabilities) to streamline connections and authentication into a single interaction. ## Motivation @@ -129,7 +129,7 @@ Same as ERC-4361 specification with minor modifications: * `uri` is optional and defaults to the uri of the requesting app if not provided. * `issuedAt` is optional and defaults to the current time if not provided. -The wallet MUST return a ERC-4361-formatted message that exactly matches the requested parameters and a signature over the EIP-191 `personal_sign` hash of the message. The app SHOULD also verify that the two match for security. +The wallet MUST return a ERC-4361-formatted message that exactly matches the requested parameters and a signature over the [EIP-191](./eip-191.md) `personal_sign` hash of the message. The app SHOULD also verify that the two match for security. ```ts type Parameters = { @@ -214,7 +214,7 @@ Returning capability results alongside the connection unlocks many valuable use ### Initial Authentication Capability -To ensure immediate value, this proposal includes a capability that combines wallet connection with authentication using the widely adopted [Sign In With Ethereum (ERC-4361)](https://eips.ethereum.org/EIPS/eip-4361) standard. This optional capability simplifies the onboarding process for apps and users by combining two steps — connection and authentication — into a single interaction. Apps that prefer alternative authentication flows can implement their own capabilities without being constrained by this design. +To ensure immediate value, this proposal includes a capability that combines wallet connection with authentication using the widely adopted [Sign In With Ethereum (ERC-4361)](./eip-4361.md) standard. This optional capability simplifies the onboarding process for apps and users by combining two steps — connection and authentication — into a single interaction. Apps that prefer alternative authentication flows can implement their own capabilities without being constrained by this design. By unifying connection and authentication into one step, apps can reduce friction, improve the user experience, and minimize redundant interactions. @@ -224,9 +224,7 @@ This standard builds on existing JSON-RPC methods and complements ERC-5792 for f ## Security Considerations -Applies [ERC-4361 security principles](https://eips.ethereum.org/EIPS/eip-4361#security-considerations). As more capabilities are added, care must be taken to avoid unpredictable interactions. - -## Privacy Considerations +Applies [ERC-4361 security principles](./eip-4361.md#security-considerations). As more capabilities are added, care must be taken to avoid unpredictable interactions. Wallet addresses and any shared capabilities must be handled securely to avoid data leaks or man-in-the-middle attacks.