That's nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg headed out for a team meeting.
Some say we never left that team meeting.
That's correct. Wait a few days.
Soon ™️
We have a few quirks to sort through next week, but who would like to test out a new LSP soon? Would require closing existing channels and changing LSP settings.
PSA: In case you missed it, Bitcoin Atlantis is shutting down their fedimint.
If you have funds there, open mutiny or fedi and transfer your funds to a different mint or wallet.
We're a lightning wallet primarily. If someone adds a fedimint and isn't using a node or on chain wallet, they should expect the funds to go to the fedimint.
If you don't want funds in a fedimint, don't add one.
Mutiny+ gives access to the TestFlight for beta testing, as well as lightning addresses, we'll be working on more features soon. You don't lose anything if you stop paying.
Their wallet isn't something that is intended to work with ours via NWC.
Release time! 🚀
In 1.7.0, we've made a number of performance improvements, bug fixes, and new features, but here's the ones we're excited about the most:
- On chain fedimint support
- Transfer funds between federations
- Node operates in a web worker now, the UI should be quicker
If you have a federation added, all on chain deposits to Mutiny will go into there.
We have full send and receive support now, so this effectively gives you a unified balance with fedimint, allowing you to send or receive via onchain & lightning.
The Bitcoin Atlantis federation is shutting down at the end of the month. We now parse all of the metadata for federations and will display pop up warnings like this.
Included in this release is the ability to transfer funds from one federation to another to make this seamless.
Lastly, we've moved all the core logic into a Web Worker. That means the UI thread doesn't have to fight with Mutiny for resources. This should make most wallet operations faster, and keep the UI responsive at all times. It's a big change, so if you see any problems let us know!
Please reply with any #bitcoin companies you know that are already on #Nostr besides the ones tagged here.
I’m working on a list. I’m mainly interested in companies that already have an established brand presence elsewhere, so let’s avoid shilling personal projects or Nostr clients please. 🙏
#AskNostr
nostr:npub1key55ax33gkl50uqemvl4khrtqrhzm7wzpc7fhseutt5ddkcwcrqgxlt3h
nostr:npub1s0vtkgej33n7ec4d7ycxmwt78up8hpfa30d0yfksrshq7t82mchqynpq6j
nostr:npub1spralxq6jlw5rdy0249vqr5sh43rfrlx2wzv3rhjjqedw559w9psrs8s72
nostr:npub1cashappn03s3cl2ljsdntv0v28e2um5lgx4vjctqjt23pcwzjhsqmtdg5l
nostr:npub155m2k8ml8sqn8w4dhh689vdv0t2twa8dgvkpnzfggxf4wfughjsq2cdcvg
nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5
nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg
nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm
nostr:npub1jg552aulj07skd6e7y2hu0vl5g8nl5jvfw8jhn6jpjk0vjd0waksvl6n8n
nostr:npub1wu4aye7ll0lnrrg638e90sehzsgpzx5t39t3mwl05aa0d0ap08esdz3vw0
nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl
nostr:npub1ve8qwrlztemdmnh62jffcr0y9m9dpqgqjdg8ufx7gc3qw5wdk74qyv9ka6
nostr:npub1earna05hx6ax38r33h3atmecjzdu547m8suw87w70aw6mlyga4hsqcja5j
Hey nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg
Getting this screen in the iOS mobile app for the past 24 hours. App worked fine last week, and I haven’t changed anything I’m aware of. How best to proceed?
Cc nostr:npub1t0nyg64g5vwprva52wlcmt7fkdr07v5dr7s35raq9g0xgc0k4xcsedjgqv nostr:npub1u8lnhlw5usp3t9vmpz60ejpyt649z33hu82wc2hpv6m5xdqmuxhs46turz 
Please file an issue on our github.
A great write up about LDK challenges and why they moved to Breez. All of these we also ran into and solved:
1. Custom rust library around LDK
1. Rapid Gossip Sync bugs and slow syncing
2. Unreliable routing algorithm
3. Concurrent device access w/ just seed word backup
If you would like advice building on LDK or would like to use our MIT libraries to assist in the development of your wallet, please reach out.
We're a small team of 3 people but happy to help in any way we can.
Resync chain in the admin settings if you need to.
Looks like nostr:npub148qm45zettnf6ekgkatnyfadunxwjpu8sy88mjdsgwc5f202d93qmejra7 is pulling out of the US. If you're sick of jumping through hoops due to the whims of the tyrants in your government, check this one out.
Here's how to avoid app stores entirely and use the nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg PWA in 5 minutes flat, including migrating your funds. LFG.
So if I sent onchain funds to nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg and it cleared while the wallet was closed, is it gone?
No
nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg
Ok all the doom loops, failed payments, and weird glitches that I have been experiencing have all gone away after I removed the Atlantis federation. I have added other federations and it seems fine. A weird glitch or something wrong with that federation I don’t know. Reporting for bug reports.
An issue on our GitHub with logs would help. We haven't been able to track this down or reproduce.
Double check that the channel shows as online. The LSP has been under a lot of load.
Looks like you had a pending payment for multiple days and didn't come back online to settle the payment. Had to close.
One source of confusion is the unified QR code when a federation is added. Right now on chain activity still comes from the normal on chain wallet.
The next major version of Mutiny will allow deposits/withdraws into a federation via onchain, effectively giving a unified balance.
