Oddbean new post about | logout
 This is also after the latest update, too.  
 So nostr:nprofile1qqst4qyeqenw7zm0fwjsty68h6cnys5jre2xd8ngqpjv5a2j26s78fspzemhxue69uhhyetvv9ujucm0d9hx7uewd9hj75a0pev is working fine. I'm just going to use that until it gets figured out. I've tried all kinds of stuff with notifications, background use, etc.  
 I can't send sats to coinos... 😅  
 Still? Where were you sending from? 
 A minibits mint. 

It's not an issue with coinos. 🤷‍♂️ 
 nostr:nprofile1qqsqdzwltpr635ehdzfd52tz947qlhq77x2c7j7yguwep9n258k2nusprdmhxue69uhhw6r9v96zu6rpwpc8jarpwejhym3wvdhj7qgmwaehxw309a6xsetxdaex2um59ehx7um5wgcjucm0d5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme04jvaud, if you are sending eCash, you need to send it from the same Mint, if you do not have one for Coinos "mint.coinos.io", you cant send eCash to Coinos, untill they add automated swap between mints on receiving. Minibits neither has it, but, since it supports other mints, it will create the mint of the origin for you. If you send using the Lighting Network it should work fine. Zapping should be working fine. 

Unless..

I noticed that when you register with coinos it creates a new nsec/npub, thus, you need to import your nsec in settings->security to use coinos as your zapping, once that is done, your zapping should work. *Coinos, please consider explaining that, the registry should ask the user to import the nsec and give an option to use Amber or an extension, currently is not easy to figure it out, shot out to espn@coinos.io, who help me with it.

nostr:nprofile1qqst4qyeqenw7zm0fwjsty68h6cnys5jre2xd8ngqpjv5a2j26s78fspzemhxue69uhhyetvv9ujucm0d9hx7uewd9hj75a0pev, I set my NIP05 using coinos.io but it shows an error, your profile too, is this a known issue?

https://image.nostr.build/82c7dad16b05a1ee3b769220d28d9f4170ca768a34659c3cc4e2deb566ca9871.jpg 
 I was attempting to send as lightning, not ecash.  
 yeah, that should not be failing, tested Minibits for weeks, improving by the day, the dev team is incredibly busy building this tool, had one issue here and there, but nothing serious

One thing I noticed is that if the app is not online it will not receive any sats via LN payments, and therefore the sending will fail... That makes it difficult to use for sats, #Coinos excels in that arena, hence my choice ATM, #Coinos, IMO, only fails in missing support for signing with a Nostr signer like Amber, eCash, on chain BTC, LN, PIN, 2FA... if they get a mobile app, IMO, they will be right now one of the top wallets 
 I can't get anything out of minibits at the moment other than small zaps where I have to try 3-5 times to get it to go through. That's not super convenient.  
 Do you see any further wallet error details in transactions?

Lightning node settles every day quite a lot of transactions close to the defined mint limit of 1mio sats without issues. 
 Sent DM with info after updating to latest app version.  
 Thank you for kind words! Receiving lightning payments does not depend on the wallet state (online or offline) as they are received by the mint's lightning node.

Mint then issues ecash of the same amount that is claimed by the wallet once it becomes online.

There are some optimizations on how often the wallet tries to claim waiting ecash from the mint, but you should get push notification immediately if your device supports them and you can any time force the claim by restarting. 
 Tested heavily and no dice. Mobile off or not online my payments to that account would not go through, perhaps I have missed something but that was my experience a month ago and with two different mobiles.

I saw you guys just made a theme update that looks amazing  plus some changes that should improve the wallet functionality, will test it again, really liked what you guys are building and you are clearly working hard on that wallet, additionally, you are very responsive and present here in Nostr, that is very much appreciated, you guys rock! 
 Get the yesterday's over the air update. There was a bugfix for a recent regression bug that prevented to claim sats coming to lightning address unless wallet restarted. It is now fixed and wallet tries to claim on start, on coming to foreground and then every 60 seconds when actively in use.