WhyDRS
WhyDRS - Needs and Responsibilities for 2025 #33
Replies: 4 comments 5 replies
-
|
Thanks for the shout out, hopefully this saves people a bit of thinking and serves as a comprehensive to-do list/roadmap to an independent and self sustaining organization. One thing of note is that Github is a viable alternative to Notion or Trello so we already have that one down. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @tehchives and @LastResortFriend for the constant contemplation and contributions in these messages and many related discussions on the tail end of last year. Some of this behind-the-scenes work might go undocumented officially, but it's sincerely appreciated in my book (and I'm sure many others across the community). By ideating now, we can truly sow the seeds for an action-packed year—all thanks to your stellar efforts! Since it's shorter, I'll start with some remarks on LRF's comments: Workflow PublicationSite PublishingOne thing I love is that we can build our own site pages relatively easily and host them as a community through IPFS. This is what James has done through the Database repository.1 Instead of relying on another service to host our information, as has so perilously resulted in past censorship, we can just collectively agree on everything in one place. Then, thanks to repo replication between everyone, it becomes almost impossible to attack the underlying infrastructure, akin to P2P file sharing. Workboard PlanningI'll get these ideas fleshed out further in the DUNA repo in due time, but just wanted to echo your points here because they're awesome, LRF! Another incredible thing James has pioneered is the organization issuers project, which greatly helps lay out action items—as you've identified. By giving everyone the chance to bring their ideas and work to the table, I just know we're on the path to the ideal independent and self-sustaining organization you mention. ComplianceIRS FilingsAlong that line of thinking, I set up this nonprofit project a while back to make sure nothing falls through the weeds when it comes to government deadlines. For now, the registered agent and mailing center get paid for by the Syndicate via credit card, Wyoming charges no ongoing association fees, and Chives took care of all the IRS setup fees (which don't recur). As per the emergent legislation, I'm not familiar with any other individuals or orgs that have worked with the DUNA laws. That said, the work going forward aligns relatively closely with standard nonprofit filings. Since the post, we did achieve that coveted IRS approval—yay! I will never pretend to be a licensed lawyer or anything like that for the community, but certainly taking care of filing info is well within my skill set. Copyright / TrademarksI think we should chiefly get the brand icons secured and published under CC BY-SA 4.0 so that it's easy for any Apes to use the WhyDRS name in their own promotions of the org. This ought to make it that much easier to spread the community far and wide, continually meeting the requisite decentralization mandates of the DUNA structure. As for official content outside public forum postings, I've done my best to explore, implement, and adapt content policies that keep everything in the hands of the public. Financial EducationChives has always been super active on keeping everything generally informational—super appreciate that here! I think we've done a great job of academic fairness and impartiality by giving everyone the room to talk out their perspectives. I wonder how we might promote this inclusion in the coming year to further the exceptional research and investigation we see oftentimes on the Reddit side. Ape's GuideI know we've been talking about this for a while, and I'd love to chat a little about where/what format everyone would most appreciate for this. There's already a lot of basic GitHub how-tos online, so I want to make sure we have the info new contributors want so that everyone in the community gets up to speed faster than a general guide. I was supposed to get a couple of videos out explaining basic things last year, so my bad for dropping the ball on that one. Maybe the largest curse of knowledge is that I forget sometimes what it was like to first use this incredible tool. I agree that there are most certainly some incredible community members with expertise waiting to be tapped into, and it's just our task at this point to give them creative avenues to express their passions.2 The good news is that a lot of other open-source communities document their best practices, so we should have a massive starting point in agreement as you've suggested. Financial ItemsChives mentioned setting up a bank account like Mercury—sounds like an awesome start to me. Then we could easily get this configured with a simple nonprofit donation flow. This would start us off relatively centralized with that account and a central deploy system with donation receipts. Ideally, we can flow all funds into a blockchain wallet for financial transparency. No matter where monies come from, I think it should, in general, be much easier to track everything in a public address with a trusted multisig to start off. This is pretty trivial to set up with Stellar, and it could make it so everyone can see exactly where outgoing funds land without the traditional opacity of PDF statements. Merch / Sales 👕How are the merch sales in general? As I understand you chatted with others about, we can have those merch items via the store, and they are separate from actual (tax-deductible) donations. I'm not familiar with any reason we'd have to do this ourselves, but I do know we've been trying to get unit costs down by ordering in bulk. Are there any community members with a special background in consumer brand sales? Donation PlatformsThere are lots of tools to use on this front, so we might greatly benefit from greater discussion here. It's simple to set up donation pages on tons of platforms once we have the bank account, and sometimes even before that. I've been working on a more decentralized framework for some time on-chain, and will continue working this into our flow in due time. Stock donations are one idea I've had given the recent (relative) share growth of certain assets. I certainly don't want to turn everything into a mini hedge fund. Do you think many community members would be interested in donating shares (and thus not paying any capital gains tax)? Specific RolesI love that we're thinking prudently about what we want and will need to grow. We have some great ideas and goals here, and I'll touch more on the latter at the end. But I definitely want to be careful with saying we need this, that, or the other from existing members. Presently, we have no funds. But we can and do still grow and build new precedents based on what community members themselves choose to contribute in their free time. This drives right into the decentralization points interwoven throughout, and I think it's really important given a long-standing past of observing voluntary community developments. I just want to be careful with dictating to people because I believe deeply in everyone's ability to identify their best contributions. Attracting IndividualsWith 65 outstanding organizational issues, much of the notice systems we've used to attract attention so far on GitHub come from directly mentioning a friend. Indeed, it was through direct connections and word of mouth that James came to complete much of their work on the new and improved Database. Might we all continue searching for existing or new community members who could fulfill some of the ideated activities? A couple of names in the community already come to mind with an active day job in marketing, communications, or SEO. We have a unique opportunity in both the mission front and working experience. Might we focus on these as our outreach grows? Namely, we don't have (and I believe don't want) a single central coordinator deciding who hires someone for a job, recruits volunteers for activities, or deploys a new marketing campaign. By keeping everything in the public domain, perhaps we can scale this loose self-organization to allow anyone to share their best efforts.2 I agree deeply with the sentiment that anyone can opt in or out of the collaboration process at any time, and that requires a new approach to organizing labor. I think the best way to empower the process stands with individual control and leeway to take the best-known course towards shared goals. If we agree here and believe in the power of the individual to formulate paths to objectives, then perhaps the most useful starting tool might be coming up with the main objectives we want to achieve this year? Outreach Representation 🗣Since this post, we've already had a number of community members reach out to set up Taking Stock shows with special industry guests. This is just one example of permissionless action which I find quite important to protect. We can achieve incredible things when community members like Throw have the leeway to independently build their own scripts to copy SEC petition text, for example. That's why I love the idea of delegating as much power as possible to individual contributors. I know we've had chats back and forth about bad actors, but I honestly see no way to censor shills who may smear our name in the opacity of most private conversations. And we can sniff them right out and document our points for anything public. So I say why not give everyone a chance to lead their own outreach/fundraising/tech mini-projects? Team FormationWe still have a very loose definition of project leaders, and I find this exhilarating. Might leaders for certain aspects of the Association emerge naturally over time, rather than by means of a directive governance vote? And might they best maintain their local influence if they must constantly prove to other contributor-members their reliability, dedication, and vision? I think we can achieve this naturally through self-organization as volunteers step up through their own volition and communal support, as suggested. ✅ Especially in a more asynchronous environment, defining shared goals may be more effective than coordinating specific actions. While the latter case may be easier and more familiar to a management-boss type, I think the inspirational aspect ought to better motivate self-starters than would a task list. Planning the minutiae of someone else's work can be a demanding job, and I love the idea of moving away from this towards a more "self-identifying and volunteering team member" structure. Fund DistributionFirst and foremost, I have made some small monetary or service gifts to community members over the past brief year or so, and the result has always been nothing short of inspirational. As soon as we start discussing anything on resource allocation, I just want to submit that each and every contributor should be able to make a $100 mistake at any time without consequence.3 By giving proven members a little bit of cash to experiment, I think we can foster an abundant, growing movement. As for larger distributions, I agree with using DUNA votes as is common amongst other DAOs to distribute funds. We touched on the wallet configs earlier, but I want to explicitly talk about the use of funds before voting considerations. Again, I really believe in people to do what's best, especially if their reputation is on the line. Since we can keep the tokens, money assets, and even voting on-chain, it should be relatively trivial to track someone's overall Association activity through the burgeoning registry. Along this line of thinking, I believe we should give maximal leeway on fund usage. What I mean here is that it could be best for campaigns to specify their objectives and key results, not the minutiae of which tools or low-level strategies to use or buy. I believe members can contribute their best work when they have the freedom to withdraw a bulk sum of money to buy the items they need—no oversight or approval process needed. If it's abundantly clear by the nature of transparent on-chain data that something's amiss, then we can take permanent corrective action. But in general, the idea I hope we can protect with the treasury is a general trust in trusted members which extends to their own prudent use of entrusted funds. Tax Implications 📜This approach assumes spending away from a central nonprofit entity. Rather, it distributes monies to members as technical "income," which you can subsequently use towards the mission at hand.4 I find this approach advantageous because it takes purchasing power away from a central group of core roles and gives individual contributors or teams the power to invest directly in their own best efforts to further the mission. This decentralized leadership can most likely only flourish when enough budgetary independence empowers day-to-day support for the most active pressing achievements. Locus of ControlThis should make it much easier to define "approved actions" for anyone that happens to have a (partial) signing key for our treasury wallets.5 I think lowering the amount of trust we place in this function is crucial because money is power. If we can minimize the control any person or group has over this key resource of our nonprofit Association, then we can keep the influence and thus innovation dispersed across the entire community.6 Again, the point here is to extend daily decision-making down to the people best equipped to choose how to donate their efforts—you! If we can remove the management committee typically associated with work and fund distribution when money is a necessary input into some work product, then I think that's a positive and inclusive stride for the Association. We'll have to wait and see what the voting participation rates look like, depending at least in part on how specific we want proposals to be—especially when they request some kind of budget. But one of the big ideas is that, with tokens distributed to active members, perhaps reputation alone (backed up by wallet holdings) can serve as a daily guiding light towards the optimal path to our shared goals. Small Highlight
This really summarizes the ethos of what I'm trying to get at both before with the funding pools and to come with the governance implications. It's such an incredible new concept that I think will really blow the KPIs out of the water when it comes to organizational efficiency. We have an incredible new system that lets contributors sustainably self-elect to share their time and knowledge assets with the community for the sake of such a valiant mission. Now it's just up to us to kickstart this facilitation process into an incredible and historic year.7 Voting TokensFirstly, I want to leave the specifics of scaling mechanisms or other numeric implementation details to a series of DUNA blog posts specifically on the topic and soliciting feedback.8 There are some incredible pioneering reputation schemes immediately developing in the Network's ecosystems, and I plan to include prominent advocates and innovators in the design process. And of course, you can't trade reputation, so this aligns with the stated deference away from secondaries. Should society really allow a financial market for power? I like the progress we're developing in documenting some majority and quorum rules here. Just to keep it in the conversation, the "governing principles" of the "organization work tokens" which serve as the Association's membership interests do have a couple of policies specified.9 They specify that:
Proposal Logs 🗳I certainly agree with these sentiments under the broad guise of transparency. I've thought a lot about implementing our own chat site for this, as is common on certain blockchains. However, I think the easy community hub and moderation clarity present in GitHub would really serve our interests here. Not only would we have a direct, transparent, and automatic log of edits, but we'd also have direct attribution automatically linked to contributor profiles associated with a growing amount of open-source work. This could take the form of a simple repo like Updates and DashboardThese things should be fun to implement based on the already transparent blockchain data surrounding distributions of hard assets. If we want on-chain voting with histories associated with public keys, then that could get bundled into this interface, too! These are a lot of the factors I'm looking at and have built around to determine neural weight in the governance token influence distribution (contract). And of course, I agree that all this should be public, and any reports we want to generate associated with that could also be helpful. I certainly wonder what members will come up with when evaluating actions and votes. Maybe the nature of suggested goals could reveal one way to interpret contribution actions. I'd certainly like to see how they score in helping further higher-level agreed-upon goals and principles. Other IncentivesLove the idea of public recognition for valuable contributions. Still waiting for more exciting times like the shoutout TS episode with WhatCan celebrating the NSCC petition and James commending the Database efforts. Badges on Discord seem like a simple and enticing incentive, and I know we've also discussed having token-gated chat channels. I personally prefer everyone to be on an equal playing field, with no communications gated off to a select few in the Association. I've been on the other side of that relationship, blocked out from learning about new ideas, far too many times to believe in its justifications. But there's obviously nothing stopping any number of close contributors from forming their own servers, group chats, etc., to work on DRS progress in their own sphere. And I think this is one of the amazing aspects of a decentralized self-organizing structure. It doesn't matter what I or anyone else alone thinks when it comes to your activity, since the end labor and donations are up to you alone. And of course, this quite clearly leads to the most efficient organization of efforts and capital in my mind. Some exceptional ideas at the end there, and I look forward to seeing them mature this year! Personal GoalsI'll throw in the ring two things I'd really like to help happen this year in furtherance of our objectives11, which aren't mentioned elsewhere.
Any action we can take to further this digitized dollar or tokenized lending ought to dump gasoline on the emerging flame of TAD3, given the requisition of capital for the investment in new corporate raises. 🌱 Footnotes
|
Beta Was this translation helpful? Give feedback.
-
|
Hey @JFWooten4 , excellent reply! I don't know how to organize things outside the Discord currently but in regards to that I'm working on some channels and roles to think about implementing. Kickstart the platforms with the most community members and they will flow into the others as they are established and learned. I'll hopefully have it ready to present over the weekend but can't say for sure since my grandmother is visiting right now. A role that seems pretty high priority to me currently is having people who crosspost between platforms until each one has a ToS friendly automated solution to the platforms in question. Since most people aren't using github having some gophers bridging the gap to Discord and beyond will exponentially speed up progress and help us keep things steady in these early stages. Overall I'm hopeful in the next 2 weeks we can get a few more eyes in here and definitely have the ideas that occur here begin to flow outward and vice versa. One thing that springs to mind after reading your response is how to properly vet the people who will have access to funds and how to hold them accountable for stuff like fraud. There's definitely the kind of people who would laugh at making alts to waste funds for the lolz or even survival if there's no kind of verification for example. |
Beta Was this translation helpful? Give feedback.
-
|
Per cross-platform exposure, how about an Financial accountability certainly stands top of mind when it comes to fund management. My first instinct would be linking token ownership and the opportunity to manage funds. Of course, once the smart contracts get deployed, only an actual DUNA vote could move the assets, which sit safely on the blockchain elsewhere. Sounds like you have some exciting items in the works based on thorough and careful consideration – can't wait to see more awesome progress like this! Footnotes
|
Beta Was this translation helpful? Give feedback.
-
|
I like this idea - I know there's already a ton of channels, but having a place to discuss Git and open source separate from where code commits get posted by the bot seems like a smart and useful move. |
Beta Was this translation helpful? Give feedback.
-
|
That's an excellent soultion for Github > Discord and other platforms. The problem sort of arises with Discord > Github because Discord's ToS dictates you can't store message data anywhere at all. That's why I'm thinking couriers or some kind of sufficiently succinct AI summary for communications going in that direction. |
Beta Was this translation helpful? Give feedback.
-
|
"Hey @JFWooten4 , excellent reply! I don't know how to organize things outside the Discord currently but in regards to that I'm working on some channels and roles to think about implementing. Kickstart the platforms with the most community members and they will flow into the others as they are established and learned. I'll hopefully have it ready to present over the weekend but can't say for sure since my grandmother is visiting right now. A role that seems pretty high priority to me currently is having people who crosspost between platforms until each one has a ToS friendly automated solution to the platforms in question. Since most people aren't using github having some gophers bridging the gap to Discord and beyond will exponentially speed up progress and help us keep things steady in these early stages. Overall I'm hopeful in the next 2 weeks we can get a few more eyes in here and definitely have the ideas that occur here begin to flow outward and vice versa. One thing that springs to mind after reading your response is how to properly vet the people who will have access to funds and how to hold them accountable for stuff like fraud. There's definitely the kind of people who would laugh at making alts to waste funds for the lolz or even survival if there's no kind of verification for example." Is something I would have said 5 hours after you posted John but I apparently forgot to press comment lmao |
Beta Was this translation helpful? Give feedback.
-
|
Oh I'm dumb, I already said it, the message was still loaded in the write section for some reason. |
Beta Was this translation helpful? Give feedback.
-
|
Not dumb! Making sure the messages are going through is worthwhile!! |
Beta Was this translation helpful? Give feedback.
-
Happy holidays everyone! We are two weeks out from the end of 2024 today, and that means we are the same two weeks away from starting the next year. 2025 will be the first full year of so much for WhyDRS, including: maintaining the codebase on this GitHub, operating as a DUNA,
Last week, on Taking Stock #55, I discussed with some community members what key areas of need there were in 2025 to 1. sustain the resources and community we have built so far and 2. grow and expand on the diversity, participation, and accessibility of that community and those resources.
LastResortFriend suggested developing a broad overarching needs and wants list for WhyDRS as a collective, drafting it as a community, and then bringing it forward so that people who want to help but are not sure on how will be able to see where they can step in. The rest of this post is heavily inspired by an initial draft from LRF (and honorable mention to his friend ChatGPT), and we will collectively improve on this over the coming weeks. Also on the near horizon I'll work with other contributors to build something like an Apes Guide to (WhyDRS's) GitHub, in same inspiration as the Apes Guide to Lemmy we built last year.
We have come so far as a volunteer collective of retail enthusiasts and we can go much further still. For these items, we don't necessarily need specifically to hire an established expert to stay on retainer - if we can find good clear citation and best practices, and agree on them as a community, then we already know that can bring us very far. It may even be there are community members with some of these areas of expertise waiting to be tapped into!
General Needs for WhyDRS
1. Legal & Compliance
WhyDRS will need legal expertise to navigate organizational, financial, and liability risks. Of note - Since WhyDRS is the first DUNA in America through Wyoming's emergent legislation, there are not necessarily experts we can tap into in order to be well prepared for common pitfalls. Instead, we'll have to prepare for common items we expect to still impact us, in addition to embracing legal talent which is curious about operating in a brand new regulatory space and potentially helping to set precedent. At time of writing WhyDRS is also still pending IRS approval to operate as a charitable nonprofit with the DUNA corporate structure.
• Nonprofit & Organizational Lawyer: Ensure compliance as a decentralized, unincorporated nonprofit.
• Securities & Financial Lawyer: Advise on SEC compliance and the legal boundaries of financial education. (Maintain academic fairness and impartiality if discussing individual stocks, or afford all stocks equal coverage)
• Intellectual Property (IP) Lawyer: Protect the WhyDRS brand, content, and materials.
• Tax Lawyer/Nonprofit Tax Specialist: Assist with tax implications for donations and resource allocation.
• Liability Lawyer: Mitigate personal and organizational liability risks.
• Compliance Officer: Monitor internal operations to ensure alignment with legal and ethical standards. (Where possible, we can lean into transparency to mitigate some compliance concerns and ask the community to assist in auditing behavior)
2. Financial Needs
Expertise to manage funds, resources, and reporting:
• Nonprofit Financial Advisor: Guide fundraising, budgeting, and resource management.
• Financial Compliance Expert: Ensure transparency in fund allocation and reporting.
• Fundraising Manager: Develop and execute donation and crowdfunding strategies.
• Merchandise and Services Specialist: We currently have a zero-profit merch storefront, but is it possible to offer items where users can add on optional donation? Would this require printing shirts and shipping them out ourselves? What if we offered free access resources, and a donation in order to download higher quality videos? Just some ideas, and I'm not sure of their feasibility.
3. Mission-Driven Outreach Needs
Roles directly supporting DRS education, awareness, and advocacy:
• Content Creators: Write articles, produce graphics, videos, and guides explaining DRS.
• Content Strategist: Oversee content consistency, quality, and strategy.
• Social Media Coordinators: Manage outreach across platforms like Twitter, Reddit, and Discord.
• Education & Outreach Specialists: Host webinars, create step-by-step guides, and engage with FAQs.
• Advocacy & PR Specialists: Build relationships with influencers, media outlets, and advocacy groups. Similarly, reach out to legacy and online media groups which are established and within the financial niche. What messages could work for which platforms?
• Front-Facing Personnel: If invited to a podcast or media program to spread the word about the nonprofit, which community members are willing and able to appear OR do we encourage anyone to spread the message, in vision of the decentralized nature of the effort?
• Crisis Communications Advisor: Prepare messaging plans for potential reputational risks.
4. Technical & Operational Needs
Roles to support the infrastructure and technological requirements:
• Technology Manager/Platform Architect: Maintain websites, forums, and tools for community collaboration.
• Cybersecurity Expert: Protect member data, forums, and platforms from attacks.
• Project Manager: Coordinate decentralized efforts, manage tasks, and ensure deadlines are met.
• Systems Administrator: Handle technical upkeep for servers, Discord bots, or websites.
• Search Engine Optimization: WhyDRS is (likely) already the largest online resource for custodial investor information. How can we get this in front of more people when they ask related questions?
5. Community Engagement Needs
Support for maintaining a motivated and inclusive decentralized network:
• Community Engagement Strategist: Build programs to activate, retain, and organize volunteers.
• Volunteer Onboarding Specialist: Streamline processes to integrate new decentralized contributors. This will include creating guides to participate.
6. Organizational Infrastructure Needs
Support roles to keep WhyDRS organized and efficient:
• Operations Coordinator: Oversee day-to-day administrative tasks and decentralized workflows.
• Data & Reporting Specialist: Track progress, analyze performance metrics, and report results transparently.
• Ethics Advisor: Maintain high ethical standards and handle conflicts of interest within the organization.
Summary of Contribution Model
1. Roles for Decentralized Members
The key to the decentralized model is that anyone, at any time, can opt in to or out of the collaborative research and resource building process. What kinds of engagement are available to people who are contributing?
• Content Creation (writers, designers, video producers)
• Social Media Management (platform moderation and outreach)
• Education & Outreach (webinar hosts, FAQ writers)
• Community Engagement (onboarding, volunteer coordination)
• Technology Maintenance (platform support and bot maintenance)
2. Roles for Dedicated Specialists or Consultants
Conversely, these roles may require more commitment and trust, as they would operate in an ongoing capacity for needs which are expected to be permanent. Also, ongoing members can help less consistent members make sure their contributions can be built on by others if they need to step away.
• Legal: Nonprofit, securities, IP, tax, and liability lawyers
• Financial: Financial advisors, compliance experts, fundraising managers
• PR & Advocacy: Media relations, PR strategists, crisis communications
• Technical: Cybersecurity experts, platform architects
• Organizational: Project managers, code consistency, messaging consistency, ethics advisors, and data specialists
Decentralized Roles and Governance Structure
1. Core Decentralized Leadership Roles
These roles ensure day-to-day decision-making while empowering the broader membership to participate actively.
• Facilitators act as temporary stewards to organize discussions, manage workflows, and summarize progress. There could be Rotational leadership where facilitators are selected on a periodic basis (e.g., monthly/quarterly). Multiple facilitators can lead on different projects or focus areas (e.g., outreach, fundraising, tech). Selected via community vote, either through online voting platforms like polls or through the DAO.
• Project Leads Coordinate specific initiatives (e.g., content creation campaigns, social media drives). Volunteers step into this role based on skills and interest, and Community approval or consensus verifies their position. Decentralized project development benefits heavily from not only enthusiastic self starters, but from those who can motivate others to join them. Project leads could provide regular project updates to the community to ensure progress and transparency or distribute tasks amongst self-identifying and volunteering team members.
• Treasury Stewards oversee fundraising and resource allocation. Rather than making distribution decisions themselves in a general sense, Decentralized members vote on fund usage for campaigns or tools. Treasury Stewards execute approved actions and must use Transparent wallets (e.g., multi-signature crypto wallets or open financial reporting platforms) and reporting so that it can be easily audited and monitored by the community.
2. Voting and Decision-Making Process
Voting mechanisms ensure equal participation and collective ownership in decision-making. Per the DUNA legislation and our certificate of organization, anyone can self identify as a member of the collective WhyDRS (or, similarly, rescind that membership).
• Proposals Framework: Members submit proposals for initiatives, funding needs, or changes in structure. Proposals must include:
◦ Objective: Clear purpose and benefits.
◦ Scope: What’s required (e.g., funds, time, tools).
◦ Deliverables: Expected outcomes and timelines.
• Voting Mechanisms are not finalized, but have been discussed. The prevailing concept is to provide governance tokens commiserate with community participation and resource development, and introduce a staling mechanism so tokens expire or weaken in power over time. We can consider Reputation-based or contribution-based weights, with the goal to maintain active contributors holding more voting power. We also have discussed making the tokens lose their voting power upon being traded to another wallet, to limit or eliminate the secondary market.
• Majority Rules: Default is simple majority (51%) approval.
• Quorum Threshold: Determine a Minimum percentage of participants (e.g., 20%) required for valid votes.
3. Transparency and Accountability Structures
To maintain trust, WhyDRS needs transparent systems to track decisions, progress, and fund usage.
• Proposal Logs: Public record of all proposals, votes, and results. UI for ease of access and democratic participation.
• Treasury Dashboard: Real-time transparency for funds raised, allocated, and remaining, or with as much disclosure as we are able.
• Regular Updates from above roles Facilitators and Project Leads provide updates to the community via:
▪ Weekly/bi-weekly check-ins. Taking Stock may transition to fill this role OR we dedicate different community discussion time to this, and try to transition Taking Stock into doing more interviews with other community figures or to discuss new legislation or current events.
▪ Public dashboards or reports.
4. Incentivize Contributors
Maintaining decentralized participation requires a balance of intrinsic and extrinsic rewards.
• Develop Reputation System: Contributions (e.g., content creation, outreach, tech support) build a reputation score or status within the community. Higher reputation can result in potential, yet-to-be-discussed benefits, such as More voting weight or Recognition and leadership opportunities.
• Contributor Recognition: Public acknowledgment of valuable contributions. Integrated incentives like badges, shoutouts, or unique roles on Discord.
• Funding for Initiatives: Contributors can propose funding for tools, software, or resources they need to achieve their work. Community votes approve these requests. Additionally, GitHub does natively support providing funding and support for individual contributors if community members are interested to do so.
5. Conflict Resolution and Consensus Building
A structured approach ensures disputes don’t disrupt decentralized operations. Is it important for us to plan ahead for potential distraction issues which could wedge or distract conversation?
• Dispute Mediators: Trusted community members (rotational or elected) act as neutral mediators for conflicts.
• Determine a Consensus Process if disagreements arise:
1. Discussion Stage: Open community dialogue to address concerns.
2. Modified Proposals: Adjust the proposal based on feedback.
3. Final Vote: Majority vote determines the outcome.
6. Scalable Tools for Decentralization
Practical tools that facilitate smooth decentralized governance:
• Discord: For real-time communication and proposal discussions.
• Snapshot: For voting without transaction costs.
• Notion or Trello: For tracking proposals, tasks, and organizational updates.
• Gnosis Safe (or similar): For transparent multi-signature fund management.
• Loomio: Consensus-building platform for structured decision-making.
Organizational Flow for WhyDRS DAO
What is the simplest step by step process from when a new idea is presented to the community via the DAO, to its implementation as a completed concept?
1. Proposals Submitted: Any member can submit a formal proposal to the community.
2. Community Discussion: Open platform for feedback and debate.
3. Voting Phase: Members vote on whether to approve the proposal.
4. Project Execution: Approved proposals are led by Project Leads or decentralized contributors.
5. Progress Updates: Facilitators and leads share regular updates.
6. Treasury Oversight: Treasury Stewards manage and report on resource usage.
Summary of Decentralized Structure
Wrapping all the above in a bow.
1. Core Leadership: Rotational facilitators, treasury stewards, and project leads.
2. Proposals & Voting: Transparent proposal system with transparent updates throughout.
3. Transparency Systems: Real-time logs, treasury dashboards, and public updates.
4. Accountability: Reputation systems, clear reporting, and dispute resolution.
5. Incentives: Recognition, reputation, and funding for tools / contributions / individuals.
6. Scalable Tools: Create consistent processes at the ground level to maintain efficient decentralized operations.
Beta Was this translation helpful? Give feedback.
All reactions