No wallet found. Please install a Wallet extension or check permission settings.
If you don't have a wallet, we recommend one of these:
To assign weights to modules, you need to stake on our validator. Click here to get started.
The value proposition of the module to Commune must be clear, transparent, and verifiable. This module provides various utilities to the Commune AI and Commune Dev Discord server, including translation, audio, GPT Assistants API, APItools (GET, POST, etc), vector memory/retrieval for relevant documentation, and more. It's configured from a list of more than 800 official and third-party 'cogs' (feature sets). Funds will be used to pay for bot hosting and upgrades, as well as organize community events and application development in partnership with The Arena Online (https://arena.x-ware.online).
Every s0 module needs a visual representation, such as a website or a GitHub repository, that explains it in detail and collects all relevant sources. Interested parties can ping @Red in the Commune AI discord server to chat now. The baseline code for the application can be found at https://github.com/Cog-Creators/Red-DiscordBot, and the list of configured features is available in a Google Doc. For missing features or to develop an open-source Redbot Cog for a specific application, users should ping @yikesawjeez in Discord to add it to the to-find/to-make list.
If the module is an endpoint, it needs to be functional and work as claimed. In this case, the Discord Bot should respond to @Red pings and !help commands.
The module owner needs to be active on the Commune AI discord, telegram, or twitter (optimally all) to represent the module and answer questions. For this module, the owner is @yikesawjeez.
If the module represents the funding of an in-development project or bounty, there should be a clear milestone-based public plan that sets expectations for its progress. A 'placeholder' document has been created for any additional applications or development plans regarding the bot or under the umbrella of this module.
For modules representing the funding of an in-development project or bounty, there needs to be a progress update at least every 3 days and show transparency on the use of funds. If this module is associated with an in-active-development product or feature, it will be reviewed at the Build and Stake, and notes will be left in the provided Google Doc.