{
 "number": 36586,
 "input_hash": "9fb255253dbf478d",
 "model": "ledger",
 "prompt_hash": null,
 "created": "2026-11-02T01:11:51+00:00",
 "result": {
  "summary": "Checks available disk space before starting background chainstate compaction and defers compaction with a warning if free space is less than the assumed chainstate size. Skips periodic compaction entirely for in-memory databases, and moves compaction start and finish logging to the info level by default for both forced and automatic compactions.",
  "problem": "Full LevelDB compaction can temporarily require nearly double the database's disk space before obsolete SST files are removed. On nodes running with tight disk margins, background compaction can exhaust disk space, causing node crashes or hangs on shutdown (as reported in #36585). Furthermore, automatic compaction start and finish messages were hidden under `-debug=coindb`.",
  "card": "Prevents background chainstate compaction from exhausting disk space by checking available filesystem space against the assumed chainstate size before starting, deferring it with a warning if space is insufficient. It also skips compaction for in-memory databases and logs compaction start and finish events at info level by default. In issue #36585 on v32.0rc3, background compaction filled the filesystem and hung the node during shutdown.",
  "evidence": [
   "Linked issue #36585: 'Background chainstate compaction (#35465) filled the disk; node then hung after shutdown (v32.0rc3)'"
  ],
  "scope_notes": "",
  "changed_since_previous": "Added a check to skip periodic compaction for in-memory chainstates, and added release notes.",
  "thread": {
   "last_event_at": "2026-11-01T18:49:09Z",
   "events": 30,
   "head_sha": "2fcfa1dae75ccd11062a6e6073600e67eb20164c",
   "schema_floor": 2,
   "schema": 2
  },
  "waiting_on": [
   {
    "at": "2026-11-01",
    "id": "rc:4436896379",
    "on": "author",
    "url": "https://github.com/bitcoin/bitcoin/pull/36586#discussion_r4436896379",
    "what": "respond to andrewtoth's pushback on warning when skipping compaction"
   }
  ],
  "risk": {
   "level": "low",
   "touches": [
    "validation"
   ],
   "why": "An incorrect disk-space check could defer compaction indefinitely or fail to prevent compaction from running on a full disk."
  },
  "discussion": {
   "author_status": "last statement processed 2026-11-01",
   "open_concerns": [
    "andrewtoth: Do not log a warning when skipping compaction, because running with less than 2x chainstate disk space should be supported and users should not receive warnings for something they cannot act on",
    "andrewtoth: Do not include a release note for this change"
   ],
   "resolved_concerns": [
    "andrewtoth: Skip compaction if there is not enough free disk space rather than only warning and continuing (fixed by l0rinc 2026-10-21)",
    "stickies-v: Whether the worst case temporary duplication occurs when a sparse level L-1 causes all files to compact dense level L in one go (answered by l0rinc 2026-10-22)",
    "stickies-v: Call CompactRange on slices instead of the entire range in one go (answered by l0rinc 2026-10-22)",
    "optout21: Log the currently observed available space in addition to the warning (fixed by l0rinc 2026-10-23)",
    "optout21: Add explanatory and call-to-action info describing that uncompacted DB takes up more disk space and that the user should free up space (fixed by l0rinc 2026-10-23)",
    "optout21: Change wording from 'Skipping' to 'Deferring' to suggest that it is not without consequences (fixed by l0rinc 2026-10-23)",
    "stickies-v: Why CheckDiskSpace() is not being used here (fixed by l0rinc 2026-10-23)",
    "stickies-v: Skip compaction entirely for in-memory databases (fixed by l0rinc 2026-10-23)",
    "stickies-v: Clarify release note phrasing around temporary disk usage during compaction (fixed by l0rinc 2026-10-23)",
    "andrewtoth: Strike the phrase 'obsolete data' from the release notes because users will not understand it (answered by l0rinc 2026-11-01)"
   ]
  },
  "reviewability": {
   "state": "Ready",
   "label": "Ready",
   "reason": "Nothing known that would invalidate a review now."
  },
  "agreement": {
   "state": "Disputed",
   "summary": "Disputed: objection that needs a change, the objector pushed back after a reply (andrewtoth)",
   "reason": "l0rinc replied to andrewtoth regarding release note wording and defended logging a warning when skipping compaction, but andrewtoth pushed back on the warning objection.",
   "evidence": [
    "andrewtoth (objection, interface, must be changed, contested): Do not log a warning when skipping compaction, because running with less than 2x chainstate disk space should be supported and users should not receive warnings for something they cannot act on",
    "andrewtoth (suggestion, scope, must be answered, open): Do not include a release note for this change",
    "sedited: Concept ACK",
    "stickies-v: Concept ACK",
    "optout21: Concept ACK",
    "stickies-v: ACK",
    "optout21: ACK",
    "stickies-v: ACK"
   ],
   "objections": [
    {
     "reviewer": "andrewtoth",
     "association": "MEMBER",
     "type": "suggestion",
     "kind": "approach",
     "harm": "",
     "request": "Skip compaction if there is not enough free disk space rather than only warning and continuing",
     "question": "",
     "text": "Skip compaction if there is not enough free disk space rather than only warning and continuing",
     "clears_with": "answer",
     "blocking": false,
     "status": "fixed",
     "status_note": "author pushed an update skipping compaction as suggested",
     "cleared": true,
     "author_replied": true,
     "others_replied": false,
     "fix_pushed": true,
     "replies": [
      "c:6309885819"
     ],
     "evidence": "2026-10-20: 'Would it make more sense to just skip compaction if we don't think there's enough free disk space to do it?'",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#issuecomment-6303711894",
     "id": "c:6303711894",
     "at": "2026-10-20",
     "status_at": "2026-10-21",
     "status_by": "l0rinc",
     "resolution_evidence": "2026-10-21: l0rinc: 'updated as suggested'",
     "pin": null,
     "from_schema": 2
    },
    {
     "reviewer": "stickies-v",
     "association": "MEMBER",
     "type": "question",
     "kind": "approach",
     "harm": "",
     "request": "",
     "question": "Whether the worst case temporary duplication occurs when a sparse level L-1 causes all files to compact dense level L in one go",
     "text": "Whether the worst case temporary duplication occurs when a sparse level L-1 causes all files to compact dense level L in one go",
     "clears_with": "answer",
     "blocking": false,
     "status": "answered",
     "status_note": "author acknowledged investigating partial compaction",
     "cleared": true,
     "author_replied": true,
     "others_replied": false,
     "fix_pushed": false,
     "replies": [
      "rc:4347320990"
     ],
     "evidence": "2026-10-21: 'My understanding of the worst case here is that this happens when all the data is on a single level L, with a very sparse (<32MiB) level L-1 above it. Because L-1 is so sparse, all L-1 files (with key'",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#discussion_r4339626383",
     "id": "rc:4339626383",
     "at": "2026-10-21",
     "status_at": "2026-10-22",
     "status_by": "l0rinc",
     "resolution_evidence": "2026-10-22: l0rinc: 'Thanks for the hint, we should investigate that'",
     "pin": null,
     "from_schema": 2
    },
    {
     "reviewer": "stickies-v",
     "association": "MEMBER",
     "type": "suggestion",
     "kind": "approach",
     "harm": "",
     "request": "Call CompactRange on slices instead of the entire range in one go",
     "question": "",
     "text": "Call CompactRange on slices instead of the entire range in one go",
     "clears_with": "answer",
     "blocking": false,
     "status": "answered",
     "status_note": "author tested compacting smaller ranges and found it could still produce large spikes and is too complex for this PR",
     "cleared": true,
     "author_replied": true,
     "others_replied": false,
     "fix_pushed": false,
     "replies": [
      "rc:4347320990"
     ],
     "evidence": "2026-10-21: 'perhaps an alternative approach could be to call `CompactRange` on slices, instead of on the entire (`nullptr`, `nullptr`) range in one go?'",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#discussion_r4339626383",
     "id": "rc:4339626383#2",
     "at": "2026-10-21",
     "status_at": "2026-10-22",
     "status_by": "l0rinc",
     "resolution_evidence": "2026-10-22: l0rinc: 'I tried compacting smaller key ranges locally, which reduced peak disk usage in some cases but could still produce large'",
     "pin": null,
     "from_schema": 2
    },
    {
     "reviewer": "optout21",
     "association": "CONTRIBUTOR",
     "type": "suggestion",
     "kind": "interface",
     "harm": "",
     "request": "Log the currently observed available space in addition to the warning",
     "question": "",
     "text": "Log the currently observed available space in addition to the warning",
     "clears_with": "answer",
     "blocking": false,
     "status": "fixed",
     "status_note": "author pushed an update including observed available space",
     "cleared": true,
     "author_replied": true,
     "others_replied": false,
     "fix_pushed": true,
     "replies": [
      "rc:4364107414",
      "c:6374496215"
     ],
     "evidence": "2026-10-22: 'Additionally logging here the currently observed available space is marginally helpful (guideline: if a log is a result of a decision based on several values, log each).'",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#discussion_r4347675764",
     "id": "rc:4347675764",
     "at": "2026-10-22",
     "status_at": "2026-10-23",
     "status_by": "l0rinc",
     "resolution_evidence": "2026-10-23: l0rinc: 'Done, thanks'",
     "pin": null,
     "from_schema": 2
    },
    {
     "reviewer": "optout21",
     "association": "CONTRIBUTOR",
     "type": "suggestion",
     "kind": "interface",
     "harm": "",
     "request": "Add explanatory and call-to-action info describing that uncompacted DB takes up more disk space and that the user should free up space",
     "question": "",
     "text": "Add explanatory and call-to-action info describing that uncompacted DB takes up more disk space and that the user should free up space",
     "clears_with": "answer",
     "blocking": false,
     "status": "fixed",
     "status_note": "author pushed an update including recovery guidance in warning",
     "cleared": true,
     "author_replied": true,
     "others_replied": false,
     "fix_pushed": true,
     "replies": [
      "rc:4364107987",
      "c:6374496215"
     ],
     "evidence": "2026-10-22: 'Could we add some more explanatory and call-to-action info here? Describing that the uncompacted DB takes up more disk space, and that the user should free up some disk space.'",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#discussion_r4347717041",
     "id": "rc:4347717041",
     "at": "2026-10-22",
     "status_at": "2026-10-23",
     "status_by": "l0rinc",
     "resolution_evidence": "2026-10-23: l0rinc: 'Done'",
     "pin": null,
     "from_schema": 2
    },
    {
     "reviewer": "optout21",
     "association": "CONTRIBUTOR",
     "type": "suggestion",
     "kind": "interface",
     "harm": "",
     "request": "Change wording from 'Skipping' to 'Deferring' to suggest that it is not without consequences",
     "question": "",
     "text": "Change wording from 'Skipping' to 'Deferring' to suggest that it is not without consequences",
     "clears_with": "answer",
     "blocking": false,
     "status": "fixed",
     "status_note": "author updated warning and replied done",
     "cleared": true,
     "author_replied": true,
     "others_replied": false,
     "fix_pushed": true,
     "replies": [
      "rc:4364107987",
      "c:6374496215"
     ],
     "evidence": "2026-10-22: 'Also, I suggest changing the wording \"Skipping\" to \"Deferring\", to suggest that it's not without consequences.'",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#discussion_r4347717041",
     "id": "rc:4347717041#2",
     "at": "2026-10-22",
     "status_at": "2026-10-23",
     "status_by": "l0rinc",
     "resolution_evidence": "2026-10-23: l0rinc: 'Done'",
     "pin": null,
     "from_schema": 2
    },
    {
     "reviewer": "stickies-v",
     "association": "MEMBER",
     "type": "question",
     "kind": "maintenance",
     "harm": "",
     "request": "",
     "question": "Why CheckDiskSpace() is not being used here",
     "text": "Why CheckDiskSpace() is not being used here",
     "clears_with": "answer",
     "blocking": false,
     "status": "fixed",
     "status_note": "author updated to use CheckDiskSpace() with 50 MiB overhead",
     "cleared": true,
     "author_replied": true,
     "others_replied": false,
     "fix_pushed": true,
     "replies": [
      "rc:4364106218",
      "c:6374496215"
     ],
     "evidence": "2026-10-23: 'nit: any reason we're not using `CheckDiskSpace()` here?'",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#discussion_r4357924174",
     "id": "rc:4357924174",
     "at": "2026-10-23",
     "status_at": "2026-10-23",
     "status_by": "l0rinc",
     "resolution_evidence": "2026-10-23: l0rinc: 'Guess the extra 50 MiB reserve is fine here (seemed imprecise to me) - changed.'",
     "pin": null,
     "from_schema": 2
    },
    {
     "reviewer": "stickies-v",
     "association": "MEMBER",
     "type": "suggestion",
     "kind": "approach",
     "harm": "",
     "request": "Skip compaction entirely for in-memory databases",
     "question": "",
     "text": "Skip compaction entirely for in-memory databases",
     "clears_with": "answer",
     "blocking": false,
     "status": "fixed",
     "status_note": "author updated code to skip automatic in-memory compaction",
     "cleared": true,
     "author_replied": true,
     "others_replied": false,
     "fix_pushed": true,
     "replies": [
      "rc:4364109056",
      "c:6374496215"
     ],
     "evidence": "2026-10-23: 'For an in-memory database, the compaction memory usage problem is arguably even worse than the on-disk one? Since memory-only is quite ephemeral in nature, I think it's uncontroversial to just skip co'",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#discussion_r4357973303",
     "id": "rc:4357973303",
     "at": "2026-10-23",
     "status_at": "2026-10-23",
     "status_by": "l0rinc",
     "resolution_evidence": "2026-10-23: l0rinc: 'Sure, I was also wondering if someone would comment on bubbling this check up - thanks, done.'",
     "pin": null,
     "from_schema": 2
    },
    {
     "reviewer": "stickies-v",
     "association": "MEMBER",
     "type": "suggestion",
     "kind": "style",
     "harm": "",
     "request": "Clarify release note phrasing around temporary disk usage during compaction",
     "question": "",
     "text": "Clarify release note phrasing around temporary disk usage during compaction",
     "clears_with": "answer",
     "blocking": false,
     "status": "fixed",
     "status_note": "author clarified release notes",
     "cleared": true,
     "author_replied": true,
     "others_replied": false,
     "fix_pushed": true,
     "replies": [
      "rc:4364109542",
      "c:6374496215"
     ],
     "evidence": "2026-10-23: 'nit: I found the \"may need another database copy\" a bit confusing, and think the rest of the phrasing could be a bit more clear as well.'",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#discussion_r4358044237",
     "id": "rc:4358044237",
     "at": "2026-10-23",
     "status_at": "2026-10-23",
     "status_by": "l0rinc",
     "resolution_evidence": "2026-10-23: l0rinc: 'Did something similar, thanks.'",
     "pin": null,
     "from_schema": 2
    },
    {
     "reviewer": "andrewtoth",
     "association": "MEMBER",
     "type": "objection",
     "kind": "interface",
     "harm": "Do not log a warning when skipping compaction, because running with less than 2x chainstate disk space should be supported and users should not receive warnings for something they cannot act on",
     "request": "",
     "question": "",
     "text": "Do not log a warning when skipping compaction, because running with less than 2x chainstate disk space should be supported and users should not receive warnings for something they cannot act on",
     "clears_with": "change",
     "blocking": true,
     "status": "contested",
     "status_note": "author replied that skipping compaction should only be temporary, but andrewtoth pushed back arguing compaction only saves disk space and low-capacity nodes will get unhelpful repeated warnings",
     "cleared": false,
     "author_replied": true,
     "others_replied": false,
     "fix_pushed": false,
     "replies": [
      "rc:4436676560"
     ],
     "evidence": "2026-10-31: 'I'm not sure we should warn about this. Running on a system with < 2x the chainstate disk space should be supported. If that is the case there is nothing the user can do, and they shouldn't be getting'",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#discussion_r4433066699",
     "id": "rc:4433066699",
     "at": "2026-10-31",
     "status_at": "2026-11-01",
     "status_by": "andrewtoth",
     "resolution_evidence": "2026-11-01: andrewtoth: 'Why not? From my understanding the compactions are just a way to reduce disk usage in the chainstate db, but don't affect node operation otherwise.'",
     "pin": null,
     "from_schema": 2
    },
    {
     "reviewer": "andrewtoth",
     "association": "MEMBER",
     "type": "suggestion",
     "kind": "scope",
     "harm": "",
     "request": "Do not include a release note for this change",
     "question": "",
     "text": "Do not include a release note for this change",
     "clears_with": "answer",
     "blocking": false,
     "status": "open",
     "status_note": "",
     "cleared": false,
     "author_replied": false,
     "others_replied": false,
     "fix_pushed": false,
     "replies": [],
     "evidence": "2026-10-31: 'I don't think this change warrants a release note.'",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#discussion_r4433072777",
     "id": "rc:4433072777",
     "at": "2026-10-31",
     "status_at": null,
     "status_by": null,
     "resolution_evidence": "",
     "pin": null,
     "from_schema": 2
    },
    {
     "reviewer": "andrewtoth",
     "association": "MEMBER",
     "type": "suggestion",
     "kind": "style",
     "harm": "",
     "request": "Strike the phrase 'obsolete data' from the release notes because users will not understand it",
     "question": "",
     "text": "Strike the phrase 'obsolete data' from the release notes because users will not understand it",
     "clears_with": "answer",
     "blocking": false,
     "status": "answered",
     "status_note": "author asked whether users need more than understanding garbage collection needs space",
     "cleared": true,
     "author_replied": true,
     "others_replied": false,
     "fix_pushed": false,
     "replies": [
      "rc:4436679534"
     ],
     "evidence": "2026-10-31: 'at least the last part of this line should be struck.\"obsolete data\" is not something a user reading the release notes will understand.'",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#discussion_r4433072777",
     "id": "rc:4433072777#2",
     "at": "2026-10-31",
     "status_at": "2026-11-01",
     "status_by": "l0rinc",
     "resolution_evidence": "2026-11-01: l0rinc: 'Do they need to understand more than garbage collection needs a bit more space?'",
     "pin": null,
     "from_schema": 2
    }
   ],
   "support": [
    {
     "reviewer": "sedited",
     "reason": "",
     "substantive": false,
     "verdict": "Concept ACK",
     "id": "c:6309945846",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#issuecomment-6309945846",
     "at": "2026-10-21",
     "association": "MEMBER",
     "evidence": "none",
     "areas": []
    },
    {
     "reviewer": "stickies-v",
     "reason": "",
     "substantive": false,
     "verdict": "Concept ACK",
     "id": "c:6319694104",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#issuecomment-6319694104",
     "at": "2026-10-21",
     "association": "MEMBER",
     "evidence": "none",
     "areas": []
    },
    {
     "reviewer": "optout21",
     "reason": "",
     "substantive": false,
     "verdict": "Concept ACK",
     "id": "r:5613334538",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#pullrequestreview-5613334538",
     "at": "2026-10-22",
     "association": "CONTRIBUTOR",
     "evidence": "none",
     "areas": []
    },
    {
     "reviewer": "stickies-v",
     "reason": "",
     "substantive": false,
     "verdict": "ACK",
     "id": "r:5626190512",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#pullrequestreview-5626190512",
     "at": "2026-10-23",
     "association": "MEMBER",
     "evidence": "none",
     "areas": []
    },
    {
     "reviewer": "optout21",
     "reason": "",
     "substantive": false,
     "verdict": "ACK",
     "id": "c:6380160065",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#issuecomment-6380160065",
     "at": "2026-10-24",
     "association": "CONTRIBUTOR",
     "evidence": "none",
     "areas": []
    },
    {
     "reviewer": "stickies-v",
     "reason": "",
     "substantive": false,
     "verdict": "ACK",
     "id": "c:6413372201",
     "url": "https://github.com/bitcoin/bitcoin/pull/36586#issuecomment-6413372201",
     "at": "2026-10-26",
     "association": "MEMBER",
     "evidence": "none",
     "areas": []
    }
   ],
   "participants": [
    {
     "login": "andrewtoth",
     "stance": "objection",
     "note": "objected to warning when skipping compaction on low-disk systems and suggested dropping or rewording the release note",
     "association": "MEMBER",
     "comments": 5,
     "first": "2026-10-20",
     "last": "2026-11-01"
    },
    {
     "login": "sedited",
     "stance": "support",
     "note": "Concept ACK",
     "association": "MEMBER",
     "comments": 1,
     "first": "2026-10-21",
     "last": "2026-10-21"
    },
    {
     "login": "stickies-v",
     "stance": "support",
     "note": "Concept ACK, ACK, re-ACK; asked about LevelDB compaction behavior, suggested compacting by slices, skipping in-memory compaction, and using CheckDiskSpace",
     "association": "MEMBER",
     "comments": 8,
     "first": "2026-10-21",
     "last": "2026-10-26"
    },
    {
     "login": "optout21",
     "stance": "support",
     "note": "Concept ACK, ACK; suggested expanding warning message and logging available space",
     "association": "CONTRIBUTOR",
     "comments": 5,
     "first": "2026-10-22",
     "last": "2026-10-24"
    }
   ],
   "derivation": "objection that needs a change, the objector pushed back after a reply (andrewtoth)",
   "model_state": null,
   "corrections": [],
   "notes": "l0rinc replied to andrewtoth regarding release note wording and defended logging a warning when skipping compaction, but andrewtoth pushed back on the warning objection."
  },
  "dependencies": {
   "depends_on": [],
   "enables": []
  },
  "categories": [
   {
    "name": "docs",
    "member": false,
    "evidence": "Release note update is secondary to the code change in validation and dbwrapper.",
    "band": "Unranked",
    "reason_tag": "bug fix",
    "score": 0.0,
    "factors": {
     "bug_severity": 2,
     "leverage": 0,
     "performance": 0,
     "security_stability": 2,
     "user_value": 1
    },
    "rationale": "Release notes that accompany a functional code change do not qualify the PR for the docs category."
   },
   {
    "name": "mempool",
    "member": false,
    "evidence": "Touches src/validation.cpp only for chainstate compaction checks, not mempool or policy logic.",
    "band": "Unranked",
    "reason_tag": "bug fix",
    "score": 0.0,
    "factors": {
     "bug_severity": 2,
     "leverage": 0,
     "performance": 0,
     "security_stability": 2,
     "user_value": 1
    },
    "rationale": "The change does not affect mempool transaction acceptance, eviction, or policy rules."
   },
   {
    "name": "tests",
    "member": false,
    "evidence": "Touches src/test/coins_tests.cpp and src/test/fuzz/coins_view.cpp only to update tests for coins DB changes.",
    "band": "Unranked",
    "reason_tag": "cleanup",
    "score": 0.0,
    "factors": {
     "bug_severity": 2,
     "leverage": 0,
     "performance": 0,
     "security_stability": 2,
     "user_value": 1
    },
    "rationale": "Test updates that pin behavior for a specific domain change belong to that domain rather than test framework infrastructure."
   },
   {
    "name": "validation",
    "member": true,
    "evidence": "Carries 'UTXO Db and Indexes' label and modifies chainstate compaction in src/validation.cpp, src/txdb.cpp, and src/dbwrapper.cpp.",
    "band": "P1",
    "reason_tag": "bug fix",
    "score": 0.78,
    "factors": {
     "bug_severity": 2,
     "leverage": 0,
     "performance": 0,
     "security_stability": 2,
     "user_value": 1
    },
    "rationale": "Prevents node crashes and shutdown hangs caused by background chainstate compaction exhausting disk space. Issue #36585 reported that automatic background compaction 'filled the disk; node then hung after shutdown (v32.0rc3)', making this an important reliability regression fix for node stability."
   }
  ],
  "confidence": "high",
  "uncertainties": [],
  "needs": []
 },
 "cost_usd": 0.0,
 "source": {
  "record": "2026-11-02T01:11:51+00:00",
  "code": "2026-10-24T01:21:33+00:00",
  "judgments": 4
 }
}