Meeting Notes: dRep Forum / dRep Collective

Governance DRep Discussion
, , ,
1

About the dRep Collective

The dRep Collective is a key working group within the dRep Forum, the largest dRep community in Cardano, representing over 33% of all active dRep delegations and more than 360 members.

Our mission is to:

  • Increase delegation to more dReps.
  • Build a decentralized distribution channel for governance.
  • Address voter apathy and activate more ADA in governance.

Through initiatives like improving dRep metadata standards and creating a dRep ecosystem map, we aim to help ADA holders better understand and connect with dReps, making governance more accessible and effective.

About This Thread

This post will serve as the central location for publishing dRep Collective meeting transcripts and recordings. By working in the open, we ensure full transparency and invite anyone willing to pick up a shovel to join us.

To keep this forum fully community-driven and inclusive, invitations have been extended to IO, Intersect, and CF to moderate the forum alongside community members.

First Meeting Transcript & Recording

Below is the transcript and recording from our most recent meeting, held on January 15, 2025, at 14:45 GMT. This session focused on key governance challenges, metadata standards, and actionable steps to enhance dRep participation.

Key topics discussed:

  • Development of a DREP ecosystem map.
  • Refining metadata standards.
  • Structuring sustainable governance initiatives.

Stay connected and explore more resources via our Linktree.

Future meeting transcripts and recordings will be added as replies to this post. Let’s build a stronger, more inclusive governance ecosystem together!

4 Likes
2

DREP Collective Recording - 2025/01/15 14:45 GMT - Transcript

Attendees

  • Alpine Oracle
  • Ben O’Hanlon (acting as Community Member, Intersect)
  • Dominick Garey
  • Freddy T
  • Kevin Mohr
  • Ratio
  • So Litty Records
  • Sudo Scientist
  • Tyler Malin

Introduction and Disclaimer

Disclaimer: This transcript is an AI-generated document derived from a recorded meeting. As such, it may contain transcription inaccuracies or formatting inconsistencies. This document has not been officially vetted by any party but reflects a community-driven discussion.

Important Notes on Context and Roles

  • Discussions represent brainstorming and idea-sharing among community participants and do not necessarily reflect the official stances, policies, or commitments of any organization, including IO or CF.
  • Ben O’Hanlon participated in this meeting in a personal capacity as a community member and member of Intersect**, not as an official representative of IO.
  • This transcript and the associated discussions should not be construed as official proposals, commitments, or endorsements.

Key Themes Discussed

  • Metadata Standards: The need for metadata to be permanent, as well as data that can dynamically change based on voting and interactions.
  • Ecosystem Mapping: Development of an interactive map for educational and navigational purposes within the Cardano ecosystem, with tie-ins to governance tools.
  • Soulbound NFTs: Discussions on creating soulbound NFTs for voting passports, credentialing, and proof of reputation.
  • Coordination and Structure: Challenges of coordinating DREPs and standardizing practices for improved interoperability.
  • Community Involvement: Importance of self-reporting metadata to maintain transparency and autonomy in categorization.
  • Funding and Adoption: Exploration of funding models for sustaining initiatives and strategies for driving ecosystem adoption.

Excerpts on Specific Points

Metadata Standards

Kevin Mohr: Into the metadata…we’ve sort of narrowed it down. We want permanent metadata and data that changes. Finalized votes at the end of a voting period need to be permanent. We don’t want those votes to change after the period has ended. Additionally, we’d have DREP IDs and wallet IDs so that NFTs can remain soulbound. Data that changes would be tied to user actions, like votes.

Ecosystem Map

Kevin Mohr: The ecosystem map is going to be interactive, educational, and informative. It’ll correspond to certain actions with governance tools and other ecosystem parts. For example, if we go to Intersect and they pass some info action, a map could display Intersect’s role in the ecosystem. Maybe you’d get a stamp or credential for your voting passport.

Soulbound NFTs

Ben O’Hanlon: One of the coolest things about the soulbound NFT concept is that it’s perennial. This isn’t just about creating NFTs; it’s about validating DREPs and reflecting voting histories. It’s also about creating sustainable, self-reporting content that generates revenue opportunities for stakeholders like DREPs and SPOs.

Adoption Strategies

