Key Refresh

Please refer to the Session creation section to learn how to create a new session.

Using the session object and an existing keyshare, we can easily refresh it to generate a new keyshare.

Full example:

ECDSA

App.tsx

import { EcdsaSession } from '@silencelaboratories/silent-shard-sdk';

export const refresh = async (session: EcdsaSession) => {
  // Creating a new keyshare for demo purpose. In real application, you can use an existing keyshare.
  const keyshare = await session.keygen();
  console.log('Keyshare: ', keyshare.keyIdBase64);

  const refreshedKeyshare = await session.refresh(keyshare);
  console.log('Refreshed keyshare: ', refreshedKeyshare.keyIdBase64);
};

EdDSA

App.tsx

import { EddsaSession } from '@silencelaboratories/silent-shard-sdk';

export const refresh = async (session: EddsaSession) => {
  // Creating a new keyshare for demo purpose. In real application, you can use an existing keyshare.
  const keyshare = await session.keygen();
  console.log('Keyshare: ', keyshare.keyIdBase64);

  const refreshedKeyshare = await session.refresh(keyshare);
  console.log('Refreshed keyshare: ', refreshedKeyshare.keyIdBase64);
};

• When session.refresh(keyshare) is called, the app and the server exchange messages to "refresh" the MPC wallet. Refer to Key Refresh for more details.
• This process enhances the long-term security of the MPC wallet by proactively updating the client's and server's secret shares.
• The wallet's public address or key remains unchanged during this process.
• The refreshedKeyshare object is of type EDSA Keyshare or EdDSA Keyshare and represents the client's new share of the MPC wallet.