Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Infura project ID required #647

Open
Ni3l55 opened this issue Sep 2, 2022 · 1 comment
Open

Infura project ID required #647

Ni3l55 opened this issue Sep 2, 2022 · 1 comment

Comments

@Ni3l55
Copy link

Ni3l55 commented Sep 2, 2022

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

@jrhender
Copy link
Collaborator

jrhender commented Sep 2, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants