Understanding a governance action page

Last updated 2026-08-02

Every Cardano governance action has its own page on DRepTalk, whether or not anyone has commented on it yet. The page collects everything about the action in one place: what it proposes, what the community says about it, who voted and why, and where it stands in its lifecycle. This guide walks through each part of the page.

You can reach an action from the governance actions list, from a DRep’s voting record, or by pasting its id into the search box. The list offers several sort orders; Sorting governance actions explains what each one means.

The tab bar

Under the action’s title sits a tab bar with five tabs: Overview, Discussion, Votes, On-chain Data, and History. Discussion and Votes carry counts, so you can see at a glance how much conversation and how many votes an action has drawn. On a phone the bar scrolls sideways.

A governance action page header on DRepTalk with the tab bar: Overview, Discussion, Votes, On-chain Data, and History

Overview

The Overview is what the proposer submitted: a summary of the on-chain changes the action would make, followed by the abstract, motivation, and rationale from the proposal’s metadata. It is the tab to read first when you want to understand what is actually being decided.

Below the proposal text, Rationale highlights shows a balanced selection of vote rationales: the strongest Yes and No positions by voting power, each expandable in place. It is a quick way to hear the best argument from both sides without reading every vote.

The sidebar next to the content answers the status questions:

The voting information card: Yes, No, and Not-voted shares of eligible voting power for DReps, SPOs, and the Constitutional Committee, with a voting trend chart

Discussion

The Discussion tab is the action’s public thread. Anyone can read it without signing in. Posting requires an on-chain governance identity: DReps, proposers and their co-proposers, SPOs, and Constitutional Committee members can sign in and post. Every post carries its author’s verified on-chain identity and links back to their profile, so you always know whether a comment comes from a DRep, the proposer, or another voter.

Frozen rationales

Some posts in the discussion are labeled Rationale and marked as frozen. These are vote rationales that a DRep chose to cross-post into the thread when casting their vote. The original document is committed on-chain together with the vote and cannot change afterwards, so the discussion copy cannot be edited either: what you read is exactly what was committed, with a link to the on-chain record. You can reply to a frozen rationale like any other post.

If the DRep later changes their vote, the frozen copy does not linger: it is replaced by the new rationale, or removed if the DRep did not cross-post again.

A frozen rationale post in a discussion thread: a DRep's cross-posted vote rationale with Voted Yes and Rationale badges and a frozen notice linking to the on-chain record

Votes

The Votes tab lists every DRep and SPO vote on the action, ordered by voting power, with a toggle to switch between the two bodies. Each row shows the voter, their vote, and their voting power at the time. Rows with a rationale expand in place so you can read the reasoning without leaving the page.

Two markers are worth knowing:

A vote row on the Votes tab, expanded to show the DRep's rationale, with a Changed badge, the superseded earlier vote, and a copy-link button

Every vote row has a copy-link button, so you can share a link that opens the page with exactly that vote expanded and highlighted. Votes with a rationale also have their own shareable page; see Linking to DReps, governance actions, and votes.

On-chain Data

The On-chain Data tab shows the action’s raw on-chain fields: ids, deposit, return address, anchor URL and hash, and the type-specific values the action would set. It is the reference tab when you want the exact values rather than the narrative.

History

The History tab shows the action’s lifecycle as a timeline: when it was submitted, how support developed over the voting window, and how it ended. A chart tracks cumulative Yes support per voting body across the window, so you can see whether an action cleared its threshold early or crossed the line late. Epochs are shown with their calendar dates.

Frequently asked questions

Who can post in the discussion?

Reading is public. Posting requires signing in with an on-chain governance identity: DRep, proposer or co-proposer, SPO, or Constitutional Committee member. Delegator sign-ins are read-only. See Signing in.

Why is a rationale post marked as frozen?

It is a copy of a rationale committed on-chain with a vote. The on-chain document cannot change, so the copy cannot be edited. It is replaced or removed if the DRep re-votes.

Why is a vote marked as not counted?

It was cast after the action was ratified, when the deciding tally was already frozen. It is shown for completeness but did not affect the outcome.

Are the numbers live?

They are synced from the chain on a schedule, usually within minutes, and each page shows an as-of time. See Data freshness.