So Litty Records: For adoption, we should start aggregating a list of platforms to engage with, like wallets, Pool PM, and others. Offering assistance to these platforms in implementing standards can accelerate adoption.

Next Steps and Workstreams

  1. Metadata Workstream: Finalizing standards for permanent and dynamic metadata. Ensuring interoperability with ecosystem tools.
  2. Ecosystem Mapping: Developing the interactive map and defining its functionality.
  3. Community Engagement: Establishing a Discord for discussions, hosting future calls, and creating centralized resources.
  4. Funding Models: Exploring Catalyst proposals, public goods funding, and potential DAO frameworks.

Final Notes

  • The next meeting will focus on formalizing responsibilities, identifying actionable steps, and securing funding for ongoing work.
  • A link tree will be created to centralize resources, including relevant documents, standards, and discussion platforms.
  • Feedback is welcome to refine this transcript and drive alignment across stakeholders.

Thank you to all participants for contributing to this evolving discussion.
This transcript represents a collaborative effort to advance decentralized governance and ecosystem growth on Cardano.

3

Is SoulBound the final name or is this tentative in the interim?

4

Sound bound is a type of NFT. What Are Soulbound Tokens? The Non-Transferrable NFT Explained

1 Like
5

Thanks for info
Just sent the application to join this community
Hopefully, will attend future meetings

6

DRep Collective Meeting #4 Notes:

Full Video: https://www.youtube.com/watch?v=DDREkhbjCsQ

Meeting Overview

  • Date & Time: Not explicitly stated in the transcript, but it’s essential to note for future reference.
  • Agenda:
    1. Metadata Discussion: Focus on understanding the current status of metadata development and gathering community input.
    2. Ecosystem Mapping: Review previous research and integrate findings into a cohesive ecosystem map.
    3. Feedback Section: Open floor for community members to share thoughts and suggestions on ongoing projects.
    4. Social Media Updates: Share recent developments and strategies for improving community engagement through social media channels.
    5. Hard Fork Discussion: Address the implications of upcoming changes in the ecosystem and how they affect community governance.

Key Points from the Meeting

Metadata Discussion

  • February 1 Deadline: The team emphasized the urgency of gathering community feedback before the February 1 deadline for metadata submissions. Members need to ensure that all perspectives are represented.
  • Community Involvement: There is a strong desire for the metadata project to reflect the collective’s needs, indicating that input should not just be top-down but involve grassroots feedback.
  • Feedback Mechanism: A proposal was made to create a Google Form to facilitate structured feedback collection. This would streamline the process and make it easier for community members to provide their thoughts without the chaos of open discussions.

Ecosystem Mapping

  • Work Streams Identified:
    Need:
    1. Working docs, channel strategy & content.
    1. Working docs, workstreams written out.
    • Outreach: Engage with wallet providers and third parties to ensure their needs and capabilities are included in the metadata discussions.
    • Mapping: Focus on the artistic and functional aspects of the ecosystem maps, ensuring they are visually appealing and informative.
    • Development: Previous research should be bundled and made accessible to inform current mapping efforts, ensuring the collective builds upon past work rather than starting anew.
  • Importance of Collaboration: Stress on the need for various stakeholders, including developers, community members, and external partners, to work together to ensure the ecosystem map is comprehensive and functional.

Social Media and Community Engagement

  • Channel Strategy: Development of a detailed plan to effectively communicate updates and engage with the community through social media platforms. This strategy should include identifying key messages and choosing the right channels for dissemination.
  • Feedback Loop: Emphasis on maintaining open lines of communication with the community, allowing them to provide ongoing feedback on projects and initiatives. This could help in adapting strategies based on community sentiment.

GitHub and Documentation

  • GitHub Usage: Discussion on how to utilize the GitHub account for the collective’s projects, including how to organize repositories and manage contributions from different members. This is crucial for transparency and collaboration.
  • Open Source Principles: A strong commitment to transparency in development processes, ensuring that all documentation and code are publicly accessible, fostering a sense of community ownership over the projects.

Action Items

  • Feedback Collection: Establish a clear mechanism for ongoing community feedback on the metadata and ecosystem mapping processes, possibly through regular check-ins or surveys.
  • Documentation: Finalize a mission statement that encapsulates the collective’s goals and a code of conduct that outlines expected behaviors and responsibilities within the community.
  • Collaboration with Intersect: Actively explore potential funding and support opportunities from Intersect to help sustain the ecosystem mapping initiatives, ensuring that the collective has the necessary resources to execute its plans effectively.

