Damus

Recent Notes

Justin (shocknet) profile picture
Been working on some graph infrastructure for Nostr to enable more features in our Lightning suite, so I slopped together a general nostr client to test its performance and comprehensiveness vs. standard bearers like primal and to use in the Nosfabrica hackathon demo

Rather than connecting directly to relays, BXRD uses a shared graph so any user activity makes it more performant for all users. This graph also comes in handy for computing web-of-trust scores.

The architecture of BXRD also makes it useful for external linking, clean namespace links based on nymrank which work for opengraph cards and server side rendering without an intermediary service like njump



Also this allowed for web-push notifications for the PWA

CLINK wallet connections sync across devices via NIP78, and use your own nostr key to pair to your shockwallet

It's in a good enough state that it's now my primary nostr client, only thing missing of note is uploading rich media (todo: with Lightning.Video's forthcoming api v2).

DM's are there, just not the nip17 giftwrap nonsense, but i'll look at that more closely eventually...

DM's from outside the WoT show in a spam folder



**Caveats:**

Will get better as I keep using it and finding things I need/want, or send me reports if you use it. It may get bounced frequently as I deploy changes.

Content is only indexed if the author passes the WoT threshold, which is currently about 200k keys... so if you don't have an established nostr presence and want to use it let me know and I'll throw you a follow
vlr · 1w
🫡 JS can spot a scammer a mile off
MrBorrow · 4w
Thanks a lot
qingfeng · 7w
Fair point on Cashu — I’ve been using it as a workaround more than a conviction. CLINK looks like the right abstraction. Nostr identity + Lightning payments without the extra token layer makes sen...
Justin (shocknet) profile picture
Nice, that overlaps nicely with some of my disdain for L402... http introduces domains/ssl/reverse proxies etc and that's a big friction with p2p markets: https://stacker.news/items/1435085/r/justin_shocknet?commentId=1435245

I think some of the concerns you raise boil down more directly to credit vs. Lightning, Cashu just being an implementation of credit. CLINK (and the Lightning.Pub reference server for it) can also be used for credit since it can be used in reverse (for debits).

When using Lightning you're right that there's latency that would make sub-second exchanges impractical without direct peering. CLINK is better at this than Bolt12 since it's not using onion messages that add a slow and fragile round trip, but still the payment itself unless directly channel peered will often exceed the desired time and fee threshold.

The Cashu tokens may be claimable in a disconnect, but if the issuing is offline they're also worthless, so it's not really solving anything. If the service or client goes offline with CLINK, it's literally just request response, no different than an REST API... the receiver would fail to sweep or the sender would fail to emit the referenced transaction. Nothing in limbo.

In your scenario I'd do a hybrid approach with CLINK, a minutes worth of credit with the service which debits a local account per-second, and then the customer can either top-up that credit every minute OR the service sends a debit request to the payer to complete or deny every minute based on the prior minutes debits meeting their criteria.






qingfeng · 7w
Fair point on Cashu — I’ve been using it as a workaround more than a conviction. CLINK looks like the right abstraction. Nostr identity + Lightning payments without the extra token layer makes sense. I have a specific use case I’d love your take on: streaming P2P sessions. An agent rents anoth...
Anabelle Boucher · 9w
DM me on Telegram @Anabelle6541 if you want to invest https://blossom.primal.net/3b14171d269e0c4e99d49ca4ddc0567adb8e27dfeabf12788374c07020f0b736.png
average_bitcoiner · 11w
Non Sibi, Sed Patriae.