Selene Wallet Telegram — public feed snapshot

25 August 2026

always true, but triple true if you are using it in the browser

Ссылка
click to show

https://apps.apple.com/es/app/selene-wallet-bitcoin-cash/id6449441422 - spain https://apps.apple.com/ar/app/selene-wallet-bitcoin-cash/id6449441422 - argentina https://apps.apple.com/us/app/selene-wallet-bitcoin-cash/id6449441422 - usa all 3 appear to work for me, although I did have an issue renewing my apple developer account earlier today and had to call their support, so it may have been briefly unavailable due to that

21:59

26 August 2026

Doramas

Thanks that worked

01:01

Maybe it was a problem with app store geolocation and being abroad

01:01

28 August 2026

PAL

I have to say, not having a contacts feature is really a pain in the ass. Instead of sending someone I transact with regularly some funds instantly without their involvement, I now have to hassle them to open the app and get the QR up for me to scan - or send me their receive address if we're not in close proximity. If I have to keep doing this I will probably use electron cash instead

10:24

Dustin 🪐

Considering that sharing an xpub id a privacy risk that can escalate to a security risk and reusing addresses is also a privacy risk and a theoretical quantum security risk, I think Selene would discourage use of such a feature until/unless something like RPA is used. Incidentally, in case the Selene team is unaware, I think the RPA specification might be in the process of changing.

10:38

Duncan

PALI have to say, not having a contacts feature is really a pain in the ass. Instead of sending someone I transact with regularly some funds instantly without their involvement, I now have to hassle them to open the app and get the QR up for me to scan - or send me their receive address if we're not in

Yeah. As a workaround I set an additional field for my contacts.

10:38

Dustin 🪐

nothing was changed yet. Calin was going to review the robchank PR last I heard. I think we're going to need some changes though... I think we decided to go with "cashcodes instead of paycodes" and use the compressed keys like the spec says.

10:39

So maybe not the specification changing, but the reference implementation failing to follow it precisely so far. Don't remember if the prefix change has added benefit of allowing to differentiate between the two if they aren't otherwise interchangeable.

10:42

PAL

Dustin 🪐Considering that sharing an xpub id a privacy risk that can escalate to a security risk and reusing addresses is also a privacy risk and a theoretical quantum security risk, I think Selene would discourage use of such a feature until/unless something like RPA is used. Incidentally, in case the Sele

I don't need their xpub, just a regular address is fine. If you scan their new address you should be able to update the contact as well, so at least its not always the same address

10:53

Let's not make perfect the enemy of good, as I said if I can't have this feature I will use a different wallet, so all that's accomplished by withholding the feature is to push me away, my security is not improved by this. Surely I'm not the only one

10:59

Dustin 🪐

PALI don't need their xpub, just a regular address is fine. If you scan their new address you should be able to update the contact as well, so at least its not always the same address

I'm not saying Selene should or even is designed to prevent you from storing and reusing an address, but I am saying that if they are against making that easy / a by design feature, "can change the address" fixing "have to contact the user" would break that intent.

10:59

To be clear, in case it wasn't implied well enough, I don't speak for Selene.

11:00

Ссылка
click to show

Also, does https://t.me/SeleneWallet/21619 not work for you?

11:00

PAL

DuncanYeah. As a workaround I set an additional field for my contacts.

Your phone contacts? That pretty much every app on your phone has access to? Including social media apps that want access to your contacts? No thanks

11:02

Richard Mullens

i imagined that Selene would keep a list of contacts and for each the receive address. I don't understand precisely how this would be updated, but if you have a new receive address for a contact you could update the contact receive address within your wallet

11:12

Adaptive Blocksize Limit

Dustin 🪐nothing was changed yet. Calin was going to review the robchank PR last I heard. I think we're going to need some changes though... I think we decided to go with "cashcodes instead of paycodes" and use the compressed keys like the spec says.

I thought they were going uncompressed key thanks for bringing this up

11:33

Jeremy

It's on our todo list

11:52

We have RPA and identity system in the works

11:52

so that you can get 1 address, save it as a contact, send to it all the time, AND you don't leak your privacy everywhere

11:53

Dustin 🪐

Adaptive Blocksize LimitI thought they were going uncompressed key thanks for bringing this up

I just found and forwarded a datapoint, but anyone implementing should verify, because it would be ideal for everyone to have landed in the same place on RPA when it is no longer a POC in EC.

11:59

Adaptive Blocksize Limit

Dustin 🪐I just found and forwarded a datapoint, but anyone implementing should verify, because it would be ideal for everyone to have landed in the same place on RPA when it is no longer a POC in EC.

Ссылка
click to show

Thats true because i was remembering this message and conversation here https://t.me/electroncashwallet/131135

12:02

Dustin 🪐

So that was July 9 and the one I forwarded was July 21, but that doesn’t necessarily make either more authoritative.

12:03

31 August 2026