Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / verida/verida-js issues and pull requests
#407 - [vda-node-xxx] Update for `StorageNodeRegistry` contract update
Issue -
State: open - Opened by ITStar10 9 months ago
#406 - Update default RPC URLs
Pull Request -
State: closed - Opened by aurelticot 9 months ago
#405 - Update default RPC URLs
Issue -
State: closed - Opened by aurelticot 9 months ago
#404 - Allow optional Polygon private key for read-only operations
Issue -
State: open - Opened by aurelticot 9 months ago
Labels: enhancement
#403 - Feature/397 vda reward client
Pull Request -
State: closed - Opened by ITStar10 10 months ago
#402 - Redefine the engine requirement and the typescript config
Issue -
State: open - Opened by aurelticot 10 months ago
#401 - Feature/397 vda reward client create
Pull Request -
State: closed - Opened by ITStar10 10 months ago
#400 - Do not pass the `openUrl` property on the deep link
Issue -
State: open - Opened by aurelticot 10 months ago
Labels: enhancement
#397 - [vda-reward-client] Create client package for `vda-reward-contract`
Issue -
State: closed - Opened by ITStar10 10 months ago
#396 - [vda-node-xxx] Add enable/disable withdrawl
Issue -
State: closed - Opened by ITStar10 11 months ago
#395 - Bug: New mainnet account shows testnet label
Issue -
State: closed - Opened by pranavburnwal 11 months ago
- 1 comment
#394 - Fix/393 message to same inbox closed
Pull Request -
State: closed - Opened by tahpot 11 months ago
#393 - Sending multiple messages to same inbox fails
Issue -
State: closed - Opened by tahpot 11 months ago
Labels: bug
#392 - Fix `getContextNameFromHash` edge case not returning the expected value
Issue -
State: open - Opened by aurelticot 11 months ago
- 1 comment
Labels: bug
#392 - Fix `getContextNameFromHash` edge case not returning the expected value
Issue -
State: open - Opened by aurelticot 11 months ago
Labels: bug
#391 - Improve notes for 3.0.0 release
Pull Request -
State: closed - Opened by tahpot 11 months ago
#390 - Merge develop into main
Pull Request -
State: closed - Opened by tahpot 11 months ago
#390 - Merge develop into main
Pull Request -
State: closed - Opened by tahpot 11 months ago
#389 - Feature/388 support destroy context account
Pull Request -
State: closed - Opened by tahpot 12 months ago
#388 - Support destroying a context or an entire account
Issue -
State: closed - Opened by tahpot 12 months ago
Labels: enhancement
#387 - Support handling context hash
Issue -
State: open - Opened by tahpot 12 months ago
#386 - Fix/node unavailable issues
Pull Request -
State: closed - Opened by tahpot 12 months ago
#385 - Issues relating to a node being unavailable
Issue -
State: closed - Opened by tahpot 12 months ago
- 1 comment
#384 - [client-ts] Fix: Refactor migration
Pull Request -
State: closed - Opened by tahpot 12 months ago
#384 - [client-ts] Fix: Refactor migration
Pull Request -
State: closed - Opened by tahpot 12 months ago
#383 - Migration has incorrect encryption key
Issue -
State: closed - Opened by tahpot 12 months ago
Labels: bug
#382 - Fix migration opening database with wrong config
Pull Request -
State: closed - Opened by aurelticot 12 months ago
- 1 comment
#382 - Fix migration opening database with wrong config
Pull Request -
State: closed - Opened by aurelticot 12 months ago
- 1 comment
#381 - Feature/380 mainnet updates
Pull Request -
State: closed - Opened by ITStar10 12 months ago
#380 - [All] Update for mainnet release
Issue -
State: closed - Opened by ITStar10 12 months ago
#379 - Add the missing `environment` property to `AccountVaultRequest`
Pull Request -
State: closed - Opened by aurelticot 12 months ago
- 1 comment
#378 - Add the `environment` property to `AccountVaultRequest`
Issue -
State: closed - Opened by aurelticot 12 months ago
- 1 comment
Labels: bug
#377 - Fix/376 node loop issue
Pull Request -
State: closed - Opened by tahpot 12 months ago
#376 - DID creation infinite loop if only 2 nodes on the network
Issue -
State: open - Opened by tahpot 12 months ago
- 1 comment
Labels: bug
#376 - DID creation infinite loop if only 2 nodes on the network
Issue -
State: open - Opened by tahpot 12 months ago
- 1 comment
Labels: bug
#375 - Close context doesn't close all databases
Issue -
State: open - Opened by tahpot 12 months ago
Labels: bug
#374 - Update UX on expired connection request
Issue -
State: open - Opened by aurelticot 12 months ago
- 1 comment
Labels: enhancement
#373 - The Verida Connect modal should provide both the deep link and the QR code
Issue -
State: open - Opened by aurelticot about 1 year ago
- 1 comment
Labels: enhancement
#372 - The Verida Connect modal should not add a `mobile` or `desktop` class to the `body` in the DOM
Issue -
State: open - Opened by aurelticot about 1 year ago
- 1 comment
#371 - The Verida Connect modal is not cleaned from the DOM and can even be added multiple times
Issue -
State: closed - Opened by aurelticot about 1 year ago
- 1 comment
#370 - Support Verida Connect network type
Pull Request -
State: closed - Opened by tahpot about 1 year ago
#370 - Support Verida Connect network type
Pull Request -
State: closed - Opened by tahpot about 1 year ago
#369 - Support network environment with Verida Connect
Issue -
State: closed - Opened by tahpot about 1 year ago
Labels: enhancement
#369 - Support network environment with Verida Connect
Issue -
State: closed - Opened by tahpot about 1 year ago
Labels: enhancement
#368 - Update data signing to support multiple sig schemes
Pull Request -
State: closed - Opened by tahpot about 1 year ago
#367 - Support verification of profile domains
Pull Request -
State: closed - Opened by tahpot about 1 year ago
#366 - Support well-known domain verification for user profiles
Issue -
State: closed - Opened by tahpot about 1 year ago
- 2 comments
#365 - Support multiple signature schemes on saved data
Issue -
State: closed - Opened by tahpot about 1 year ago
Labels: enhancement
#364 - Support jwt-sd signature scheme
Issue -
State: open - Opened by tahpot about 1 year ago
Labels: enhancement
#363 - Fix typescript build errors
Pull Request -
State: closed - Opened by tahpot about 1 year ago
#362 - Data migration: Typescript errors
Issue -
State: closed - Opened by tahpot about 1 year ago
#361 - AutoAccount doesn't implement disconnect
Issue -
State: closed - Opened by nick-verida about 1 year ago
#360 - Database connections not being closed when messages are sent
Issue -
State: closed - Opened by nick-verida about 1 year ago
- 3 comments
#359 - [vda-common] Updated mainnet contract addresses
Pull Request -
State: closed - Opened by ITStar10 about 1 year ago
#358 - [vda-common] Update contract addresses for mainnet
Issue -
State: closed - Opened by ITStar10 about 1 year ago
#357 - Consider an error framework for identifiable errors thrown by the library
Issue -
State: open - Opened by aurelticot about 1 year ago
- 1 comment
#356 - vda-did-resolver swallows exceptions without logging
Issue -
State: open - Opened by nick-verida about 1 year ago
- 2 comments
#355 - Mainnet release
Pull Request -
State: closed - Opened by tahpot about 1 year ago
#354 - Feature/353 support replicating contexts
Pull Request -
State: closed - Opened by tahpot about 1 year ago
- 1 comment
#353 - Support replication of application context
Issue -
State: open - Opened by tahpot about 1 year ago
Labels: enhancement
#352 - [vda-node-client] Function list for `vda-node-client` and `vda-node-staking` packages
Issue -
State: closed - Opened by ITStar10 about 1 year ago
- 1 comment
#351 - Explore multi-party encryption
Issue -
State: open - Opened by tahpot about 1 year ago
Labels: enhancement
#351 - Explore multi-party encryption
Issue -
State: open - Opened by tahpot about 1 year ago
- 1 comment
Labels: enhancement
#350 - Optimise API documentation generation
Issue -
State: open - Opened by aurelticot about 1 year ago
- 1 comment
Labels: documentation
#349 - [web-helpers] Hotfix for WebUser.connect() error
Pull Request -
State: closed - Opened by tahpot about 1 year ago
#348 - Fix/347 - Fix `WebUser.connect` crashing when getting public profile
Pull Request -
State: open - Opened by aurelticot about 1 year ago
Labels: bug
#348 - Fix/347 - Fix `WebUser.connect` crashing when getting public profile
Pull Request -
State: open - Opened by aurelticot about 1 year ago
Labels: bug
#348 - Fix/347 - Fix `WebUser.connect` crashing when getting public profile
Pull Request -
State: open - Opened by aurelticot about 1 year ago
Labels: bug
#348 - Fix/347 - Fix `WebUser.connect` crashing when getting public profile
Pull Request -
State: open - Opened by aurelticot about 1 year ago
Labels: bug
#348 - Fix/347 - Fix `WebUser.connect` crashing when getting public profile
Pull Request -
State: closed - Opened by aurelticot about 1 year ago
Labels: bug
#347 - Fix `WebUser.connect` crashing when getting public profile
Issue -
State: open - Opened by aurelticot about 1 year ago
Labels: bug
#347 - Fix `WebUser.connect` crashing when getting public profile
Issue -
State: open - Opened by aurelticot about 1 year ago
Labels: bug
#347 - Fix `WebUser.connect` crashing when getting public profile
Issue -
State: closed - Opened by aurelticot about 1 year ago
Labels: bug
#347 - Fix `WebUser.connect` crashing when getting public profile
Issue -
State: open - Opened by aurelticot about 1 year ago
Labels: bug
#346 - [encryption-utils] v2.2.2 release
Pull Request -
State: closed - Opened by tahpot about 1 year ago
- 1 comment
#345 - Don't force global JSON.stringify to be sortable
Pull Request -
State: closed - Opened by tahpot about 1 year ago
- 1 comment
#344 - Feature/326 mainnet test new
Pull Request -
State: open - Opened by ITStar10 over 1 year ago
- 1 comment
#344 - Feature/326 mainnet test new
Pull Request -
State: closed - Opened by ITStar10 over 1 year ago
- 1 comment
#344 - Feature/326 mainnet test new
Pull Request -
State: open - Opened by ITStar10 over 1 year ago
- 1 comment
#344 - Feature/326 mainnet test new
Pull Request -
State: open - Opened by ITStar10 over 1 year ago
- 1 comment
#343 - Remove JSON.stringify global scope hot replacement with `json.sortify`
Issue -
State: open - Opened by Eengineer1 over 1 year ago
- 1 comment
Labels: bug
#343 - Remove JSON.stringify global scope hot replacement with `json.sortify`
Issue -
State: open - Opened by Eengineer1 over 1 year ago
- 1 comment
Labels: bug
#343 - Remove JSON.stringify global scope hot replacement with `json.sortify`
Issue -
State: closed - Opened by Eengineer1 over 1 year ago
- 1 comment
Labels: bug
#343 - Remove JSON.stringify global scope hot replacement with `json.sortify`
Issue -
State: open - Opened by Eengineer1 over 1 year ago
- 1 comment
Labels: bug
#343 - Remove JSON.stringify global scope hot replacement with `json.sortify`
Issue -
State: closed - Opened by Eengineer1 over 1 year ago
- 1 comment
Labels: bug
#342 - pin did-jwt-vc version
Pull Request -
State: closed - Opened by nick-verida over 1 year ago
#342 - pin did-jwt-vc version
Pull Request -
State: open - Opened by nick-verida over 1 year ago
#342 - pin did-jwt-vc version
Pull Request -
State: open - Opened by nick-verida over 1 year ago
#341 - Unable to send message. Recipient does not have an inbox for that context (Verida: Vault)
Issue -
State: open - Opened by nick-verida over 1 year ago
- 1 comment
#341 - Unable to send message. Recipient does not have an inbox for that context (Verida: Vault)
Issue -
State: open - Opened by nick-verida over 1 year ago
- 1 comment
#340 - Unable to create DID: Already exists
Issue -
State: open - Opened by nick-verida over 1 year ago
- 1 comment
#340 - Unable to create DID: Already exists
Issue -
State: open - Opened by nick-verida over 1 year ago
- 1 comment
#340 - Unable to create DID: Already exists
Issue -
State: open - Opened by nick-verida over 1 year ago
- 1 comment
#340 - Unable to create DID: Already exists
Issue -
State: open - Opened by nick-verida over 1 year ago
- 1 comment
#340 - Unable to create DID: Already exists
Issue -
State: open - Opened by nick-verida over 1 year ago
- 1 comment
#339 - Closes 338. Map the DID string to the correct DID format
Pull Request -
State: closed - Opened by nick-verida over 1 year ago
#339 - Closes 338. Map the DID string to the correct DID format
Pull Request -
State: closed - Opened by nick-verida over 1 year ago
#339 - Closes 338. Map the DID string to the correct DID format
Pull Request -
State: closed - Opened by nick-verida over 1 year ago
#339 - Closes 338. Map the DID string to the correct DID format
Pull Request -
State: closed - Opened by nick-verida over 1 year ago
#339 - Closes 338. Map the DID string to the correct DID format
Pull Request -
State: closed - Opened by nick-verida over 1 year ago