Controlling NCW Generated keys on device

Support
1

Hi,

I can see that upon creation of MPC keys (in the demo app or my web app), two entries/files are generated "SECURE-STORAGE_privateKeyForCSR" and SECURE-STORAGE_cosignerSecureData. When the SDK retrieves the keys to sign a transaction I can see it’s expecting both. For my use case ideally I’d want one file / key generated. My question is can this be controlled,? Why does the web SDK creates two files and how are they being used? I’m assuming it’s related to the
ISecureStorageProvider interface that is passed to the FireblocksNCWFactory, but I don’t see a way to initialize the SDK without providing an implementation of that interface.

fireblocksNCW = await FireblocksNCWFactory({
env: ENV_CONFIG.NCW_SDK_ENV as TEnv,
logLevel: “INFO”,
deviceId,
messagesHandler,
eventsHandler,
secureStorageProvider,
logger,
reporting: {enabled: true},
});

Thanks!

2

Hi, My name is Mohammed and I am from Fireblocks.
you are right it is due to the secure storage provider and it needs both for the signing process. This is how our demo is configured and would need both files.
Kindly check out this guide related to the key storage options you have

Thanks

3

Hi @B_MCC, Wilfred here from Fireblocks.

Could you clarify what is it that you are trying to achieve and what specific issue are you facing?