Makes total sense. Thank you. So in Haven's case this likely isn't the problem, as in, the Outbox relay only ever accepted events signed by me, and as far as I can tell, it accepts all events signed by me, including replaceable events (unless I consume all my "tokens", then it starts rate limiting). So I'm still at loss about what's triggering the 10002 event write "loop".

How does Amethyst check if my Outbox relay latest 10002 event is up to date? (Can you roughly point me to this code in Amethyst?)

Reply to this note

Please Login to reply.

Discussion

ohhh I just logged into your relay and it sent ALL the past versions of your own 10002 events. There are 44 10002 events coming down to Amethyst just for yourself. For each one of the 43 outdated events, Amethyst replies with the new one.

nostr:nprofile1qqsw9n8heusyq0el9f99tveg7r0rhcu9tznatuekxt764m78ymqu36cpz4mhxue69uhhyetvv9ujuat50phjummwv5hszymhwden5te0wahhgtn4w3ux7tn0dejj7qg4waehxw309an8yetwwvh82arcduhx7mn99uuwx66a something is wrong with haven's replaceable code. A filter by kind 10002 should only return the latest event, not all versions.

You can test it here: https://lightningk0ala.github.io/nostr-wtf/query

with filter: [{"kinds": [10002]}]

Yep I saw this too, I will have a fix for it this week. Ty gentz

Nevermind I see it on desktop but not phone

Check the notes I’ve tagged you in over the past few days. If you want to reproduce the problem yourself, just add a relay to your Inbox/Outbox list using Amethyst, save it, and sign the new 10002 event. Repeat this a few times and either use Vitor’s filter above or my "Citrine fix" script. Both will return more than one kind 10002 event.

Also, it seems Haven is accepting but silently ignoring Kind 5 Deletion Requests, so my script doesn’t fix the issue. Deleting the Outbox database and reimporting notes from well-behaved relays does fix the problem.

Delete is fixed now on the inbox relay

Fiatjaf still working on kind 10002