pull down to refresh

Hey there!
Long time lurker, making my first post here!
I share something I have been working on for myself but that might be of interest to somebody.
I made a selfhosted webapp wallet that leverages the Strike API (via the strike api key you can generate at dashboard.strike.me ) and Tor, to keep you anonymous.
Strike provides no-kyc accounts for some latin american countries, so you can just be creative and create an account in one of those countries and protect your privacy while using one of the most robust lightning wallet out there 😇
For kyc users, the webapp still prevents strike to get your private info, not only your ip address, but also anything leaked through the strike app trackers.
Sure, not your keys, not your coins. But for small amounts I find it to be a useful backup solution. Be smart and use our own node as your primary wallet!
A few screenshots of the UI:
The app work both for onchain and lightning. It is very light and fast and easy to install through docker, you can follow the guide here:
NOTE: This is a repost, as I mistyped the repository in the original post 😁
is there a way to get a strike.me username with this method or that's more proprietary? i must have answered my own question ...
reply
0 sats \ 1 reply \ @Signal312 6h
Could you clarify a bit - specifically how does using Strike with Robosats work for you? You say "when payment fails"...do you mean you're buying btc, and your invoice, that you submitted to robosats, has failed?
If you're buying btc, and your lightning invoice fails repeated, that can be a huge hassle.
However, using boltz.exchange works really well to get the funds directly into btc. You submit a lightning invoice from robosats to boltz.exchange, and it just works. Every single time, no delay, no resubmitting.
reply
Yeah, boltz is a great option, and I do that from time to time! However prefer lightning network, especially for smaller amounts.
And I mainly sell there for bigger amounts, so Boltz would not be an option.
reply
What is the goal with making this ? Why would I use this so called "anonymous" Strike instead of multiple other LN wallets that could do a better job?
reply
Let me set this straight: People should use non-custodial wallets whenever possible. Phoenix, ZEUS... or even better their own nodes.
However at times they are not reliable and/or require knowledge and management (opening channels, rebalancing, syncing), so a back up solution such as this one might be a good idea, depending on everyone trade offs.
The reason I built this are two:
  1. when I use Robosats, payments frequent fails. So I used this as a temporary backup method: when payment fails, I get funds through my webapp and then forward them to my CLN node.
  2. when I am outside, I prefer not to connect to my home node for security reasons.
I registered to strike no-kyc via tor, and only ever connected to their api via tor limiting the exposure of my information.
That being said, if non-custodial solution always work flawlessly, people should NOT use this project or any non-custodial wallet.
Also, in my own opinion, NO-KYC custodial solutions should not be demonized when they are used correctly and with limited amounts.
reply
now this is interesting, one cud send sats from a kyc'ed Strike account to a decoy non-kyc'ed Strike wallet, that looks like a legit Strike user, and then send them off to wherever.
neat exercise in privacy and sats flow.
reply
0 sats \ 1 reply \ @DarthCoin 7h
ah ok so you want to use it only with the bitcoin part, just as a decoy wallet, using strike node liquidity and then just move the sats to your custody. Yeah that make sense.
reply
Yeah, correct. Only as a decoy bitcoin wallet 👍
reply
This is definitely of interest to people! Thank you!
reply
0 sats \ 1 reply \ @OT 10h
Pretty cool!
Care to share which Latin American countries don't require KYC?
reply
One of them is Brazil, but there are a few
reply