Temperature Check: Building a Talent Hub for Cosmos

Context: It’s widely recognized in the Cosmos Ecosystem that there are certain coordination challenges. These are inherently linked to the decentralized nature of the system, which is a feature, not a flaw. However, these issues should be addressed to alleviate the problems they create, potentially hindering adoption. One such challenge concerns the absence of a centralized entity to effectively guide and unite talent within the ecosystem. Analysis: To further analyse the situation, we also found that there was an enormous reliance on trust assumptions regarding credibility of actors. More often than not, subjective judgement prevails instead of quantitative and qualitative analysis. If left unaddressed, this issue will result in ‘cartelization’ and reputation systems that prioritize connections over merit-based and accountable approaches as the system scales. Secondly, we have identified an overemphasis on development , which unintentionally discourages the involvement of other skill sets, such as marketing, business development, and traditional finance. We have also observed a significant growth in the developer cohort, leading to increased specialization. To prevent…

Excerpt (1195 of 13474 characters). Read the whole post on the forum ↗

I like the concept !

What would be the main challenge to implement it and is there any downside in your opinion?

Also, do we have a way to quantify or “show” what’s the current/potential demand in terms or applicants, jobs offering… etc within the AEZ ? Showing data could help to decide.

I like the neutral and non profitable aspect of this proposal. Just a tool, not another punzi. Looking forward to the discussion

Thank you Govmos for you dedication to the Cosmos community

We think the ecosystem as whole should approach this topic as a necessary public-good funding. The key argument we shared relates to the fact that there will be an inevitable bottleneck in the future if this situation is not addressed preemptively. We are currently relying on foundations and DAOs which won’t be able to follow the demand as it scales. Moreover, creating a decentralized platform to take over the charge will require extensive work to be designed, specified, built, tested, and lastly implemented. Due to the public nature of the business and its relatively low profit margin to operate correctly, we identified this as a perfect match for a joint funding from the two sources currently operating this human ressource coordination, namely the AADAO and the ICF. Govmos: To present a detailed plan for the project, we suggest proceeding in a series of sequential steps: • Community debate • Specifications • Funding • Tokenomics • Building • Infrastructure deployment As we previously described, building public infrastructure takes time, more than building in a centralized manner. This is why we think it is important to kickstart the first steps…

Excerpt (1195 of 2050 characters). Read the whole post on the forum ↗

Bringing a talent portal onchain is definitely an interesting usecase. Onchain attestations could solve some of the assumptions and trust involved with recruitment today - but I’m still unsure how we can utilize this for qualitative evaluations/data.

Regardless, agree with @Govmos that such a project will probably (esp at this stage) be a public goods type project. We will probably need a few trailblazers to innovate, experiment and then quash traditional recruitment portals.

If any team is looking to build on this idea, do give us at @ATOMAcceleratorDAO a shout!

Syed: Onchain attestations could solve some of the assumptions and trust involved with recruitment today - but I’m still unsure how we can utilize this for qualitative evaluations/data. This is indeed the tricky part to understand so you are correct to point it out, this clearly requires deeper explanations. Let us review step by step to answer your question properly: • The main challenge in the design is to maintain privacy of user’s whilst bringing authentication to the data. The best solution we could find was to hold the database in a classic web2 server with access limited to active validators while the frontend is open-sourced. This is how we achieve the trust-minimization privacy preserving while having a decentralized execution made by a cohort of validators which risk severe reputation backlash if they ever break the privacy commitment. Moreover we clearly imagined a system where social consensus will slash via the Hub governance if someone ever does this. • Once we have that private database, its important to understand how the data flows. On this server, the data is processed by the open-sourced frontend, therefore only the users with credentials are…

Excerpt (1197 of 3993 characters). Read the whole post on the forum ↗

Welcome to apply for the QF grant that is dedicated to support teams and public infra like yourself!
You could find on DoraHacks website, or feel free to reach out to me on TG: chris_dora
would love to learn more about it.

This looks to be directionally similar to this Talent Hub I think:

Web3's Trusted Hiring Platform For Tech Professionals

Calyptus is Web3's leading employment platform helping tech professionals land a job 3x faster. Start your onchain resume and fast-track your career in crypto today.

The UX design of this system shares many similarities with a typical web2 app, but with the addition of on-chain credential attestations. Our system, however, utilized a web2 backend with a fully open-sourced front-end and on-chain execution, multiple validators verifying the authenticity of web2 data for block committing. We also considered a fully web3 approach for users who decline optional privacy features. Although our vision differs in the backend, the timing may not be optimal to compete. Let’s revisit this in a few months and observe Calyptus’s progress. Thank you for the feedback, it was valuable and insightful.

Not exactly the same, but check out this project that came through on the Cosmos Hub Nigeria accelerator run by @ATOMAcceleratorDAO
https://dorahacks.io/buidl/24504

This project aligns well with several key objectives outlined in our initial vision for this initiative. We are encouraged by its direction and fully support the incubation and successful implementation of such projects within the ecosystem

