🛣️

Rep3.gg Meeting 3/15/23

The conversation is about an onboarding program using cake rewards to earn NFTs. Participants start as fighter level zero and complete tasks to earn cake points and move up levels, becoming fatter fighters until they reach sumo level fat and get an NFT. The first level is open to anyone who completes the onboarding tasks, but subsequent levels require completing bounties for the dow. There is discussion of badges and governance, with suspended status for inactive participants. The tool used for tracking bounties is Dwork, but there are limitations that may require manual effort or automation.

The conversation is about building a credentialing platform with a main membership badge and multiple tiers of badges for participation, contribution, appreciation, holding tokens, etc. The badges are sole bound tokens and have an on-chain association that allows for the creation of rules for each tier to automate the process. The badges can be customized with different designs and animations based on activities such as staking or governance votes. The conversation also touches upon using Lego-style graphics for the badges and creating different NFTs as child NFDS under one parent membership badge.

The conversation is about a tool for creating and managing badges for community members. The tool allows for manual badge distribution or integration with Discord roles to automate the process. There are different approaches to using the tool, including relying on activity points from an external platform like Dwork or creating separate bounty badges within Reptory itself. The main membership tier can be upgraded or downgraded based on these badges. Technical difficulties with Metamask were encountered during the demonstration of the tool.
The conversation is about different approaches to automating the process of awarding badges for completing bounties in a community. The first two methods are manual and do not require much effort, while the third method involves integrating with Dwork's API and has associated costs. There is discussion about whether people who get paid for completing bounties should also receive cake points, and uncertainty about whether Dwork's API is open or closed. Ultimately, they need to decide on a strategy that balances automation with workload and cost considerations.

The conversation is about making decisions and sharing a screenshot. They discuss accessing a site called Fight Club and the different roles available, including the fighter role which gives access to other channels. They also talk about creating badges for community participation, upgrading/downgrading levels, and using Snapshot for governance integration. The idea of incentivizing people with bounties or rewards for attending meetings or completing tasks in an education program is brought up, along with the possibility of creating a credentialing system that captures all aspects of community involvement.

The conversation is about an onboarding program using cake rewards to earn NFTs. Participants start as fighter level zero and complete tasks to earn cake points and move up levels, becoming fatter fighters until they reach sumo level fat and get an NFT. The first level is open to anyone who completes the onboarding tasks, but subsequent levels require completing bounties for the dow. There is discussion of badges and governance, with suspended status for inactive participants. The tool used for tracking bounties is Dwork, but there are limitations that may require manual effort or automation.

The conversation is about building a credentialing platform with a main membership badge and multiple tiers of badges for participation, contribution, appreciation, holding tokens, etc. The badges are sole bound tokens and have an on-chain association that allows for the creation of rules for each tier to automate the process. The badges can be customized with different designs and animations based on activities such as staking or governance votes. The conversation also touches upon using Lego-style graphics for the badges and creating different NFTs as child NFDS under one parent membership badge.

The conversation is about a tool for creating and managing badges for community members. The tool allows for manual badge distribution or integration with Discord roles to automate the process. There are different approaches to using the tool, including relying on activity points from an external platform like Dwork or creating separate bounty badges within Reptory itself. The main membership tier can be upgraded or downgraded based on these badges. Technical difficulties with Metamask were encountered during the demonstration of the tool.
The conversation is about different approaches to automating the process of awarding badges for completing bounties in a community. The first two methods are manual and do not require much effort, while the third method involves integrating with Dwork's API and has associated costs. There is discussion about whether people who get paid for completing bounties should also receive cake points, and uncertainty about whether Dwork's API is open or closed. Ultimately, they need to decide on a strategy that balances automation with workload and cost considerations.

The conversation is about making decisions and sharing a screenshot. They discuss accessing a site called Fight Club and the different roles available, including the fighter role which gives access to other channels. They also talk about creating badges for community participation, upgrading/downgrading levels, and using Snapshot for governance integration. The idea of incentivizing people with bounties or rewards for attending meetings or completing tasks in an education program is brought up, along with the possibility of creating a credentialing system that captures all aspects of community involvement.