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

All messages show encrypted, Impossible to communicate with each other or transact. #25

Open
nostitos opened this issue Apr 14, 2023 · 9 comments

Comments

@nostitos
Copy link

nostitos commented Apr 14, 2023

It's hard to describe, Simply nothing works anymore.

We're logged with primary keys.

@plebhash
Copy link

plebhash commented Jul 26, 2024

any updates here?

facing similar issues with @diegokolling

according to @hugohn it's related to Matrix SDK?

@hugohn
Copy link
Collaborator

hugohn commented Jul 27, 2024

Correct, the error is related to the Matrix SDK.

Current solution is to recover the wallet manually. I'm sharing the steps below.

How to manually recovering a Matrix-backed collaborative wallet

  1. Back up your keys and wallets (BSMS), if you have not.
  2. Delete the chat, and the associated wallet.
  3. Have all co-signers update the app.
  4. Have all co-signers recover their respective key in the app.
  5. Create a new group chat and invite the original members.
  6. Once all original members have joined (and only then), recover the original wallet in the new chat by doing "Create a new collaborative wallet" > "Recover wallet" > Select BSMS file from step 1.

@diegokolling
Copy link

diegokolling commented Jul 27, 2024 via email

@plebhash
Copy link

plebhash commented Jul 27, 2024

on a side note: I used the Element client (which is built on the Matrix protocol) on a regular basis until not long ago.

this would always happen while bootstrapping new devices on the same account.


Correct, the error is related to the Matrix SDK.

Current solution is to recover the wallet manually. I'm sharing the steps below.

How to manually recovering a Matrix-backed collaborative wallet

  1. Back up your keys and wallets (BSMS), if you have not.
  2. Delete the chat, and the associated wallet.
  3. Have all co-signers update the app.
  4. Have all co-signers recover their respective key in the app.
  5. Create a new group chat and invite the original members.
  6. Once all original members have joined (and only then), recover the original wallet in the new chat by doing "Create a new collaborative wallet" > "Recover wallet" > Select BSMS file from step 1.

will these steps also work for our case?

I believe @diegokolling already had the nunchuk app on this mobile for a while. I on the other hand had just installed it, so I think our case sort of falls into the "bootstrapping" category as well (similar to what I described about my experience with Element above)

@hugohn
Copy link
Collaborator

hugohn commented Jul 28, 2024

@diegokolling you shouldn’t get the Encrypted messages if you do a fresh install. However all members must do it.

@diegokolling
Copy link

diegokolling commented Jul 28, 2024 via email

@hugohn
Copy link
Collaborator

hugohn commented Jul 28, 2024

No, I’m not sure what you meant by “some kind of authentication”?

If you don’t do a fresh install, you’ll be stuck with the old set of Matrix E2EE keys, so messages could not be decrypted. This is unfortunately the architecture of the free collaborative wallet which currently relies on the Matrix SDK.

A fresh install would allow all parties to reset their key sets and start over. As long as you have the original keys and wallet config backed up, you should always be able to recover the same collaborative wallet within a new chat.

For a more reliable version of collaborative wallet, I suggest the Finney service.

@diegokolling
Copy link

diegokolling commented Jul 28, 2024 via email

@Cyberpunk-Hardware
Copy link

Can you please confirm that Finney doesn't use matrix and what it uses?

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

5 participants