Skip to content

Commit

Permalink
Change the openlogin ed25519 conversion package
Browse files Browse the repository at this point in the history
  • Loading branch information
yashovardhan committed Dec 2, 2024
1 parent a8ef837 commit 85506d5
Show file tree
Hide file tree
Showing 5 changed files with 8 additions and 8 deletions.
2 changes: 1 addition & 1 deletion docs/connect-blockchain/near/web.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ provider for Near in Web3Auth, so we must use the private key to make RPC calls
To access the user's private key, the application can use the function
`web3auth.provider.request({method: "private_key"})` from the Web3Auth provider. Yet, this key
cannot be used with Near since it requires the `ed25519` key. Therefore, we must use the
`getED25519Key()` function from `@toruslabs/openlogin-ed25519` to convert the `secp256k1` key to an
`getED25519Key()` function from `@web3auth/base-provider` to convert the `secp256k1` key to an
`ed25519` key.

```tsx
Expand Down
2 changes: 1 addition & 1 deletion docs/features/server-side-verification.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -239,7 +239,7 @@ const app_pub_key = getPublicCompressed(
<TabItem value="ed25519">

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

const app_scoped_privkey = await web3auth.provider?.request({
// focus-next-line
Expand Down
8 changes: 4 additions & 4 deletions docs/migration-guides/tkey-v11-to-v15.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -99,11 +99,11 @@ from v15, developers can use the tKey with the Blockchain ecosystem which uses t
:::warning

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

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

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

Expand Down
2 changes: 1 addition & 1 deletion docs/sdk/pnp/react-native/usage.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@ export type LoginParams = BaseRedirectParams & {
*
* Note: This parameter won't change format of private key returned by auth service. Private key returned
* by auth service is always `secp256k1`. As of now you have to convert it to `'ed25519'` if you want.
* You can use `@toruslabs/openlogin-ed25519` npm package for this purpose.
* You can use `@web3auth/base-provider` npm package for this purpose.
*
*
* @defaultValue secp256k1
Expand Down
2 changes: 1 addition & 1 deletion src/common/sdk/pnp/web/_auth-login-settings.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ export type LoginParams = BaseRedirectParams & {
*
* Note: This parameter won't change format of private key returned by auth. Private key returned
* by auth is always `secp256k1`. As of now you have to convert it to `'ed25519'` if you want.
* You can use `@toruslabs/openlogin-ed25519` npm package for this purpose.
* You can use `@web3auth/base-provider` npm package for this purpose.
*
*
* @defaultValue secp256k1
Expand Down

0 comments on commit 85506d5

Please sign in to comment.