Replying to Avatar The Daniel 🖖

I did test earlier by restoring a relay backup from a different client and it worked for me, but might warrant further testing. This is definitely an edge case.
Avatar
idsera 4d ago 💬 1

nostr:nevent1qvzqqqqqqypzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uqzqrhafj3zlnlc7gz35xk0su4988qplz34wd4l54yyu7lymr7mkva6vzpg9s

Reply to this note

Please Login to reply.

Discussion

Avatar
The Daniel 🖖 4d ago 💬 1

Thanks, I think we’ve got it solved! There’s no bug in nos2x, it was just a lack of detection method for the older wallet format created by the previous app. Bug was on our end.

Avatar
idsera 4d ago 💬 1

I still reproduce the same problem.

Avatar
The Daniel 🖖 4d ago 💬 1

It hasn’t been merged yet.

Avatar
The Daniel 🖖 3d ago 💬 1

OK, the fix has been merged and tested.

I created a new wallet with the Jumble Spark prototype using the Keys.band extension, which does not support NIP-44 encryption, so the backup was encoded using NIP-04.

I then switched to nos2x to decrypt and restore the same wallet using Zap Cooking, and it worked as expected.

Your relay backup should work now.

Avatar
idsera 3d ago 💬 2

Yes, worked ok now. I was able to restore, thanks.

Avatar
idsera 3d ago

Avatar
The Daniel 🖖 3d ago