Explore DAO votes, treasury records and governance thresholds.
ZecHub decides its funding on-chain, and the rule is stricter than it looks: a proposal needs 67% of yes+no and 40% turnout. This skill turns your coding agent into a copilot that computes both tests from the live indexer, names every voter, and reads the treasury without falling into its traps. Every figure comes with a citation.
npx skills add Michae2xl/openzcash --skill zechub-copilotBring your own model. No key, no hosted service.
Add to your agent
…and 40+ more agents the skills CLI supports. Omit -a to auto-detect your agent, or add -g to install globally.
❯
Did proposal A116 pass? It had twice as many yes as no.
No. It computes both tests and shows which one failed: 66.67% approval against a 67% bar. A yes-majority is not enough, and 25 proposals have died that way.
What is ZecHub voting on right now?
Every open proposal with its tally, turnout, and what it still needs: more votes for quorum, or more yes for the 67% bar.
How much can ZecHub actually spend?
The spendable balance, not the headline total. Three separate pots, and the biggest one is donations rather than working capital.
What has ZecHub paid contributors?
The payout table reconciled against the dashboard total. They differ by $5,200 because one is per-period and the other cumulative.
The skill encodes the traps that produce wrong answers: abstentions that carry quorum without diluting the threshold, closed and rejected both meaning defeat, milestones marked complete next to money still pending, a member count that is snapshotted per proposal, and the difference between what the DAO holds on-chain and what ZecHub can actually spend. It is read-only and never submits or votes.