From 0af58b9dfc90dd2f038e2e0b67bf0834c760c50a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Germ=C3=A1n=20Mart=C3=ADnez?= Date: Thu, 19 Sep 2024 18:18:30 +0100 Subject: [PATCH] Update signer property --- pages/sdk/signers/magic.mdx | 8 ++++---- pages/sdk/signers/privy.mdx | 8 ++++---- pages/sdk/signers/web3auth.mdx | 8 ++++---- 3 files changed, 12 insertions(+), 12 deletions(-) diff --git a/pages/sdk/signers/magic.mdx b/pages/sdk/signers/magic.mdx index b1883a651..0519c6218 100644 --- a/pages/sdk/signers/magic.mdx +++ b/pages/sdk/signers/magic.mdx @@ -95,7 +95,7 @@ Check out the [Safe Signers demo app](https://github.com/5afe/safe-signers) on G ### Get the provider and signer - Once the user is logged in, you can get the `provider` and `signerAddress`, which is the externally-owned account of the user that was derived from its credentials. + Once the user is logged in, you can get the `provider` and `signer`, which is the externally-owned account of the user that was derived from its credentials. {/* */} @@ -115,14 +115,14 @@ Check out the [Safe Signers demo app](https://github.com/5afe/safe-signers) on G }) const metadata = await magic.user.getInfo() - const signerAddress = metadata.publicAddress + const signer = metadata.publicAddress ``` {/* */} - With the `provider` and `signerAddress` you are ready to instantiate any of the kits from the Safe\{Core\} SDK and set up or use this signer as a Safe owner. + With the `provider` and `signer` you are ready to instantiate any of the kits from the Safe\{Core\} SDK and set up or use this signer as a Safe owner. ### Logout @@ -141,7 +141,7 @@ Check out the [Safe Signers demo app](https://github.com/5afe/safe-signers) on G ## Recap and further reading -After following this guide, you are able to create a Safe signer using Magic and get the `provider` and `signerAddress` required to initialize the kits from the Safe\{Core\} SDK. +After following this guide, you are able to create a Safe signer using Magic and get the `provider` and `signer` required to initialize the kits from the Safe\{Core\} SDK. Learn more about Magic by checking the following resources: diff --git a/pages/sdk/signers/privy.mdx b/pages/sdk/signers/privy.mdx index e93bdd8ef..e8922014c 100644 --- a/pages/sdk/signers/privy.mdx +++ b/pages/sdk/signers/privy.mdx @@ -117,7 +117,7 @@ Check out the [Safe Signers demo app](https://github.com/5afe/safe-signers) on G ### Get the provider and signer - Once the user is logged in, you can get the `provider` and `signerAddress`, which is the externally-owned account of the user that was derived from its credentials. + Once the user is logged in, you can get the `provider` and `signer`, which is the externally-owned account of the user that was derived from its credentials. To do that there is a `useEffect()` that is executed when any of the `ready`, `authenticated`, `readyWallets` and `wallets` variables have its value updated. Once they all are `true` and `wallets` has a length greater than zero, you have access to the `wallets` first element, which is the user's connected signer. @@ -143,7 +143,7 @@ Check out the [Safe Signers demo app](https://github.com/5afe/safe-signers) on G transport: custom(ethereumProvider) }) - const signerAddress = wallets[0].address + const signer = wallets[0].address } } init() @@ -154,7 +154,7 @@ Check out the [Safe Signers demo app](https://github.com/5afe/safe-signers) on G {/* */} - With the `provider` and `signerAddress` you are ready to instantiate any of the kits from the Safe\{Core\} SDK and set up or use this signer as a Safe owner. + With the `provider` and `signer` you are ready to instantiate any of the kits from the Safe\{Core\} SDK and set up or use this signer as a Safe owner. ### Logout @@ -172,7 +172,7 @@ Check out the [Safe Signers demo app](https://github.com/5afe/safe-signers) on G ## Recap and further reading -After following this guide, you are able to create a Safe signer using Privy and get the `provider` and `signerAddress` required to initialize the kits from the Safe\{Core\} SDK. +After following this guide, you are able to create a Safe signer using Privy and get the `provider` and `signer` required to initialize the kits from the Safe\{Core\} SDK. Learn more about Privy by checking the following resources: diff --git a/pages/sdk/signers/web3auth.mdx b/pages/sdk/signers/web3auth.mdx index 8bbef1563..55447b9c6 100644 --- a/pages/sdk/signers/web3auth.mdx +++ b/pages/sdk/signers/web3auth.mdx @@ -122,7 +122,7 @@ Check out the [Safe Signers demo app](https://github.com/5afe/safe-signers) on G ### Get the provider and signer - Once the user is logged in, you can get the `provider` and `signerAddress`, which is the externally-owned account of the user that was derived from its credentials. + Once the user is logged in, you can get the `provider` and `signer`, which is the externally-owned account of the user that was derived from its credentials. {/* */} @@ -141,14 +141,14 @@ Check out the [Safe Signers demo app](https://github.com/5afe/safe-signers) on G transport: custom(web3authProvider) }) - const signerAddress = await provider.getAddresses())[0] + const signer = await provider.getAddresses())[0] ``` {/* */} - With the `provider` and `signerAddress` you are ready to instantiate any of the kits from the Safe\{Core\} SDK and set up or use this signer as a Safe owner. + With the `provider` and `signer` you are ready to instantiate any of the kits from the Safe\{Core\} SDK and set up or use this signer as a Safe owner. ### Logout @@ -166,7 +166,7 @@ Check out the [Safe Signers demo app](https://github.com/5afe/safe-signers) on G ## Recap and further reading -After following this guide, you are able to create a Safe signer using Web3Auth and get the `provider` and `signerAddress` required to initialize the kits from the Safe\{Core\} SDK. +After following this guide, you are able to create a Safe signer using Web3Auth and get the `provider` and `signer` required to initialize the kits from the Safe\{Core\} SDK. Learn more about Web3Auth by checking the following resources: