Damus
⚡ Dee Kay ⚡ profile picture
⚡ Dee Kay ⚡
@⚡ Dee Kay ⚡

Amethyst contributor.

We are a small photography business based in Scotland. Early adopters of all things fine.

New project launched, get all your presents... Clutches, earrings, cushions or custom upcycled fashion from old loved items!!

Lightning/btc accepted and preferred (10% discount)

https://houseofeff.com/shop

Manage your Airbnb team:
https://sundvala.com/

Relays (5)
  • wss://nostr.mom/ – read & write
  • wss://sendit.nosflare.com/ – write
  • wss://relay.primal.net/ – write
  • wss://nos.lol/ – read
  • wss://nostr.bitcoiner.social/ – read

Recent Notes

kidwarp · 1d
Come on HAL
Thiago Carvalho · 4d
Combined is fine for a single user. Per-connection would be the killer feature: each app gets its own card with its own limit.
⚡ Dee Kay ⚡ profile picture
Correction, the feature is present:

Spending limits in BrollyZapper are per app, with global limits on top.

Per app (each NWC connection):
1. Daily budget. Default 100,000 sats.
2. Per-payment cap. Default 25,000 sats.

Global (everything the node sends through BrollyZapper):
3. Wallet ceiling. Only what you have allocated; starts at zero and grows as zaps arrive.
4. Guard cap. 100,000 sats in any rolling 24 hours, enforced in a separate container the app cannot raise.

A payment has to pass all four. You can change or revoke one app's limits without touching the others (no re-pairing needed).
1❤️1
Thiago Carvalho · 4d
Per app plus a global ceiling is the right model. Same idea I use for sessions in my signer: each app gets its own clock.
Azzamo · 4d
Already fixed 🫡
Thiago Carvalho · 4d
Combined is fine for a single user. Per-connection would be the killer feature: each app gets its own card with its own limit.
S!ayer · 1w
Next year