nick-verida
nick-verida
### Please check that this issue hasn't been reported before. - [X] I searched previous [Bug Reports](https://github.com/OpenAccess-AI-Collective/axolotl/labels/bug) didn't find any similar reports. ### Expected Behavior When installing just using pip...
PouchDB database locations should be configurable or default to somewhere guaranteed to be writable.
In a number of scenarios including deployment via AWS Amplify Next.js support the default location for PouchDB database (which I _think_ is whatever the current directory is) isn't writable. It...
Currently we use `https://assets.verida.io/registry/storageNodes/testnet.json` for our testnet. For the new Banksia testnet we need to support `https://assets.verida.io/registry/storageNodes/banksia.json`
Currently `vda-did-resolver` [swallows exception traces without logging or passing useful information](https://github.com/verida/verida-js/blob/032961cb1cfd8f5969dcab15dff724558f2302f0/packages/vda-did-resolver/src/activeDIDCount.ts#L33). This makes debugging production errors impossible - we know it failed but have no visibility into why.
When doing ``` await messaging.send("did:vda:testnet:0xf080913daa2f1F2F93dfF494a2F3E6e1A2e2C492", messageType, data, subject, config) ``` I get the following error: ``` Error: Unable to send message. Recipient does not have an inbox for that context...
When using `2.3.6` we see this error: ``` Error: Unable to create DID: Already exists at VdaDid. (/Users/nlothian/dev/verida/didmessaging/node_modules/@verida/vda-did/src/vdaDid.ts:82:23) at step (/Users/nlothian/dev/verida/didmessaging/node_modules/@verida/vda-did/dist/vdaDid.js:33:23) at Object.next (/Users/nlothian/dev/verida/didmessaging/node_modules/@verida/vda-did/dist/vdaDid.js:14:53) at fulfilled (/Users/nlothian/dev/verida/didmessaging/node_modules/@verida/vda-did/dist/vdaDid.js:5:58) at processTicksAndRejections (node:internal/process/task_queues:95:5)...
Some things that we know we aren't resilient to: * Nodes disappearing * Being logged into an app that uses a node that is no longer available * corrupt data...
Using the developer tutorial at https://developers.verida.io/docs/tutorial/verifiable_credentials the generated QR code is showing as invalid when scanned and verified via verida.network. The Vault shows the same QR code as valid. Both...
I have code that does something similar to this: ``` const did = veridaContext.account.accountDid ``` This is fine if logging in normally, but if I reconstruct the context like this...
Currently the minimal code to send a Credential looks like this: ``` const messaging = await veridaContext.getMessaging() // give is a subject that makes sense const subject = "Test COVID19...