crypto

yesterday i kickstarted the github page of /weeklyhackathon

the mission is to transform this into a fun competition that creates a flywheel effect between token traders and our community

building open source software that can showcase the power of farcaster as the social fabric of the new internet

https://github.com/weeklyhackathon

what's the best way to decentralize a github repo?

i want that only the holders of a given token can submit requests to change this codebase. how would you do that?

cc @nintynick.eth

Building global interoperable roles @ hatsprotocol.xyz | DAOs are the endgame of crypto

maybe require 2/2 approvals on PRs of which one of the approvals is a bot that will only approve if you're a token holder

this should work great under the following assumptions:

1. Its acceptable to trust the bot / server / host
2. The goal is to token-gate PR *merges* and not PR *submissions*. If you need to gate submissions (eg due to spam concerns), then a different approach would be required. Possibly some kind of github wrapper app that submits PRs on behalf of authorized users.

Cultivating a freer internet 🌱 The community-governed network behind Radicle and Drips. Join the community 🤝 http://discord.gg/radworks

building /hatsprotocol | 
proudly mid-curving it since 1995

the real (longer term) answer is to use @radworks's Radicle, but that would require a more onchain-forward ui/client than what they have currently. maybe @ele has an update on progress there?

a front end for the radicle protocol/network that includes more onchain-native functionality

what do you mean with a more onchain-forward ui/client? 

(this is v exciting)