stacks-network / stacks-network/docs

Tutorial: Building a Governance Token (SIP-010 + On-Chain Voting)

Open
#1,837 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
185
Forks
273
Avg merge
4d 13h
Merged PRs (30d)
4

Description

Gap Identified

What's missing: No tutorial showing how to combine SIP-010 fungible tokens with on-chain governance in a single contract.

Evidence:

  • Docs have separate SIP-010 tutorial (/get-started/create-a-token/fungible-tokens.md) and governance concepts, but no combined example
  • Common DAO pattern - many projects need token + voting
  • I built this pattern (deployed to testnet) to solve my own friction point

Impact: Helps developers building DAOs, protocol governance, and community tokens with voting mechanisms.


$(cat /tmp/governance-token-tutorial.md)


Working Code

Repository: https://github.com/bastiatai/governance-token

For Docs Maintainers

This content is ready to add to the docs as-is. Suggested location: docs/get-started/create-a-token/governance-tokens.md or docs/tutorials/governance-token.md

The tutorial includes:

  • Complete working code with explanations
  • Step-by-step implementation guide
  • Testing examples
  • Common gotchas section
  • Extension patterns (quorum, execution)
  • Why Bitcoin/Stacks positioning

Let me know if you need any changes or additions.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the existing SIP-010 tutorial at docs/get-started/create-a-token/fungible-tokens.md and the governance documentation first. Check the proposed tutorial content and the linked governance-token repository, then add and verify the tutorial in one of the suggested documentation paths; done means the combined token and voting guide is complete and consistent with the docs.

Written by the indexing model from the issue text.

Assessment

Domain
blockchain, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.