fryorcraken

Results 52 issues of fryorcraken

# Bug Report ## Problem Flow seems broken/unresponsive when repairing keycard at sign in. ## Reproduction 1. Unpair keycard using keycard connect 2. Sign out of Status 3. Sign in...

bug
keycard
E:Bugfixes
E:Keycard

- **Version**: 0.37.3-05e8e7e ``` ▶ npm ls libp2p uint8arraylist @libp2p/websockets @libp2p/multistream-select [email protected] /home/fryorcraken/src/status-im/js-waku ├─┬ @chainsafe/[email protected] │ └─┬ @libp2p/[email protected] │ ├─┬ @libp2p/[email protected] │ │ └── [email protected] deduped │ ├─┬ [email protected] │...

need/triage

This is the one used by libp2p so should be safe: https://github.com/ipfs/aegir/blob/9fdc195ffb89ea3a339615c9f4715cd9c31cdddf/package.json#L284

track:maintenance

When using `waitForRemotePeer` with `store`, a strange behaviour happens with the underlying libp2p `peerStore`: 1. `waitForRemotePeer` resolves, I can confirm that the `peerStore` contains a peer with `store` protocol. 2....

bug
track:maintenance

## Problem In a browser environment, loss of connectivity may happen. When it happens, this would impede the application to receive and send messages. Strategies need to be designed to:...

track:restricted-run
track:production

This is a **change request** ## Problem The release process is manual, hence it is difficult to _release early, release often_. This repo will become a multi-repo soon #802 and...

## Problem See https://forum.vac.dev/t/waku-v2-scalability-studies/142/9?u=fryorcraken for original post tl;dr: 1. Browser nodes do not connect to each other with the currently available transport protocols (tcp, websocket). 2. Browser nodes do not...

track:restricted-run
epic

## Problem Currently, only _static_ peer discovery is available in js-waku, which limits the number of peers js-waku can discover. To remediate to this, [34/WAKU2-PEER-EXCHANGE](https://rfc.vac.dev/spec/34/) was designed. ## Definition of...

enhancement
track:discovery

Needs nwaku fix https://github.com/status-im/nwaku/pull/1090

blocked
track:restricted-run

## Problem It seems that `ethereum-cryptography/pbkdf2`does not use the subtle crypto API: https://github.com/status-im/status-web/pull/295/files While we do not use `ethereum-cryptography`, we do use the `noble` libraries for cryptography, by the same...

enhancement
good first issue
track:restricted-run