SN release: postpone non-custodial switch, encrypted device sync, blink receives \ stacker news ~meta

pull down to refresh

The November 5th non-custodial switch is postponed. We knew it would rain in October, but it ended up pouring and we missed the deadline. The switch will still happen, guaranteed. We'll give a two week warning once the changes are done this time around. Those of you that got ready in advance are set, but everyone else will have a bit more time.

encrypted device sync

In your settings, you can enabled encrypted device sync which will allow us to sync changes to your sending wallet credentials between devices. Enabling device sync requires each device input the same mnemonic passphrase and can be shared between devices via QR code scanning.

Once enabled and you leave the device sync page, it's impossible for SN to show you this passphrase again (we store the passphrase in browser storage that we cannot read from). If you lose the passphrase, you can reset device sync and start again, but it'd be best to store the passphrase somewhere secure.

For now, device sync only synchronizes wallet sending credentials between your devices, but in the future it will also be used for other types of secure storage like encrypted messaging keys, ecash notes, nostr keys, etc.

Most of the device sync technical design and code was written by @rblb who has been helping us out for the last month or so.

blink receives

You can attach Blink for receives now (via @rblb)

other stuff

There are a bunch of little bug fixes and other stuff here and there in this release, but not much worth mentioning.

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 13m sats to 31 contributors for 138 contributions! View an up to date list of contribution awards here: https://github.com/stackernews/stacker.news/blob/master/awards.csv

Previous release: #721818

We are hiring.

view all related items

234 sats \ 1 reply \ @Aardvark 4 Nov

I'm still happy I attached my wallet regardless if it needed to be done now or later.

This site has really helped me become a lot more familiar with LN, so it's a win for me either way.

31 sats \ 0 replies \ @nym 4 Nov

Same here

147 sats \ 0 replies \ @supratic 5 Nov

In case you missed it:

136 sats \ 0 replies \ @WeAreAllSatoshi 4 Nov

Encrypted device sync is awesome!

79 sats \ 0 replies \ @TheMorningStar 4 Nov

Thanks for the postpone notice. I'm glad I can still use SN wallet. It's best and hassle free.

56 sats \ 0 replies \ @grayruby 4 Nov

And here I rushed to get the @NFLsurvivor2024 account set up with an attached wallet today. Haha.

Oh well. Saves me the trouble of doing it in a couple weeks.

36 sats \ 14 replies \ @Satosora 4 Nov

Encrypt data sounds good, but how many people are going to forget their passphrase?

152 sats \ 3 replies \ @DarthCoin 4 Nov

0 sats \ 0 replies \ @random_ 5 Nov

Very mystical. Magic words even.

0 sats \ 1 reply \ @Satosora 4 Nov

Darth, we have all been on that boat before. 10 years later you find you paper wallet you used as a bookmark.

197 sats \ 0 replies \ @DarthCoin 4 Nov

but yes, encrypted device sync is a cool feature

20 sats \ 9 replies \ @k00b OP 4 Nov

A good number.

How many people want us to be able to steal/breach their money and read their private messages?

20 sats \ 5 replies \ @k00b OP 4 Nov

Also if you lose the passphrase, but one device is still connected, you can reset device sync on that device without data loss.

15 sats \ 1 reply \ @SimpleStacker 4 Nov

Any reason we can't choose our own passphrase?

25 sats \ 0 replies \ @k00b OP 4 Nov

You're more likely to choose a weak one than not. I can create an issue if you want to produce the passphrase or entropy yourself.

15 sats \ 2 replies \ @Satosora 4 Nov

Okay, thats not too bad then. Most people have at least two devices on, right?

20 sats \ 1 reply \ @k00b OP 4 Nov

I'd guess on average multi-device people have a desktop/laptop and a phone. Many people just use one device though I'd guess.

0 sats \ 0 replies \ @Satosora 4 Nov

This should encourage some to use two. Just in case the unimaginable happens.

0 sats \ 2 replies \ @Satosora 4 Nov

I know, everyone wants the privacy until they cant figure out why its not working. I just think it will be a headache on your end.

21 sats \ 1 reply \ @k00b OP 4 Nov

I'd rather have many small headaches that aren't my fault but we work really hard to prevent than a bullet to the brain.

0 sats \ 0 replies \ @Satosora 4 Nov

Right, less that can fall back on you is good.

19 sats \ 0 replies \ @DEADBEEF 5 Nov

I’m glad I already attached my wallet it relieved a lot of anxiety I didn’t even know I had about the impending switch.

18 sats \ 7 replies \ @SimpleStacker 4 Nov

Does it matter which device I enable device sync from? I'm currently on a device that doesn't have credentials for my attached wallet.

5 sats \ 6 replies \ @k00b OP 4 Nov

It won't matter if you start with Device A (that doesn't have credentials), but you'll need to input the passphrase in Device B (the one that does have credentials) for them to sync to Device A.

0 sats \ 5 replies \ @SimpleStacker 5 Nov

hmm, I synced my phone and my home computer which is connected to my wallet. But when I try to zap from my phone i still get the QR code

300 sats \ 0 replies \ @k00b OP 5 Nov

It looks like there's a bug where you have to refresh the browser for the sync'd creds to show up.

I'll fix that today.

0 sats \ 3 replies \ @k00b OP 5 Nov

If you go to your attached wallet on your phone, are the credentials sync'd?

Which wallet attachment are you using?

237 sats \ 2 replies \ @SimpleStacker 5 Nov

Alby with NWC

fwiw, I saw the receiving credentials in the attached wallet configuration page on my phone, but the sending credentials were blank.

I also refreshed my browser and same thing

Edit: NVM it's working now after another refresh

21 sats \ 1 reply \ @k00b OP 5 Nov

So sorry. I should've caught that before shipping.

114 sats \ 0 replies \ @SimpleStacker 5 Nov

no need to apologize, it's impossible to catch everything all the time

15 sats \ 0 replies \ @flat24 5 Nov

I'm ready and prepared, I attached my Coinos wallet and it works perfectly, I still get SATS in the SN wallet, but also to my attached wallet... keep working guys @k00b "It will be ready, when it's ready" 👍

20 sats \ 0 replies \ @IamSINGLE 5 Nov

The suspense continues! I'm in for the switch.

0 sats \ 0 replies \ @random_ 5 Nov

Never switch never. MTL4LYFE

Thank you for the postponement.

0 sats \ 0 replies \ @Msd0457890 4 Nov

I am new to Bitcoin and arriving here has brought me into a sea of knowledge. Adding a Litening wallet has helped me become more familiar with the great world of Bitcoin.

0 sats \ 3 replies \ @0xbitcoiner 4 Nov

For someone who only uses one device, what's the benefit of enabling "encrypted device sync"?

33 sats \ 2 replies \ @k00b OP 4 Nov

Your wallet sending credentials are only ever in plaintext in browser memory. They’re much harder to steal.

0 sats \ 1 reply \ @0xbitcoiner 4 Nov

For those using WebLN and LN address, this is not the case, is it?

33 sats \ 0 replies \ @k00b OP 4 Nov

Oh yeah if you're only using WebLN for sending, nothing is stored by us and, for now at least, device sync is no use to you.

0 sats \ 0 replies \ @0xbitcoiner 4 Nov

deleted by author

we are postponing the non-custodial switch

encrypted device sync

blink receives

other stuff