Skip to content

feat(examples): DAO to propose polls and vote #4082

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 20 commits into
base: master
Choose a base branch
from

Conversation

moonia
Copy link

@moonia moonia commented Apr 8, 2025

A simple DAO that allows members to create polls (proposals) and vote on them.

Add the following:

Realms:

r/moonia/home: Renders the DAO dashboard listing all existing DAOs and exposes user-facing actions.

p/moonia/utils: Provides helper functions for caller identification and safe index parsing

Pure:

p/moonia/dao: Core logic of the DAO. Includes membership, proposal creation and deletion, voting.

p/moonia/admin: Manage admin rights and actions.


I'm also looking for suggestions on file organization. 🚀

@Gno2D2
Copy link
Collaborator

Gno2D2 commented Apr 8, 2025

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):
  • IGNORE the bot requirements for this PR (force green CI check)
  • The pull request description provides enough details
Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)
🟢 Pending initial approval by a review team member, or review from tech-staff

☑️ Contributor Actions:
  1. Fix any issues flagged by automated checks.
  2. Follow the Contributor Checklist to ensure your PR is ready for review.
    • Add new tests, or document why they are unnecessary.
    • Provide clear examples/screenshots, if necessary.
    • Update documentation, if required.
    • Ensure no breaking changes, or include BREAKING CHANGE notes.
    • Link related issues/PRs, where applicable.
☑️ Reviewer Actions:
  1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.
📚 Resources:
Debug
Automated Checks
Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 The pull request was created from a fork (head branch repo: moonia/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

Pending initial approval by a review team member, or review from tech-staff

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 Not (🔴 Pull request author is a member of the team: tech-staff)

Then

🟢 Requirement satisfied
└── 🟢 If
    ├── 🟢 Condition
    │   └── 🟢 Or
    │       ├── 🔴 At least 1 user(s) of the organization reviewed the pull request (with state "APPROVED")
    │       ├── 🔴 At least 1 user(s) of the team tech-staff reviewed pull request
    │       └── 🟢 This pull request is a draft
    └── 🟢 Then
        └── 🟢 Not (🔴 This label is applied to pull request: review/triage-pending)

Manual Checks
**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

  • Any user with comment edit permission
The pull request description provides enough details

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 Not (🔴 Pull request author is a member of the team: core-contributors)
    └── 🟢 Not (🔴 Pull request author is user: dependabot[bot])

Can be checked by

  • team core-contributors

@leohhhn leohhhn self-requested a review April 8, 2025 19:29
Copy link

codecov bot commented Apr 8, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

Copy link
Contributor

@leohhhn leohhhn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, left some preliminary comments :)

Comment on lines +34 to +49
func ParseQuery(path string) (daoID string, showStats bool) {
parts := strings.Split(path, "?")
if len(parts) < 2 {
return "", false
}

args := strings.Split(parts[1], "&")
for _, arg := range args {
if strings.HasPrefix(arg, "dao=") {
daoID = arg[len("dao="):]
} else if arg == "stats" {
showStats = true
}
}
return
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this package seems like general utils package, but then you see that it's actually not, as it has things replated to your specific app. When you separate code like this, it also makes sense to think about how other people might use your code.

In this case, I have two things to say:

  • maybe this utils package should be under r/moonia/home/utils, or /internal
  • for handling queries and paths, you can use the p/demo/mux package. Check this tutorial out: https://gno.land/r/docs/routing

Comment on lines +8 to +44
// Admin Methods //

func IsAdmin(addr std.Address) bool {
return ds.DAO.IsAdmin(addr)
}

func SetAdmin() string {
return ds.DAO.SetAdmin()
}

func TransferAdmin(addr std.Address) string {
return ds.DAO.TransferAdmin(addr)
}

func KickMember(addr std.Address) string {
return ds.DAO.KickMember(addr)
}

func AddMember(addr std.Address) string {
return ds.DAO.AddMember(addr)
}

func ListMembers() map[std.Address]bool {
return ds.DAO.Whitelist
}

func AcceptRequest(addr std.Address) string {
return ds.DAO.AcceptRequest(addr)
}

func DeclineRequest(addr std.Address) string {
return ds.DAO.DeclineRequest(addr)
}

func ListRequests() map[std.Address]bool {
return ds.DAO.ListRequests()
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a lot of boilerplate code. Check out the safe object examples such as ownable, and try to make a top-level struct that is safe to expose, and also automatically gives you the getters and setters you need.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🧾 package/realm Tag used for new Realms or Packages.
Projects
Status: No status
Status: In Progress
Status: Triage
Development

Successfully merging this pull request may close these issues.

3 participants