This is not what I am thinking. Problem with these is that they can be redeemed at the mint and then passed to another person without him knowing. Maybe the token should be put inside in some way so that you should destroy the note in order to redeem it. The use case that I am thinking is the normal use case of paper (physical paper) money, like passing them to another person. And on top of that whatever is technically possible as enhancement, like ability to check if this note is backed by real bitcoin and possibly redeeming it (by destroying the note as I said).

Obviously. While I haven't written so explicitly, it is clear from my post. I am asking specifically about the technical implementation.

I think this post is not for the bitcoin territory.

That made me think... cracked screen is a quite common thing. People use their phones with cracked screens. Maybe this is an actual issue.

Once upon a time it seemed silly to me that people will actually use the screen to type and not physical buttons. To me it is still extremely inconvenient to this day (fat fingers). Nevertheless, the touch screen is so versatile that its versatility trumps this (to me major) inconvenience. In the same way the camera has became a versatile input device. It is used not only for its originally intended purpose (taking pictures), but also to transfer information.

As for the NFC... there are actually wallets that support NFC. Zeus supports it (I haven't tested it but I would guess it works).

QR codes in my opinion are more efficient. NFC requires the devices almost touch each other, QR codes work from a distance.

Just a note: their fedimint (freedom one) has problem paying lightning invoices in the moment. Maybe for some reason there is no longer suitable lightning gateway...

Yeah, but preimage verification is not there. I tried doing it manually by using online tools for invoice encoding and h265 hashing, but i failed. I think i failed because the preimage is displayed in hex, but the online tool interprets it as a string...

Well, ecash ballance does get restored (tested by me). And all I've read is that ecash is stored locally.

I don't get something. Since Mutiny supports eCash and eCash notes are supposedly stored on your device (or maybe the mutiny server), how are they recovered by the passphrase? If they are on the server, then running your own server won't recover these.

I got that. I just explained why I had no way of knowing about your warnings.

Do you think the default mutiny servers are compromised?

I haven't seen your warnings. I am on stacker.news since 2 weeks ago.

Nevertheless, do you think the Mutiny servers are compromised at the moment? Do you think this may cause the "incorrect password" issue?

I was wandering do block explorers like mempool.space visualize chain splits?

OK, small update. I did try sending larger amount outward. And after that I did succeed receiving via this channel. So... success i guess?

I have read these. I don't want to mess with LSP before experiencing "normal" lightning channels. I don't exactly currently understand reserves. The channel displays 4152 local and 4152 remote reserve. As far as I understand these should cover eventual channel close? I also don't understand how the sum of liquidity and reserves don't make the channel capacity.

I will maybe try to send more sats outbound tomorrow and see if this will allow me to receive sats.

BTW do you people realize how unusable this is for non tech people that want to spend their time in some other way than learning why they can't transact? And even if you manage to abstract everything go explain to someone new that he has to pay money to receive money. I think that's why eCash, that people here love to hate, is and will gain more and more traction (And I still don't know why transactions in mutiny out of the fedimint cost 1%, but that's a different topic).

I will... But i don't have enough money to open multiple channels. So for now I am testing Zeus. Later I will maybe try other wallets.

Thanks, but this is not the problem for me, as i already said i was able to send sats (impossible with the channel partner offline).

Unfortunately I still CANNOT receive sats with channel to another node. The following are true:

Either I am missing something, or Zeus doesn't work correctly (who knows, maybe it can only work with wrapped invoices or something).

I will investigate (or not) later depending on my mood.

I will interact as a person testing and playing around. I don't have any bitcoin economy around me.