@TonyGiorgio
stacking since: #70380
10 sats \ 0 replies \ @TonyGiorgio 30 Apr \ parent \ on: SN's wallet plans meta
It can be very ecash like in UX but with the ability to withdraw. I hope to see a fedimint integration at some point. There's a lot of complicated things going on here instead of just asking users to write down 12 words for a federated ecash balance. SN doesn't even need to run a mint, just let users select their own from bitcoinmints.com
Don't let perfect be the enemy of good. Sybils are great and all, but you'll find that this already works pretty well.
Be very careful with this. Study the LNProxy source code and understand why they make the decisions they make. Also understand that this may result in more force closes from the payer side. It's easy to lose money on this if you're not careful.
One thing you don't have control over is what CLTV is being set on the receiver invoice. If you don't have a direct route to every wallet, which you might be able to do easily enough, you're also going to get into fee and timeout trouble.
You mention zeus somewhere else, a hodl invoice to a hodl invoice just sounds like a disaster.
You're going through all of this "fee credit" work, might as well make fee credits a requirement throughout this site. It sounds like as a non-custodial receipient, I'm still going to be acquiring "fee credits" from non-wallet users, and I'm effectively unable to do a single thing with those besides upvote with them. Perhaps just treat fee credits as a requirement to participate in the site at all, make it required gas in order to get credit for zaps to other people.
2nd point
You're recreating the wheel here a lot. If you look at what's been done with nwc.dev, you can effectively just create two invoices, one to the recipient's wallet and one to you. Send them to the wallet via NWC and have them both be paid by the sender. You can use lnurl verify to ensure they are paid, and if both of them are not, then don't show the upzap at all. Granted, there's not a lot of wallets that support NWC yet.
All of this is going to be difficult, sucks to see you have to do this. I would rather just deposit sats from my wallet and occasionally use this site for the few dollars worth of sats that are involved for most people. Though without the ability to withdraw those, it starts to make this site less worth it for me. Nostr has already figured this out, you're just in the difficult position that you have to monetize through the use of zap volume. The other nostr clients aren't doing this.
100 sats \ 2 replies \ @TonyGiorgio 28 Apr \ parent \ on: The Dilema of Mutiny Wallet with Fedimint lightning
Settings -> emergency toolkit -> save state
Then setup your server and do the import state option.
It's in your browsers storage, that's where the local backup comes from. It's also remotely stored as well, encrypted.
But when you're self hosting, it's your storage now. So it needs to fill it with your data which is what the state file is for.
Holy shit you literally are brain dead.
Straight from GitHub, from the same link you shared, a guide to do exactly what we have always said you can do.
This is the last time I communicate with you. Go get a life, and some education.
100 sats \ 10 replies \ @TonyGiorgio 28 Apr \ parent \ on: The Dilema of Mutiny Wallet with Fedimint lightning
That serves the client side frontend code. God you're fucking retarded.
Quit lying you stupid fuck.
- You still have seed words and storage stored locally on the device
- The app store apps still exist
- The apps are still available on GitHub
- It's on the start9 app store
- The source code still exists
- It's still self custody at the end of the day
You can sit there and continue lying, not knowing what the fuck you're talking about, or you can go do something productive for society.
I won't hold my breath on the latter.
You just opened up the issue over the weekend and we need time to investigate. The sats are likely not gone. There's no reason to be freaking out about it.
44 sats \ 1 reply \ @TonyGiorgio 12 Apr \ parent \ on: There is no such thing as a dust UTXO bitcoin
Actually yeah, I think it's still possible out of band.
10 sats \ 3 replies \ @TonyGiorgio 12 Apr \ parent \ on: There is no such thing as a dust UTXO bitcoin
Yes
Amazing, that's great to know. We just built something blind token based too at Mutiny, will be writing about it more this week.
Lightning can be very private from the sending perspective, less on the receiving side, though we're working on that too, slowly but surely.
Will throw up a burner account and play with Kagi more. Thank you for doing this and answering these questions!
Good to know, though the concern is that we have to trust that. Would prefer tech that we could verify searches wouldn't be linked together. Less concerned about it being stored, more concerned that it's being linked together tied to a specific individual.
This is amazing, thank you for what you do and for doing this as well. Lightning payments for this is a perfect use case and really appreciate the fact that you accept it.
I think the main reason I haven't used Kagi yet is because I'm turned off by tying all of my searches to the same account. Have you thought about pay-per-api call with Lightning? Or doing something with blind authentication tokens to pay for X number of requests upfront and you can't tie any of the requests back together to the source of payment?
There's a lot of things I believe Kagi gets right, but I'm concerned about the privacy by using a single account. I know I can throw away every month, but I don't know how often I would do that on top of all the other manual hassle I do every month for privacy.