Closing Remarks

  • Next Steps: Coordinate timelines for deliverables, including the metadata project, ecosystem mapping, and the development of a voting platform for internal governance.
  • Call for Participation: Encourage members of the collective to get involved in specific work streams based on their interests and expertise, fostering a culture of collaboration and shared responsibility.

Additional Notes

  • Transparency: Ensure that all discussions, decisions, and plans are well-documented and shared with the community to maintain transparency and trust.
  • User Experience: Consider developing a platform that enhances the user experience for newcomers, providing a clear understanding of the ecosystem and how they can engage effectively.

These expanded notes provide a more detailed account of the discussions and action items from the meeting, serving as a comprehensive guide for future initiatives within the DP Collective.

2 Likes
7

DRep Collective Meeting #5 Notes:

In this meeting, group members convened to establish a structured agenda for their ongoing collaborative projects, particularly focusing on the development of ecosystem maps related to the Cardano blockchain. The meeting began with a review of highlights from the previous meeting, emphasizing continuity and accountability. The agenda was organized into several segments, including workstream updates, volunteer opportunities for coordination, and discussions on community involvement. Participants engaged in a collaborative dialogue to identify key areas of responsibility, volunteer for workstreams, and establish a timeline for actionable tasks. The meeting also featured an introduction from new members and updates on various projects, including the development of a mission statement and partnership strategies. The group emphasized the importance of communication, project management, and the need for defined roles to streamline their efforts moving forward.

Highlights

  • :speaking_head: Structured Agenda: The meeting introduced a clear agenda structure to enhance collaboration and accountability among members.
  • :earth_africa: Workstream Ownership: Members were encouraged to volunteer for specific workstreams, creating a sense of ownership and responsibility.
  • :date: Regular Updates: Emphasis was placed on weekly updates for each workstream to ensure progress tracking and transparency.
  • :arrows_counterclockwise: Community Engagement: Discussions highlighted the importance of involving the community and sharing information across various channels.
  • :chart_with_upwards_trend: Project Development: Updates included ongoing projects like ecosystem mapping and the need for a mission statement, reflecting a focus on long-term goals.
  • :handshake: Partnerships: The group discussed strategies for building partnerships, emphasizing the importance of collaboration within the Cardano ecosystem.
  • :clipboard: Feedback Mechanisms: The introduction of various forms for collecting feedback and tracking progress was discussed to streamline communication.

Key Insights

  • :bar_chart: Importance of Structure: Establishing a structured agenda is crucial for facilitating productive discussions and ensuring that all relevant topics are covered. This helps members stay focused and accountable for their contributions.

  • :couple: Volunteer Engagement: By encouraging members to take ownership of specific workstreams, the group fosters a sense of commitment and accountability. This approach not only enhances individual involvement but also promotes collaborative efforts toward common goals.

  • :date: Regular Updates as a Best Practice: Implementing a system for weekly updates allows the team to keep track of progress and challenges faced in each workstream. This practice ensures that all members are aligned and can provide support where needed.

  • :globe_with_meridians: Enhancing Community Involvement: Actively engaging the broader community is essential for the success of the group’s initiatives. This includes sharing updates through social media and other channels to generate interest and involvement from outside contributors.

  • :chart_with_upwards_trend: Focus on Long-Term Goals: The discussions around creating a mission statement and identifying strategic partnerships indicate a long-term vision for the group. This focus can help guide decision-making and prioritization of tasks in the future.

  • :handshake: Building Partnerships: Exploring partnerships within the Cardano ecosystem can provide valuable resources and support for the group’s initiatives. Identifying key players and potential collaborators is an important step in expanding the group’s influence and impact.

  • :memo: Feedback and Communication Tools: The introduction of various feedback forms and documentation strategies can streamline communication and ensure that all members’ voices are heard. This system can help capture insights and suggestions that can drive project improvement.

Overall, the meeting served as a foundational step in establishing a more organized and productive approach to the group’s work, emphasizing collaboration, accountability, and community engagement in their efforts to build and enhance the Cardano ecosystem.

