Skip to content

Commit 85506d5

Browse files
committed
Change the openlogin ed25519 conversion package
1 parent a8ef837 commit 85506d5

File tree

5 files changed

+8
-8
lines changed

5 files changed

+8
-8
lines changed

docs/connect-blockchain/near/web.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ provider for Near in Web3Auth, so we must use the private key to make RPC calls
9292
To access the user's private key, the application can use the function
9393
`web3auth.provider.request({method: "private_key"})` from the Web3Auth provider. Yet, this key
9494
cannot be used with Near since it requires the `ed25519` key. Therefore, we must use the
95-
`getED25519Key()` function from `@toruslabs/openlogin-ed25519` to convert the `secp256k1` key to an
95+
`getED25519Key()` function from `@web3auth/base-provider` to convert the `secp256k1` key to an
9696
`ed25519` key.
9797

9898
```tsx

docs/features/server-side-verification.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -239,7 +239,7 @@ const app_pub_key = getPublicCompressed(
239239
<TabItem value="ed25519">
240240

241241
```ts
242-
import { getED25519Key } from "@toruslabs/openlogin-ed25519";
242+
import { getED25519Key } from "@web3auth/base-provider";
243243

244244
const app_scoped_privkey = await web3auth.provider?.request({
245245
// focus-next-line

docs/migration-guides/tkey-v11-to-v15.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -99,11 +99,11 @@ from v15, developers can use the tKey with the Blockchain ecosystem which uses t
9999
:::warning
100100

101101
Please note, this is a native support for `ed25519` curve in tKey SDK, unlike the previous
102-
integrations where, using the `openlogin-ed25519` package, a sub key was derived for supporting the
103-
curve.
102+
integrations where, using the `@web3auth/base-provider` package, a sub key was derived for
103+
supporting the curve.
104104

105-
If you are already using the `openlogin-ed25519` package for your application, please do not upgrade
106-
to this method as **it might cause the keys to change** for existing users.
105+
If you are already using the `@web3auth/base-provider` package for your application, please do not
106+
upgrade to this method as **it might cause the keys to change** for existing users.
107107

108108
For new integrations, we recommend using this new flow of native support for `ed25519` curve.
109109

docs/sdk/pnp/react-native/usage.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ export type LoginParams = BaseRedirectParams & {
140140
*
141141
* Note: This parameter won't change format of private key returned by auth service. Private key returned
142142
* by auth service is always `secp256k1`. As of now you have to convert it to `'ed25519'` if you want.
143-
* You can use `@toruslabs/openlogin-ed25519` npm package for this purpose.
143+
* You can use `@web3auth/base-provider` npm package for this purpose.
144144
*
145145
*
146146
* @defaultValue secp256k1

src/common/sdk/pnp/web/_auth-login-settings.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ export type LoginParams = BaseRedirectParams & {
7070
*
7171
* Note: This parameter won't change format of private key returned by auth. Private key returned
7272
* by auth is always `secp256k1`. As of now you have to convert it to `'ed25519'` if you want.
73-
* You can use `@toruslabs/openlogin-ed25519` npm package for this purpose.
73+
* You can use `@web3auth/base-provider` npm package for this purpose.
7474
*
7575
*
7676
* @defaultValue secp256k1

0 commit comments

Comments
 (0)