Avatar
Justin (shocknet)
3316e3696de74d39959127b9d842df57bddc5d1c7af8a04f1bc7aed80b445088
Head of building shit | Lightning.Pub | ShockWallet.app | Lightning.Video/thecto

It's a less secure version of ShockWallet's UX that uses Nostr to sync state and device tokens... and it doesn't use flakey ecash

Replying to Avatar PABLOF7z

unified balance where my money is saved on relays

this is a "nostr balance" that will follow me around on any nostr app

and I just zapped nostr:npub1vwymuey3u7mf860ndrkw3r7dz30s0srg6tqmhtjzg7umtm6rn5eq2qzugd without having to connect nostr-wallet-connect

it just works, no QR codes, no secrets, nothing... your nsec gives you access to your money

Totally back-asswards way of doing this, if ECash mints want to copy ShockWallet and Lightning Pub do it correctly with remote signing and device tokens

By not being an extension, it's a software remote signer, management dashboard, and widget any developer can embed

Yea this will just help have them not get compromised in the first place, there's no graceful way to recover from that... Gotta repoint everyone

Apps will be able to paste in a widget so no browser extensions needed, allowing for an enterprise class UX and management tools

Pleased to announce we'll be giving Pub demo's and can help you set up a Lightning node to share with friends, families and customers, easily over Nostr.

Come see us at @TheBitcoinConf Makerspace next month!

DNS can't rug your lightning.pub

ShockWallet.app and lightning.pub been doing this awhile, without shitcoins

Nope, some sister cos and I'm friendly with the founders, but I'm not part of this in any way

I'd probably accept new methods PR in the kind 21000 proto, but if they want to waste their time on shitcoins they may as well waste it on NWC

Small brain thinking

There are ~300 undecillion ip6 addresses, each is a peer we need to scale to obviously

Nostr is the b2b settlement layer for notes

Scaling will be done through custodial enote mints

This rationale highlights my issues with it

Custody of small amounts (credit) is inevitable in an economic sense, but ECash isn't additive to that at all, while ECashers position them as synonymous despite solving the wrong problems inhibiting broader adoption of Bitcoin as a MoE

It's not more programmable than any other database, it's actually much worse because of the the abstraction from the underlying asset

The privacy benefits are farcical, particularly in the context of small nodes, and treating it as a new payment spec is deleterious to interoperability

If the goal is to have shared friends and family nodes for Bitcoin as a MoE, then Lightning.Pub is superior to mints in every way