1 Like
8

DRep Collective Meeting #6 Notes:

Summary

The DREP Collective Meeting Number Six, moderated by Matthew Capps, covered workstream updates (including funding needs), Dagwell’s progress on metadata standards (needing community awareness), and partnership exploration (with Intersect, XSPO, and at the Hawaiian Blockchain Summit). Ben O’Hanlon, Kevin Mohr, Dominick Garey, Derrick Oatway, and Ratio presented updates on ecosystem mapping, GitHub workflow improvements, and website/smart contract development, highlighting the need for refined metadata and clearer self-reporting processes. Next steps include securing funding, improving metadata standards awareness, and finalizing partnership proposals.

Details

Meeting Logistics and Introductions: The meeting, DREP Collective Meeting Number Six (00:04:20), experienced initial technical difficulties with participant Ben O’Hanlon’s connection (00:01:13), but they eventually joined. New attendees, including Glafkos Mitsidis, introduced themselves (00:04:20). Matthew Capps became the meeting moderator (00:08:44).

Workstream Updates & Coordination: Kevin Mohr provided a summary of the previous meeting’s highlights, which included identifying leads and contributors for each workstream and reviewing website progress (00:04:20). They also reported on their coordination tasks, including moderation setup across different platforms, minute consolidation on GitHub, and plans for promotional campaigns and ecosystem mapping (00:08:44). Funding was identified as a crucial next step, particularly for development work (00:09:48).

Dagwell (Metadata Standards) Update: Dominick Garey, representing Dagwell, shared their progress on metadata standards, explaining that the process of registering with Puro for carbon credit distribution highlighted the need for improved metadata organization (00:10:54). They described reaching a feedback stage for their proposed standard. Ben O’Hanlon suggested a workstream to raise awareness of this work within the wider community (00:11:56).

Partnerships: Matthew Capps discussed partnerships, noting the need to identify existing partnerships and explore new ones. They mentioned Intersect as a potential partner, emphasizing the need for a proposal outlining the project’s value proposition and timeline (00:13:16). The discussion also included potential partnerships with XSPO, DAO builders, and involvement in the Hawaiian Blockchain Summit to reach Japanese DREPs (00:18:10). Dominick Garey suggested leveraging Cardano’s governance structures to pursue partnerships wherever Cardano communities meet (00:21:11).

Ecosystem Mapping: Ben O’Hanlon, head of ecosystem mapping (00:22:03), outlined their approach, focusing on creating a brief to attract creatives and addressing the need for clarity regarding potential funding and commitments (00:22:57). They highlighted the importance of managing expectations around potential future funding (00:27:29).

GitHub Development and Workflow: Ratio presented a detailed overview of the DREP Collective’s GitHub account, showcasing three forms (onboarding, workstream report, and developer feedback) designed to streamline communication and workflow (00:32:11) (00:38:45). They also presented the team structure, issue tracking system, and project board within the GitHub account to manage work streams (00:39:36).

Alpine and Dagwell (Website & Smart Contracts) Update: Derrick Oatway (Alpine) demonstrated the progress on the ecosystem map, highlighting the use of self-reported metadata and extended fields as defined in SIP 119 (00:43:11). They stressed the need to refine the metadata and the self-reporting process (00:44:27). Dominick Garey explained their work on the backend, emphasizing the ability to update metadata dynamically and the integration with smart contracts (00:46:43). They presented a proof of concept demonstrating the minting, updating, and querying of metadata using the smart contract (00:50:30). A key discussion point was determining the necessary extended fields and the level of hand-holding needed for self-reporting (00:44:27) (00:51:20). They also confirmed that future plans include adding real-time gallery functionality and improved wallet integration (00:49:31).

Suggested next steps

Ben O’Hanlon will scope out a brief to share with creators regarding ecosystem mapping, addressing the questions of ‘why this, why me, why you, why now’.

Matthew Capps will identify existing partnerships and check with each workstream owner about partnership needs, noting existing partnerships like Intersect, XSPO, DAO builders, and the Hawaiian Blockchain Summit.

The group will focus attention on using GitHub for communication and collaboration, creating accounts if needed.

The group will provide feedback on the current work regarding metadata standards, specifically focusing on extended fields, the self-reporting form, and how much handholding is needed for the self-reporting process.