A microblogging + DAO platform. Topics or Communities are individual DAOs, each with their own treasury and some limited governance mechanisms. Membership fees are determined by each community; users can join as few or as many as they wish.
MicroDAO was tested on Polygon Mumbai, but can likely be run on any EVM.
- All DAOs use the network token as currency.
- Voting is free for DAO members, but restricted to one vote per member (address).
- Registration is halted while a proposal is active.
npm installnpm run start(launches atlocalhost:3000)- Open up MetaMask and make sure the Polygon Mumbai testnet is selected.
- Look here for a quick way to add it to MetaMask
- Connect your wallet.
There is only one DAO right now, but you can create as many as you like.
Take a look at Available Scripts for additional CLI commands.
This project includes some helpful bits, including
- A self-contained state instance. You can subscribe to it like any other state.
- A
connectbutton that will automatically trigger a wallet connection.
Default network is Algorand, but if yourstdlibinstance is usingETH, it will trigger MetaMask. - A light API for interacting with your
@reach/stdlibinstance.
- ReactJS with Typescript support: A popular front-end framework for building web applications
- Reach Language: A compiled language for building multi-chain smart contracts. This template includes the JS dependency, and not the CLI.
- Cryptocurrency Icons as well as a single-file API (and ReactJS component) for using them
- Google's Material Icons for quick UI sugar
- SASS (no pre-defined style libraries: you can
npm installany additional dependencies.) - Typescript
- 🦆 raphsducks: an unopinonated state manager.
- 🦆 reachduck: a simple API for interacting with the blockchain and/or a reach
stdlibinstance
Reach allows the creation of multi-chain smart contracts with a single language, which compiles down to JS and the native code for each chain. Learn more here.
In the project directory, you can run:
Runs the app in the development mode at http://localhost:3000.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation. Some other helpful topics: