I have sent and received ZAPs working now with amount + comment, etc. not shown above.
The issue is validating ZAPs is very non-deterministic. Lots of failure points - non-spec, DNS, changed lud06, receiver old metadata event, etc.
Skip validation and it’s far less brittle.. and I think that’s what people are doing today in client apps.
Is anyone else validating ZAPs? What’s your experience?
I also have identity proof of work aggregation based on the sum of all their events batch processing. Maybe 50% done.
I think I only had 350 pow. Was less than I expected. That’s without trying and 100% random. From maybe 2,200 events.
Event pow aggregation is a step deeper. Sum of all pow for an event and it’s replies. More intensive to calculate, but fairly ok if stream processing against existing values.
Maybe a black hole. Maybe a useful way to identify value and/or low value content.
