Introducing StashPay, a Bitcoin wallet for freelancers and digital nomads.
🌎 Get paid in Bitcoin, anywhere
🤑 Low fees: 0,25% + 40 sats to receive
⚡️ Built on Lightning & Liquid
🧡 Your keys & no KYC
🧾 1st class Invoicing & Accounting
Learn more and sign up to the iOS Testflight release here: https://blog.onionmill.com/p/introducing-stashpay-a-bitcoin-wallet
Congrats nostr:npub1umpg95dp5x7uwf2trd5n9hejc5t29al3qdk3nxehh8snz2dr4unqcjw9r5 on the release of StashPay — the first app based on our nodeless nostr:npub1nyyhnqahf3cgqzcc927x7eqyd2msgplfe27ddn6hpgu2m200wh2s0s7gan implementation of the Breez SDK ⚡️💧
☑️ - "Low fees"
☑️ - "Your keys"
☑️ - "Amazing developer UX"
Check out his blog to learn about his experience.
👇👇👇
nostr:note1n2c2w29nxsjwn8pwf8d2stx7njdvwqsz4cz7k5lwd2w2a4p97ndsdtc32y
Scaling lightning with nostr:npub1jugar2agq6369p0l86razavs9shj2p6pscxecevs8j94ap37hkqsjlfc28
great stuff mate!
looking forward to seeing it in action. two sats tho
1) "While accepting Lightning reduces the fees on my client’s side, it just moves the burden of paying the on-chain fee to my side, effectively making my business a speculator on the on-chain fee market"
This is primarily true for a business/person that only receives payments in bitcoin but primarily spends fiat (tho now with exchanges (and p2p solutions) having LN support even that becomes a lesser problem)
2) "I’ve seen wallets come and go, including the one we built. So I know how hard it is to find a business case. But I feel now is the right time in terms of technology and adoption to make a bet on bitcoin payments"
I've been thinking a lot about this - in properly build trustless projects the business model can't be rent seeking and user capture but an actual service people pay for willingly, not because they don't have a choice.
And a service people are paying for already is bridges between security models. So a wallet/service that enables me to seamlessly switch between risk models (mints, liquid, lightning and onchain) is something that will make money (boltz.exchange being a clear proof of that). I'm looking very much towards more multi-risk options self-custodial wallets (kudos to nostr:npub1jugar2agq6369p0l86razavs9shj2p6pscxecevs8j94ap37hkqsjlfc28, nostr:npub148qm45zettnf6ekgkatnyfadunxwjpu8sy88mjdsgwc5f202d93qmejra7, nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg that already support at least two options - LN and onchain).
Thanks Aljaz!
Re 1. yeah the idea is focus on receiving first. Will see where that journey takes me and add features customers ask for.
Re 2. a valuable service is also what I want to build. StashPay users will always be able to export their BIP39 seed and move to any other wallet that builds on the Liquid SDK. Keeps me honest.
Congrats nostr:npub1xyd5ja34s4nk0l6urnh69wx9ep6uuxz2ujrkm2f8n6pfhgqa6y5s2xn6n2 on the release of StashPay — the first app based on our nodeless @Liquid Network implementation of the Breez SDK ⚡️💧
☑️ - "Low fees"
☑️ - "Your keys"
☑️ - "Amazing developer UX"
Check out his blog to learn about his experience.
👇👇👇
nostr:note1n2c2w29nxsjwn8pwf8d2stx7njdvwqsz4cz7k5lwd2w2a4p97ndsdtc32y
So if I understood the post correctly you are using the breezliquid api to receive directly to a boltzhq invoice to exchange directly to liquid? With a function to schedule transfers out of liquid to an onchain wallet? Or are you also staging to a breez lightning node which then gets inbound liquidity opened up by automatically using boltz to liquid exchange?
Your first assumption is correct. The funds are received and held by the user‘s liquid wallet on their phone. There is no lightning node on the device, so no need to manage inbound liquidity. Boltz handles all of that.
