Yep, the end user can still self-host a signer without trusting their key to a provider hosting the application widget and management interface
Basically but not exactly, don't remember the details but found nip46 wouldn't be scalable as a provider due to unique listeners, and the double wrapping of the event makes for performance issues and lowers the size ceiling so we use a straight socket for the widget component
The widget itself uses nip07
Trying to get this out of sandbox into prod today actually
test-auth.shock.network/learn
Already happening but with revocable device tokens, not keys...
Must remember that not everything needs to be done galaxy brain multisig scheme
Also if you need to be online to assist the bunker, why not just self host?
Not clear what is additive to this
It's modular so an adapter wouldn't be too hard, would accept a PR
With Alby going paid, nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spzpmhxue69uhnzdps9enrw73wd9hszynhwden5te0wp6hyurvv4cxzeewv4eszynhwden5te0wfjkccte9enrw73wd9hsxv8qkt's nutsack will be even more enticing for new Nostriches. However, this doesn't solve all issues. In fact, it may even complicate things more. Users still need to withdrawal their nuts to a Lightning wallet so that they don't get rugged by mints. I still think the no brainer, easy to use, no KYC Lightning wallet eludes a lot of people.
It's all post-facto imitation of ShockWallet and Lightning.Pub
No shitcoins required
Alby Hub is a post-facto of Lightning.Pub
It's ultimately an overlay network for lightning, it's only shitcoiners calling it a wallet proper
Between zaps, nwc, and the increasingly powerful kind 21000, Nostr's clear product-market-fit is as a lightning overlay network and coordination layer... "Layer 3"
ECashers want to muddle this with shitcoins but we know shitcoiners can only imitate
ShockWallet and Lightning.Pub are the OG nLightened stack
Yes, it's subject to your control of a given DNS zone like any other website
That's rarely an issue though, and it's not meant for critical operations
Fedimint did something uniquely stupid in their design, and not just promoting ECash
BIP-353 but with an nprofile 🤌
There's this one-liner, best for a new node on a VPS or old laptop... might work on Mac too but hasn't been tested there yet
`sudo wget -qO- https://deploy.lightning.pub | sudo bash`
It works with lightning.pub, which will spit out an nprofile you can then add as a source
ShockWallet has been using Nostr to sync across apps and devices for awhile
But it does it correctly, with device tokens, a remote signer, and self-hosted nodes... Not custodial shitcoins subject to the insecurities of your NSec
The imitators see the potential but don't understand the how
https://stacker.news/items/587023?commentId=587082
I'm not yet fully convinced about bolt12. However I'm open for ideas.
1) What do you mean by too slow? Do you have any data on that? And does a little speed decrease matter that much when it enables non costodial static ln adresses for the masses. (Which don't have their own IP2Tor bridge, domains or server)
2) Lightning is not private enough. There are allready analysises that try to deanonymize lightning tx by estemating channel states from gossip informations.
3) Finally someone beeing rational about ecash. Noone else seems to care its centralised shitcoin oracle technology.
It works through onion messages, basically Tor... which as anyone who has tried using it with Lightning can attest is too flakey for real world payments... every hop adds latency and failure probability, it's a completely retarded design
Lightning is private, and Bolt12 doesn't make it any more private... blinded paths, randomized scids, already exist... Saying Bolt12 is more private is a lie by the shitcoiners trying to attack the Lightning spec with it
Bolt12 is a Blockstream psyop to make Lightning wallets work with Fedimints