DRepTalk reads on-chain data (governance tallies and status, DRep profiles, vote badges) on a schedule, not on every page load. That keeps the platform fast and cheap to run. It also means these values are cached, not live: each one is shown with an explicit “as of” time, and we never claim it is live. Forum posts themselves are never delayed. Here is how often each thing updates.
| Data | Refresh | Notes |
|---|---|---|
| Forum posts and topics | Immediate | Real forum activity is not delayed; anonymous views are edge-cached for about 30 seconds. |
| Governance actions (new threads) | About every 15 minutes | A discovery cron opens one thread per new on-chain action. |
| Governance tallies and status (DRep, SPO, CC) | About every 15 minutes, active actions only | Frozen once an action is ratified, enacted, expired, or dropped. Shown with an “as of” time. |
| Per-post vote badges | About every 20 minutes, active actions only | Vote lists are larger than the tallies but still refresh on a short cycle. |
| DRep profiles (name, bio, avatar) and status | About every 4 to 6 hours | The drep-sync cron keeps every DRep profile current. |
| DRep role re-check (write access) | Daily | Independent of the login session. |
Which vote rationales appear
On a governance action’s Positions tab we show the on-chain rationales attached to votes. Each rationale is a separate document the DRep links from their vote, often hosted on IPFS or their own server, so reading one means fetching an external file. To keep the page fast and reliable we surface the rationales behind the largest share of the voting weight first, and widen coverage from there over time. A rationale that is not shown here yet is in no way diminished: it stays permanently recorded on-chain, fully valid, and you can open it directly from the vote’s on-chain link.
Rationales come in two on-chain shapes: a single free-text comment, and a structured form that splits the reasoning into a summary, a full statement, and a conclusion. We render both, so an institutional DRep who files the structured form reads the same as anyone else.
A vote can also be cast after an action has already passed its threshold and gone to ratification. It is still a valid on-chain vote, and we show it with its rationale, but its weight was not part of the frozen tally, so on the Positions tab we mark it “not counted” and strike its weight through.