Closed ghost closed 6 years ago
Awesome! Seems like there is definitely interest in a way to facilitate/bootstrap working relationships in a district concept. The "HQ" proposal I think has a similar goal though the focus is on design and creative work rather than blockchain. Perhaps there is room for some collaboration and the district could either be multi-purpose for consultancy, or the code simply re-used across districts. 👍
Edit: Also would be really interesting to understand how the reputation mechanism would operate.
Hi! We are absolutely open to collaboration. We have also discussed as a group that the lines between different skillsets are often blurred, for example one of our teammates Jasper is an engineer but also identifies as a designer.
I can certainly see the benefits to working with a common taxonomy of skills or creating ways that districts can interact.
It's also interesting to think about how some districts might do similar things, but do them in a philosophically different way, and that could be okay, or ever desirable.
It's also interesting to think about how some districts might do similar things, but do them in a philosophically different way, and that could be okay, or ever desirable.
I think that this would definitely be the optimal situation, where districts share resources and collaborate on building and improving the district0x infrastructure but compete for attention from the community, leading interesting ideas and innovations.
please send me a direct message on district slack regarding your proposal. @angelo
The ‘Elaborate’ tag has now been added. If you would like to add more detail or development we can reopen. After you have developed your idea more, you will need to reach out to Brady directly on Slack, Telegram, or Reddit to have it reopened.
A closed proposal will only be reopened if a significant amount of effort has been put into developing the idea. A sure fire way to get your proposal reopened is to make mock ups, wireframes or other content that can better conceptualize your idea. Technical details of what tools or processes will also be considered if they are sound and realistic approaches.
Name
Bridge - P2P Blockchain Consultancy
Purpose
Although promising, blockchain technologies - including Ethereum - are still in a somewhat inaccessible stage in what regards the layman. While there are many arguments for why such technologies will make things easier for entrepreneurs, businesses and the general public, at large, people who prioritize affordable and simple solutions to their problems have not yet experienced the benefits of decentralization. On the one hand, this probably happens because most of the "web 3.0 technologies" are in their infancy, with relatively few fully functional protocols being widely used. On the other hand, solution-driven adoption is still difficult, since it involves some learning curves (new environment, possibly new language, etc.) Therefore, development of specific blockchain web solutions for businesses and the general public remains costly. Fortunately, such gaps seem to be bridgeable given the open characteristic of the web 3.0. As new tools are put forward by early developers, a horizon of possibilities is created for good lego builders - d0xINFRA being a good example of this. Thus, theoretically, these people have/will acquire the skills to assist in any blockchain project/solution that any layperson might need. Put both parties in a marketplace with an incentive mechanism and you have Bridge, a Peer-to-Peer Blockchain Consultancy.
Description
Perhaps one of the turning points for web 3.0 adoption will be accessibility in terms of project development - for each web business running on the blockchain, a few more people will be familiar with the benefits of cryptocurrencies, etc. However, for such a thing to happen, the general public must have means through which they can bring their ideas into the blocks - with our without development knowledge. In order to facilitate that, Bridge would seek to connect those with the needs to those with the know-how. This would work through a digital marketplace, where "consultancy seekers" can post their blockchain related projects and/or unsolved problems, and meet a community of "consultants" that can help in bridging their ideas into the blocks. The marketplace would be built upon d0xINFRA, which is already generally understood by this community. Additional changes should be made to accommodate for optimal GUI and communication with Dapps (see below). As with Ethlance, matching would occur based on synergy and rating systems for both sides.
Payment
Forms of payment should be left open for mutual agreement between the parties. Leveraging the flexibility of standard ERC20 tokens, it should be possible for payments to take the form of ownership. That way, if it is in the interest of both parties, a service can be conducted in exchange of ownership over the final product. For that, one possibility is to enable the creation of an Aragon entity whenever a match happens (similarly to the creation of a district). That way, not only would the requested project be developed into the blockchain, but it would also kick off as a DAO. It is also advised the creation of a payment timeline that describes under which conditions (e.g. project development milestones) the specified payment(s) will happen.
Coordination
In order to foster collaboration and successful projects, Bridge could be set up in a way that the information inputted by the "consultancy seekers" can be exported to a Colony entity, where coordination with "consultants" will happen. This would potentially allow for multi-collaboration, where more than one "consultant" can jump in to help.
Challenges
As previous district proposals listed here, Bridge would encounter technical challenges regarding cross-Dapp communication. However, the biggest challenge foreseen is, ironically, user adoption. Bridge seeks to provide a useful way to connect the layman with problems and potential blockchain solutions. However, as with any other bridge connecting two places, its path must be attractive. Otherwise, people might as well take another route or not cross at all. That being said, this district should be designed for the layman. That is, simple, easy to use and effective. And as an aspiring developer, I know these are the greatest challenges a project can ever have.
Author's slack name: @danilo