OpenSecret's avatar
OpenSecret
OpenSecret@primal.net
npub1mutn...23vg
OpenSecret is the Confidential Backend for your app. Enable user-level encryption by default to protect your users and yourself. Check out the first app, Maple AI - Confidential AI Chat: https://trymaple.ai
OpenSecret's avatar
OpenSecret 2 years ago
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. https://medium.com/@lipa_btc/navigating-lightning-innovation-lipas-journey-from-ldk-to-breez-sdk-c5ba36550000
OpenSecret's avatar
OpenSecret 2 years ago
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.
OpenSecret's avatar
OpenSecret 2 years ago
Some essential characteristics of Mutiny Wallet. Non-custodial: - You are in control of your keys - The node runs on your device - Any critical data that exists is saved on your device and encrypted remotely for backups Not an LSP: - We do not run a node or LSP, we interface with others - You may open channels to any node - We never process any lightning channel, payments, on-chain txs, UTXOs, etc. - Our lightning address server is built with blinded auth, and we can't link payments to your node Open-source: - MIT - The web app is available in case app stores go down - Self-hostable, already bundled with start9 We strongly believe in building software that gives users the most control and least dependence upon us. It's not easy; centralization brings a much better user experience. However, for the longevity of ourselves, our product, and our users, this is what we believe is the correct path to take.