Tally proposal substatus

[rin-st]

Do we need to use web scraping, onchain data, or if current status is enough? Try to check ongoing proposals to figure out

---

Details:

From #6

Status, substatus and substatus_deadline can be tricky, we need to check if we should use web scraping or try to figure out from onchain data

Website examples, copied from #17 (comment)

For the substatus I was thinking in this data that is shown in the sidebar of the website:

• Crosschain proposal status example:

• Not crosschain example:

Tally-ui -> Api event type mapping, copied from #17 (comment)

Tally UI → API Event Type Mapping

Standard flow

UI Label	API Event Type
Draft created	drafted
Published onchain	created
Voting period started	activated
Voting period ended	succeeded
Proposal queued	queued
Proposal executed	executed

Cross-chain/Arbitrum flow

UI Label	API Event Type
Draft created	drafted
Published onchain	created
Voting period started	activated
Extended voting period	extended
Voting period ended	succeeded
Proposal queued	queued
L2 Execution	callexecuted
L2-to-L1 message	(UI only, no event type)
L1 Execution	crosschainexecuted

Failure states

UI Label	API Event Type
Proposal defeated	defeated
Proposal canceled	canceled
Proposal expired	expired

Note: pendingexecution may appear between queued and executed as a waiting state. This mapping is inferred from Tally API docs and Governor contract events — no official UI↔API mapping exists.