This is the kind of framework that is necessary to facilitate some of the other kinds of businesses I’ve previously outlined in an ecosystem managed kind of way. I’m of the opinion that projects that generate positive cash flow that is funneled back into the ecosystem, and that serve as a marketing/community relations tool - is a net positive multiplier for the ecosystem. What is the general consensus in investing in businesses other than online blockchain apps? I think there is a huge opportunity to build DAO businesses that are more in the manual labor / robotic and automation sectors with a management structure. • Window Cleaning • Car Wash • Real Estate Development • Farming And the kinds of collabs that can be done with chains like Regen and other businesses in this sector. There is business development work and overhead associated, salaries for management team ect… with this strategy, but profit sharing and experimenting with this strategy would be an interesting social experiment. What are your thoughts on using these kinds services as a community relations marketing approach? This could even be a strategy that enguaged validator teams could help out in…

Excerpt (1198 of 1409 characters). Read the whole post on the forum ↗

A Cosmos Cosm-Wasm app for managing projects? cosmwasm-projectmanagement/ ├── Cargo.toml # Project dependencies and metadata ├── examples/ │ └── schema.rs # Generates JSON schema for messages ├── src/ │ ├── contract.rs # Main contract logic (instantiate, execute, query) │ ├── error.rs # Custom contract error types │ ├── msg.rs # Message definitions (Instantiate, Execute, Query, Hook) │ ├── state.rs # State definitions (storage items, structs) │ ├── execute.rs # (Optional) Break down execute logic handlers │ ├── query.rs # (Optional) Break down query logic handlers │ ├── lib.rs # Crate root │ └── event.rs # (Optional) Event definitions Serious about putting this kind of plan into action? Okay, let’s brainstorm the features needed for a project management application built using CosmWasm smart contracts. Here’s a breakdown of potential features, categorized for clarity: I. Core Project & Task Management (On-Chain Logic) • Project Creation: • Define project name, description, goals. • Assign a project owner/administrator (wallet address - `Addr`). • Optionally link to a project-specific token or treasury. • Store project metadata (potentially…

Excerpt (1192 of 6898 characters). Read the whole post on the forum ↗

VII. What?

‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎

Updating a kernel requires the chain to be stopped, or it used to at least, building an app to handle some of the same functionality with smart contracts creates a poduct on the hub where there is a fully operational ecosystem that can be enguaed internationally - and updates to the core fucntionality are non-consequential. That’s the logic, anyhow. The management of services that generate net positvie cash flow, being bootstrapped by the community pool - is an idea I’ve thought is worth serious consideration. The goal is for those funds to feed back into the ecosystem, perhaps - enguage new participants in the ecosystem by introducing and/or encouraging the “buillt in” payment rail for those services, and having branded laborer’s servicing those job funcitons. Something else to consider - if a validator can multi-task, manage a small team performing some service, and he makes addional income from this service, they might be less likely to dump the tokens - AND there would be that additonal network value introducded into to the ecosystem. There is a community of people here - how enguaged do “we” want to be in our network effects? Some concepts I’ve been broaching for some…

Excerpt (1197 of 1775 characters). Read the whole post on the forum ↗

This architectural proposal is well thought out. Any team interested in developing this framework could consider integrating a modest developer fee into the execution of some—or all—of the on-chain contracts. This would allow for the initial development costs to be gradually covered over time. In our view, this would represent a net positive and contribute to the creation of a truly valuable product. jasonsprouse: User Experience (UX): Interacting directly with smart contracts via wallets can be cumbersome. A good front-end UI is crucial to abstract away blockchain complexities for non-technical users. We also agree that the frontend suggestion is highly relevant. However, we believe it should be considered as a follow-up phase, given the significant workload required to ensure proper integration with all underlying contract interactions. Conclusion: At Govmos, we fully support the creation of this Talent Hub . The breakdown of features proposed by @jasonsprouse aligns perfectly with our own vision. Should he—or any other community member—be interested in building the actual contract architecture, we would be more than happy to support the effort in any way…

Excerpt (1198 of 1240 characters). Read the whole post on the forum ↗

I’m for this…it’s in alignment with things I’ve suggested in the past. The variety of work could cover everything from administrative to manual labor. It can be done as an independent chain such as you’ve suggested - with smart contracts or as a smart contracting system on Atom. Govmos: Funding: Due to the public good nature that extends way beyond the Cosmos Hub into the entire Cosmos Ecosystem, this should be a joint-funded program which financial details should be debated between the ICF’s @crainbf and @Youssef from the AADAO. Which ever you think might be better. This is historically how these products come to market…a developer fee in the contract isn’t the practical way to get a product to market. I also want to point out that Ai, although it can expediate the development of solutions…I’ve seen Ai suggest anti-patterns that are severe security risks, for example: storing a private key signature in the browsers local storage. Restricting funding because there is technology that helps productivity ≠ intelligence. BEAWARE, pay close attention and scrutinize anything thoroughly before you think even the best available systems “do the work for you.” I’m…

Excerpt (1195 of 1508 characters). Read the whole post on the forum ↗