You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @Ni3l55 , yes, due to a breaking change on Infura's side, a projectID is now necessary. I will coordinate with you to determine which Infura project we should use to get this functionality restored.
I’m suddenly receiving a ‘project ID required’ when using
didRegistry.ipfsStore.save(…)
Probably coming from the ipfs-http-client in the DidStore.
Might be related to PR #638 ?
I never had to specify infuraID (only for the resolver)
My initialization which was unchanged:
const { connectToCacheServer } = await initWithPrivateKeySigner(MY_PRIVATE_KEY, NODE_RPC_URL); const { connectToDidRegistry, assetsService, verifiableCredentialsService } = await connectToCacheServer(); const { didRegistry } = await connectToDidRegistry();
And then using:
didRegistry.ipfsStore.save(stringifiedVC);
results in:
[ERROR]: project id required
The text was updated successfully, but these errors were encountered: