Oddbean new post about | logout
 We have to reduce the byte size of zaps. Some zaps are just too big and are several KB of data (without the user even providing a comment) which causes problems.
zap space is limited!  
 Private zaps?  
 I've seen zap requests with maaaany relays (which could be considered an attack vector) 
and I think some private zaps are also rather big - but I honestly don't know the spec there. 
we currently have a size limit on metadata and saw some zaps failing because of that.  
 The relay list in the zap event comes from the client that does the zapping, right? 
 Yes. But it's not just the relay list, the `pzap` (encrypted zap content afaik) is rather big, also for short zap comments (maybe because of the padding?)

https://sourcegraph.com/github.com/vitorpamplona/amethyst/-/blob/quartz/src/main/java/com/vitorpamplona/quartz/events/LnZapRequestEvent.kt?L192 
 That’s not part of the spec afaik 
 Yeah, also couldn't find any specs. Seems to work similar to NIP-04 DMs though... 
 Yeah, that list comes from the inbox relays the user is using. Amethyst for instance just adds them all. So if a user has 20+ inbox relays (which should be only 3), all 20 get into the list. 

This is a general problem of poor relay management since many of those relay are offline or are paid and the user is not even paying for it.  
 seems to me like you need to add compression because relay lists on zaps can easily be compressed massively this way, there is only like 800-1200 or something relays, and about 30 of them most frequent 
 Let’s see 👀 
 You are breaking Alby: 
nostr:nevent1qqs8lwes70xltmqnz7qg7wq5uew5e8ny0s9zh3x9fz44atyw5ekrdqsppemhxue69uhkummn9ekx7mp0qgsrxra3gv0lnkxz2pcxh0xuq9k4f9dr7azwq3aypqtnay4w0mjzmtqrqsqqqqqp3w9nel