Events & Governance Alerts
Get alerts for Stacks ecosystem events (meetups, hackathons, conferences, community calls) and Stacks governance activity (SIPs and CAB voting).
In short
Set up alerts for Stacks ecosystem events and SIP/CAB governance by describing them to Nova. Lists every trigger, condition field and polling interval (30 minutes for events, 2 hours for governance).
Get alerts for Stacks ecosystem events (meetups, hackathons, conferences, community calls) and Stacks governance activity (SIPs and CAB voting). Both are set up conversationally — no command or wizard, just tell Nova what you want to monitor. Available on Discord and Telegram.
How Setup Works
- Describe the alert to Nova in plain language.
- Nova interprets the request, builds the alert conditions, and confirms them back to you (e.g. "I'll set up an alert for new Stacks ecosystem events. Sound good?").
- You confirm, and the alert is created.
- Nova polls the data source on a schedule (see each topic below) and notifies you when conditions match.
Combining conditions is a Premium feature — Premium users can pair multiple conditions with AND/OR logic in one alert, e.g. "alert me about new virtual events only" (change_type = new_event AND event_type = virtual) or "alert me when SIP-034 reaches Ratified" (sip_id = sip-034 AND sip_status = Ratified).
Free vs Premium
Both alert types count toward your total alert limit. Free and Premium limits (alert count, conditions per alert, cooldown, time windows, digest mode) are in Smart Alerts and the Premium guide.
Ecosystem Events
Alerts when events are posted, about to start, or change status. Polled every 30 minutes — a cooldown of 30+ minutes is recommended. Data is sourced from the Zero Authority DAO events platform.
| Trigger | Details |
|---|---|
| New Event Posted | A new event was added to the Stacks ecosystem calendar |
| Starting Soon | An event is starting within the next hour |
| Status Change | An event's status changed (e.g. upcoming → in-progress, cancelled) |
Event details include: title, date/time, virtual vs in-person, location or meeting link, host, attendee count, token requirements, and on-chain attendance badges.
"Notify me when new virtual events are posted"
Condition fields (Nova builds these from your description):
| Field | Values | Description |
|---|---|---|
| change_type | new_event, status_change, starting_soon, any | What kind of event activity triggered it |
| event_type | virtual, irl | Virtual or in-person events |
| event_status | upcoming, in-progress, completed, cancelled | Current status of the event |
| host_username | Any username | Filter by event host |
| tokens_required | true, false | Whether the event requires token staking |
You can also browse without creating an alert — ask things like "What Stacks events are coming up?" or search events by topic.
SIP Governance
Alerts for Stacks Improvement Proposals (SIPs) and CAB (Consideration Advisory Board) voting. Polled every 2 hours — a cooldown of 120+ minutes is recommended. Data is sourced from the Zero Authority DAO Governance API.
| Trigger | Details |
|---|---|
| SIP Status Change | A SIP moved between stages (e.g. Draft → Review → Accepted → Ratified) |
| New SIP Proposed | A new SIP appeared in the registry |
| CAB Vote Opened | A Consideration Advisory Board vote was opened for a SIP |
| CAB Vote Closed | A CAB vote has concluded — includes yes/no/abstain tallies |
SIP details include: title, status, type (Meta/Consensus/Standard), consideration area, authors, abstract, GitHub PR link, and forum discussion link. CAB vote details include: which SIP, voting status (open/closed), vote tallies (yes, no, abstain), and total votes cast.
"Alert me when CAB voting opens on any SIP"
Condition fields:
| Field | Values | Description |
|---|---|---|
| sip_id | e.g. sip-032, sip-021, or any | Specific SIP or wildcard |
| sip_status | Draft, Review, Accepted, Activation-in-Progress, Ratified, Withdrawn, Rejected, or any | Target status |
| change_type | status_change, new_sip, cab_vote_opened, cab_vote_closed | What kind of governance activity |
| cab_voting_status | opened, closed, any | CAB vote state filter |
SIP lifecycle:
Draft -> Review -> Accepted -> Activation-in-Progress -> Ratified
\-> Withdrawn
\-> Rejected
CAB voting can occur at various stages and influences whether a SIP advances.
You can also browse without creating an alert — ask "What's the status of SIP-032?", list SIPs by stage, check open CAB votes, or view governance stats. Nova returns full SIP details including CAB voting state, vote tallies, and links to GitHub and forum discussions.
zadao.ai