pull down to refresh

@ek has overhauled wallets with some of the things we've learned over the last 6 months or so:

attach wallets, not protocols
attach multiple versions of the same wallet and protocol
implicit send wallet device sync
- device sync is on by default and you only need to bother with copying passphrases when adding additional devices
improved logging

The UI/UX is admittedly a little rough around the edges still, but the foundation, the hard part, is better suited to our plans and needs. We'll iterate on UI/UX based on feedback and please let us know if you experience any problems.

if you are being asked for your passphrase unexpectedly

You will need to click reset, creating a new passphrase, and attach your sending wallets again.

Our on-device migration to 'wallets v2' failed for some of you. There was a bug that re-encrypted your wallets with a new passphrase which will make your existing attached sending wallets inaccessible. We're so sorry and know how frustrating this stuff is.

I'll be online all day to help with any problems. Please mention me or ek if you need help.

View all commits here: https://github.com/stackernews/stacker.news/commits/master/

Since starting the Open Source Contributor Award Rules (OSCARs), we've paid a total of 24.8m sats to 49 contributors for 253 contributions! View a nearly up to date list of contribution awards here: https://github.com/stackernews/stacker.news/blob/master/awards.csv

Previous release: #1010425

view all related items

100 sats \ 13 replies \ @siggy47 5h

Now I am getting this message on mobile when attempting to access my wallets:

failed to load wallets decryption error

@ek @k00b

36 sats \ 12 replies \ @ek 4h

Thank you, so decryption is indeed failing.

But you can load your wallets fine on desktop?

100 sats \ 9 replies \ @siggy47 4h

Yes. everything is fine on desktop.

536 sats \ 4 replies \ @k00b OP 4h

You're using grapheneOS on mobile right siggy? I wonder if the browser doesn't support a feature we expect or something.

0 sats \ 0 replies \ @ek 4h

ohhh, this is a good hint

0 sats \ 2 replies \ @siggy47 4h

Correct

0 sats \ 1 reply \ @ek 31m

Hey, sorry we still haven't figured out what's going wrong on your mobile device. We just pushed some more code. Do you now see decryption error: OperationError?

view all 1 replies

36 sats \ 3 replies \ @ek 4h

Can you give me a screenshot of the wallets page on desktop so I can check if what you see is also what I expect you to see?

100 sats \ 1 reply \ @siggy47 4h

deleted by author

36 sats \ 0 replies \ @ek 4h

Okay, that's what I expected, mhh.

You can delete the screenshot now if you want

reply on another page

0 sats \ 0 replies \ @siggy47 4h

deleted by author

0 sats \ 1 reply \ @k00b OP 4h

Do we still clear storage on logout? That might be a quick fix if so.

0 sats \ 0 replies \ @ek 4h

No, because there's nothing to clear anymore

edit: oh, except the key ...

655 sats \ 1 reply \ @0xbitcoiner 8h

Great job!

When you open any page on SN for the first time, that orange square pops up next to the nym. It disappears really fast though, I don’t think it used to do that. browser version.

55 sats \ 0 replies \ @ek 8h

damn, that's a regression, thanks for the report

77 sats \ 1 reply \ @Carresan 5h

if you are being asked for your passphrase unexpectedly

I saw this message , just clicked reset and attached coinos wallet. All working smoothly. Thanks for this upgrade!

15 sats \ 0 replies \ @ek 4h

thanks for the feedback!

100 sats \ 10 replies \ @siggy47 8h

Okay, I created a new send passphrase on dektop linux, and things seem fine. On mobile, I can't access wallet, nor can I zap. It just keeps reloading.

36 sats \ 9 replies \ @ek 7h

mhhh, not sure yet why it would load forever

will keep you updated

100 sats \ 8 replies \ @siggy47 7h

Okay. Can you explain how to unsync devices now? Maybe I can unsync, load a new passphrase on mobile, then live with them unsynced for a while?

36 sats \ 3 replies \ @k00b OP 7h

ek removed the ability to unsync.

unsynced wallets are less secure
it made the code more complicated

I'm sorry siggy. I'm confident you'll need to reset and reattach sending wallets.

0 sats \ 2 replies \ @siggy47 7h

That's okay, but I can't reset on mobile. It keeps reloading. The send ability I have on desktop is not synced with mobile, so I can't zap on my phone. Timing sucks, since I'm going away tomorrow and won't have access to my desktop, lan for nodes, etc. Oh well. I guess I'll be cc'ing for a while.

36 sats \ 1 reply \ @ek 7h

I should have added code to show errors to users. I think loading your wallets is failing.

Will do that now, we should definitely be able to get your wallets to load on mobile within the next few hours

view all 1 replies

36 sats \ 3 replies \ @ek 7h

There's no unsync anymore, all sending wallets are now always stored encrypted on the server.

The first device you opened SN with today gets to set the key, and when you use a different device, it will either already have the same key, or it won't, then it will ask you for the passphrase to derive the same key.

But I think something went wrong with detecting existing keys, so we accidentally generated new keys for some 🙈

