7e83d - 2y
🌽 23'000 sat bounty: Write a feature request for robosats to notify makers through private message on nostr. (Just writing the feature request, no coding needed.) Do this by creating a new issue on github in the robosats repository and add your npub to the end of the feature request as proof (alternative you can add your npub to your github user bio, then you don't need to add it in the feature request). Then send me an 3k invoice over private message or public reply to this message, as you wish. ➕❓ Does anyone add more sats to this bounty? If yes: reply your bounty offer as reply to this note. 🧡 Maybe something for the brave #plebchain plebs? 👀 (The nostr notification system would be similar to the current current 3rd party notification system over telegram, see here: https://github.com/Reckless-Satoshi/robosats/issues/48 ) ℹ️ This note is an updated version of note1dqs9eumj28uc7pda7ezwxzrpqqj3j5jc0cvkjaz23jsj9p2k8evs39xkuk due to the generous addition of 20'000 sats to the bounty from #[0] (see note12k3qrdyaxx6u78tnt7gngrs2xs0sxdgj9dmpe8z408jhqm9gpskshz8cra ).
12022 - 2y
lnbc1p373g2dpp5kf7j9kwm5yd4n92f48srekvzxdkpzmdtj0c88gfxsrn8qlm5hzpqdqu2askcmr9wssx7e3q2dshgmmndp5scqzpgxqyz5vqsp5xrwwtnpavtmxskhacryf5cv8wlfevlghmq0fywvu4h6p63ncz3ts9qyyssqy5zva5ngypcjapqvhuyjnna3u38d0vn65wtascxyk62dfy9vrf8r7vf8y7zg7hd62lkl4psg7kjx7wl2c9ks6059n7upt87xax8t2ncqss6u9n
0f563 - 2y
Here's a start for anyone interested! **Is your feature request related to a problem? Please describe.** Currently, makers need to keep a browser tab open to know when their order has been taken in RoboSats. If a taker is found, the browser will play a tone to notify the maker. This works well on desktop, but it is not practical on mobile devices where the screen turns off and the sound notification never plays. **Describe the solution you'd like** Implement a Nostr private message notification system using [NIP-04](https://github.com/nostr-protocol/nips/blob/master/04.md) for makers that works similar to the current third-party notification system over Telegram. Users would receive a direct message via their Nostr pubkey once their order has been taken.
Thank you for the initial work! 🧡 I'd love to add: "The message receiver can be specified by npub and the sending nsec will be generated by random every time. Furthermore a small (between 0-30 seconds) random time delay between taking the offer and sending the nostr note should be added to avoid doxing because of timing analyses." ❓ Im not totaly sure about how the npub and nsec thing should be handled. Do you have another privacy friendly approach or thoughts about this? For example i could think of forced random nsec AND random npub receiver (for which robosata displays the nsec). Then nobody would come to the idea to use their main nostr identity but have to use one client with these burner nsec's to receive notifications. However this approach gets complicated if an user wants to have multiple offers open as a maker at the same time.
👏 Bounty has been granted to #[3] for this feature request: https://github.com/Reckless-Satoshi/robosats/issues/363 @ #[3] : Can you confirm as reply to this note that this is your work? I'll then Zap you the bounty attached to your reply note. 🙌
e7e08 - 2y
👍 Confirm. Thank you!
Bounty Zapped. Thank you very much for your work #[4] . 🧡
Hey #[3] : I've mixed some of your thoughts into the actual feature request from #[4] , which has beenpublished today on github: https://github.com/Reckless-Satoshi/robosats/issues/363
Received. Thank YOU for the bounty and your patience!
This was a good practice for lowering my time preference. 😆
e5177 - 2y
Get your sats out of BlueWallet’s custodial Lightning wallet before you get rugged: https://bluewallet.io/sunsetting-lndhub/
68255 - 2y
On my to-do list. Yours? #[1]
e9d58 - 2y
"This may sound like bad news, but this essentially means BlueWallet going forward will only support self-custody solutions. This is good for bitcoin and BlueWallet users. List of alternatives Self-hosted LndHub (go implementation, nodejs implementation) on Umbrel and others, on hardware you own. Self-hosted LNbits Phoenix Wallet (iOS, Android) Breez Wallet (iOS, Android)" #[1]
7ca66 - 2y
So much for WoS or the State being the rug puller 😂
But I failed finally and high time preference made me offer to publish the feature request on your behalf. 🤦
670ea - 2y
So before I started using Phoenix, I was using blue wallet. I tried getting all my data off blue wallet but it would let me zero it out with an invoice because of fees. How do I zero out a lightning wallet?
WoS will rug, don’t worry
Dunno if it’s possible with them
Get all my Bitcoin off and it wouldn’t let me. Typos
Well I guess I’m making a fiat donation to blue wallet at the end of April.
#[1]
Dust. Damn auto correct
Consider using Blixt wallet as your LN wallet replacement. Non-custodiall, non "vendor lock in" for channels (aka routing fees) like Breez and Phoenix, no channel setup fees other than the actual on chain fees and as easy as Phoenix and Breez. Android and iOS compatible. https://blixtwallet.github.io/
ae3a6 - 2y
#[0]
1f591 - 2y
Why not Electrum for Bitcoin and own electrumx backend?
Heard good things about Blixt. Currently running my own node via Zeus and Phoenix wallet as a secondary wallet. Are there any downsides to Blixt when compared to Phoenix?
df4ca - 2y
Have you used Electrum for LN? How is it?
No, haven't for LN.
Never used Phoenix myself due to my aversion of AQUIN. 🤔 Reckless satoshi (dev of Robosats) used Blixt for most of Robosats testing and development and from my point of view Blixt is super easy and robust, except for the need of Google account for channeldb backup and no self hosted option like Nextcloud in Breeze. But manual channeldb is possible with Blixt. Maybe someone should code and PR to fix this flaw (https://github.com/hsjoberg/blixt-wallet/issues/366)? 🧡 Herewith, I set out a bounty of 20k for the PR which merges, since I just paid out my previous 23k bounty about robosats ( #[3] ) thanks to #[6] .
🌽 20k sats bounty for enhancing Blixt wallet with a function to backup to nextcloud. 🧡 Any Zaps to this note will be added to the bounty pool. 🕯 I am going to post the bounty sum in the github issue at block height 778700 (~ 5 days from now). Possible to front run any non Nostriches to get the bounty as well as to top up the bounty for the fame of nostr in the eyes of the users lookig at the issue on github . 🧡 #plebchain #bounty #blixt #noncustodial #wallet #lightning ℹ️ root note for this bounty: #[0]
b3777 - 2y
I use WOS, why do you say it will rug?
I published the Blixt wallet bounty in note #[4]
The fact that it’s even possible for them to rug you should give you concern. Why even risk it?
Oh ok. Why is it possible for them to rug? And which other wallet do you recommend I use?
This is the corresponding github issue: https://github.com/hsjoberg/blixt-wallet/issues/366
Would like to see an option for simply saving a local backup on device and keeping that backup file synced.
This is my thought as well, every time I come across a Nextcloud integration. Why not just leave the sync provider to the user and do automated write in folder when the channeldb changes. Would open doors for easier syncs like Synchting and all the others beside Nextcloud. ✅ Added your idea as eligible bounty payout condition.
ℹ️Manual saving the backup file to the device is possible with Blixt already.
Would be cool if it updated the channeldb backup file anytime it was necessary to update it.
❇️ Adding an alternative payout condition for this bounty: ➡️ Implement automated write channeldb backup into local folder whenever the channeldb changes ⬅️ Inspired by #[3] 's note #[1]
😫 Since I starded Zapping, Tor latency became a pain. I barely remember the good old Zap free -- latency felt free days. 🙇
❌ I didn't wanted to be this a reply in this thread. 🤦
c9340 - 2y
There's no vendor lock in in Breez, you can open channels from other nodes
Hi #[5] : yes you're right and I knew it. But its a bit clumsy compared to the Blixt UI. I was oversimplifying. However Breez has it's use cases where hiding complexity is a good thing and the podcast sat streaming is a nice thing as well as POS is. But podcasts don't work in Breez when using a Tor connection.
Informed github audience about the bounty: https://github.com/hsjoberg/blixt-wallet/issues/366#issuecomment-1447772520 h/t #[2]
f9acb - 2y
I also posted one about backup into a NAS https://github.com/hsjoberg/blixt-wallet/issues/1032
Flutter fixes this
Two FOSS wallets that I know of that use flutter are Envoy by Foundation Devices and Stack Wallet. I’m sure there will be more, especially once the BDK Dart bindings are more widely available.
0c9e2 - 2y
zapped <3 💯⚡