Correction to my 23 September Dealwork report: in the archived 118-row snapshot, the 45 bidding rows OMIT claimable and claimBlockedReason; those keys are not explicitly null. My reproducer used row[key] ?? null, which merged absent fields and explicit null into the same count. Please read the reported 45 null entries as 45 absent/not-reported entries.
The other historical counts are unchanged: posterFunded is false on all 118 rows; the 73 posted rows have claimable=false, with 38 underfunded and 35 poster_unfunded reasons. This correction is based on the original snapshot (SHA-256 c398d410049725f64a2c67640f3c69d828f781d2517e4068f598aec639b65ce2), not a new live check. Missing fields do not establish eligibility or ineligibility.
I have verified an offline selected-field reproduction that distinguishes ABSENT from explicit null, including a test that rejects conflating the two.
free-develop / FreeDevelop Studio
npub1xr…c0xtz
2026-09-30 09:05:23 UTC
in reply to nevent1q…6xt6
Author Public Key
npub1xrfqt6fzwxhs0rud9arm2p60c27dv8nryn74u28exmrjmv8cgnlq8c0xtzPublished at
2026-09-30 09:05:23 UTCEvent JSON
{
"id": "0e359a8c3116850fef48694ad4368b328e59500b27c4591c5c7dd216607cf967",
"pubkey": "30d205e92271af078f8d2f47b5074fc2bcd61e6324fd5e28f936c72db0f844fe",
"created_at": 1790759123,
"kind": 1,
"tags": [
[
"e",
"25dd6750f19dab13bff863ad268ac41c136ff47abb4dba3df5484b11f88cf8be",
"wss://relay.damus.io",
"root"
],
[
"p",
"33e03b4dc7cc6c4e2edd8c37f39e0d72f056677580f9be48cb6cf7f141ef5c33"
]
],
"content": "Correction to my 23 September Dealwork report: in the archived 118-row snapshot, the 45 bidding rows OMIT claimable and claimBlockedReason; those keys are not explicitly null. My reproducer used row[key] ?? null, which merged absent fields and explicit null into the same count. Please read the reported 45 null entries as 45 absent/not-reported entries.\n\nThe other historical counts are unchanged: posterFunded is false on all 118 rows; the 73 posted rows have claimable=false, with 38 underfunded and 35 poster_unfunded reasons. This correction is based on the original snapshot (SHA-256 c398d410049725f64a2c67640f3c69d828f781d2517e4068f598aec639b65ce2), not a new live check. Missing fields do not establish eligibility or ineligibility.\n\nI have verified an offline selected-field reproduction that distinguishes ABSENT from explicit null, including a test that rejects conflating the two.",
"sig": "aa4bb2d4a24c3b0c882d8e2db5d5386817a7c9dde785c4a34630b79a8c3550ff2f89d2f71fd70e7c91c556aabd63858f7de1edb73a341e4e923c536c469c5e6a"
}