But not sure if your wallets loading forever on mobile is related to that.

0 sats \ 2 replies \ @k00b OP 7h

I was weary of that new vibe coded hook that you made last minute. Is that the cause?

0 sats \ 1 reply \ @ek 7h

The bug is at least happening in there, but it might also have happened with what I had before

it wasn't vibe coded though 👀

view all 1 replies

99 sats \ 2 replies \ @unschooled 7h

things seemed pretty smooth for me via lnd attachment option. no apparent interruption except for a few moments where i got a 500 internal server error.

11 sats \ 1 reply \ @ek 4h

thanks for the feedback, glad it worked for you

21 sats \ 0 replies \ @unschooled 4h

thanks for your work. logs and wallet pages are looking pretty slick.

21 sats \ 1 reply \ @jasonb 1h

I’m guessing the gun requirements were lightened up? I’m a triple threat again!

50 sats \ 0 replies \ @k00b OP 1h

Device sync is on by default now.

222 sats \ 4 replies \ @BlokchainB 7h

Okay I am back in action! Should I establish a passphrase now?

84 sats \ 1 reply \ @k00b OP 7h

I'd wait to establish the passphrase until you need to sync with a device and can write it down.

100 sats \ 0 replies \ @BlokchainB 7h

Okay thank you.

0 sats \ 1 reply \ @BlokchainB 7h

Nvm I see the app already set one for me after I reset

57 sats \ 0 replies \ @k00b OP 7h

Yes, it gives you a one immediately so that your wallets are properly secured even without syncing to other devices yet.

33 sats \ 1 reply \ @SimpleStacker 4h

I didn't get any notifications or messages to do anything. Does that mean no action is needed on my part? I seem to be able to zap from my wallet (Alby Desktop connected via NWC)

30 sats \ 0 replies \ @ek 3h

Yes, don’t need to do anything, that’s how it was supposed to go

42 sats \ 0 replies \ @hasherstacker 6h

Thank you SN Team for the nice job. SN is self-custodial

100 sats \ 5 replies \ @BlokchainB 7h

Sigh! I wish we had more warning this was going to come. I am not going to be able to resync my wallets till this evening. Thus I may have trouble zapping all day.

70 sats \ 2 replies \ @k00b OP 7h

I'd be happy to buy you some cowboy credits for your trouble and to keep the zaps coming.

100 sats \ 0 replies \ @BlokchainB 7h

Thanks but I have a workaround that I do in situations like this. It’s annoying but I can get back up and zapping in a bit.

Thanks for the offer

0 sats \ 0 replies \ @LibertasBR 6h

This is a great offer, no jk.

55 sats \ 1 reply \ @0xbitcoiner 7h

Stuff like this is exactly why I’ve been keeping a buffer (~5k) of sats and CCs in my SN wallet. That way I 'never' run into issues! If you need some CCs, just say it, I’ll lend you some!

33 sats \ 0 replies \ @BlokchainB 7h

Thanks. I do have a workaround but it’s just a real pain in rear to do. But let me get working on it

150 sats \ 2 replies \ @ek 8h

Found a bug that is related to why old passphrases no longer work, but not sure I can fix it in a way that they will start working again, only that it doesn't happen again.

0 sats \ 1 reply \ @k00b OP 8h

If you want to submit a pr, I can try to get it deployed before some folks encounter the bug.

0 sats \ 0 replies \ @ek 8h

okay, should be up in 10 minutes

edit: nooo, can't reproduce anymore

33 sats \ 1 reply \ @emoclew 4h freebie

Adding my ln recieve and nwc send, I noticed the new layout, nice layout and good ux, cashu me is available which is pretty cool. Nice touch

0 sats \ 0 replies \ @ek 4h

thanks and welcome!

100 sats \ 6 replies \ @WeAreAllSatoshi 8h

Also, I noticed a brief 500 when loading SN earlier this morning. I assume it was during this deployment?

582 sats \ 4 replies \ @k00b OP 8h

Yep, we expected a backwards incompatible rolling deployment (db gets migrated, but client doesn't know yet), but this migration was also non-atomic (spread across two migrations) and the second one failed unexpectedly requiring manual intervention.

I woke up at 5a this morning and ek and I were in a video call anticipating something like this. By far, this is the most complicated migration we've done to date. We migrated 'polymorphic' relations (ie a hack with triggers for fast polymorphic joins) and encrypted columns, nearly doubling the number of tables we store wallet related stuff in.

150 sats \ 1 reply \ @Scoresby 6h

5am...migrated polymorphic relations...backwards incompatible rolling deployment...failed unexpectedly

this is what I imagine my nightmares would be like if I was a developer.

152 sats \ 0 replies \ @k00b OP 6h

This was a nightmare. When these migrations fail, you have no idea how long it might take to resolve. Even with tons of QA, we experienced a bunch of problems.

Modeling data for long term storage and millisecond access is hard. Getting the design wrong, like we did with wallets v1, is very expensive.