# About W3A Overview about the Web3 Association
⭐ **Mission** Fixing the incentives with Web3. 🎯 [**Focus**](/about/focus) We think about incentives, governance and economics. We analyse treasuries, funding processes, organisations and money. Our focus is to collaborate with existing teams across Web3 ecosystems and help them with improving their treasuries, funding processes, governance, organisations and money. We create educational resources that provide insightful and actionable information about these systems and how they could be approached. Over time Web3 Association is looking to create the industry preferred destination to learn about Web3 treasuries and funding processes. We actively look to help with starting experiments and collaborations that can generate new learnings that can improve the Web3 industry. 💡 [**Approach**](/about/approach) Our initial contribution outcome focus has been the creation of educational resources about treasury and funding systems. These provide insightful and actionable information about Web3 treasuries that teams can use when improving their own treasury systems. A shared learning approach has been adopted that focuses on increasing the amount of collaboration and shared learnings across the industry. Educational resources have helped to identify promising experiments and learning opportunities which is a large part of our focus moving forward. 🗺️ [**Roadmap**](/about/roadmap) Our current roadmap plan is documented and updated as this changes over time. The other potential areas of focus are also listed to give a better idea of the areas of work that could be suitable in the future. :family: [**Contributors**](/about/contributors) List of the core contributors involved in the Web3 Association initiative with any contribution history logs. 💬 [**Links & contact information**](/about/links-and-contact-information) All of the online profiles for Web3 Association and some contact information # Focus Why the Web3 Association is focused on supporting and improving treasury systems across Web3 ecosystems The main focus for the Web3 Association in the short term has been to help with accelerating the improvement and adoption of Web3 treasury solutions through the creation of educational resources, experiments and open source software. ## **Why focus on treasury systems?** Treasury systems help with the storage, management and distribution of assets owned by a community. Existing governments and institutions as well as many emerging Web3 projects are all examples of communities both large and small that rely on effective treasury systems to manage how funds are collected and distributed to most effectively benefit their communities. Determining how to best manage and distribute treasury funding is difficult. There is a vast range of ways and purposes that community assets could be used to most benefit that community. Making group wide decisions is challenging, each decision of where to distribute funding can each have a number of different trade offs to consider. Web3 ecosystems have an opportunity to improve and expand on the lessons learnt in existing centralised treasury systems used by existing governments, organisations and communities. Treasury systems adopted in Web3 ecosystems have the potential to become more effective at helping communities make impactful and effective decisions on how best to manage treasury assets. Creating effective treasury systems would help provide further evidence on the importance of Web3 ecosystems and how they can be more effective than existing systems. Sensible monetary policies with effective treasury systems will create an increasingly attractive value proposition to entire societies looking for better ways for their countries and larger organisations to be more effectively or responsibly managed. ## **The opportunity to improve treasury systems** Some simple math can helps to highlight the amount of opportunity there is to create impact through contributions that help improve treasury systems across Web3 ecosystems. The total market cap of cryptocurrencies has been increasing over recent years with a combined total market cap reaching values well above $1 trillion. Within that total market cap there are numerous blockchains, layer two solutions and applications that each have their own treasuries being managed to support the continued development and growth of their communities. Both [DeepDAO](https://deepdao.io/organizations) and [DeFiLama](https://defillama.com/treasuries) are useful tools for finding the total value of some of these treasuries across Web3. Even a conservative estimated value from these sources highlight that there is well over $10 billion currently being managed in treasuries across these communities. Considering that these lists are not exhaustive, and do not include all blockchains and decentralized application projects, the actual total will be a fair amount higher. Keeping these total treasury valuations in mind we can then compare how much value would be generated by looking at what funding is distributed annually each year and then considering what the value of improvement would be by improving those treasuries by a certain percentage. Improvements could comprise of time savings in developing or managing treasury systems or improvements in how the funding process is operated to most effectively direct funds to the most impactful initiatives. **Example value of making improvements to treasury systems**
Total treasuries valueAnnual distributionPotential value of any improvements made
$10 billion$100 million (1%)$1 million (1%), $5 million (5%)
$500 million (5%)$5 million (1%), $25 million (5%)
$1 billion (10%)$10 million (1%), $50 million (5%)
$50 billion$500 million (1%)$5 million (1%), $25 million (5%)
$2.5 billion (5%)$25 million (1%), $125 million (5%)
$5 billion (10%)$50 million (1%), $250 million (5%)
$100 billion$1 billion (1%)$10 million (1%), $50 million (5%)
$5 billion (5%)$50 million (1%), $250 million (5%)
$10 billion (10%)$100 million (1%), $500 million (5%)
These simple calculations help highlight the scale of the opportunity in continuously making even small improvements to Web3 ecosystem treasuries. Even a 1% distribution rate for treasuries that have a combined total value of $10 billion produces an opportunity of $1 million in value if improvements can be made that would on average improve the effectiveness of those treasuries by 1%. As the total value of treasuries increase this opportunity for improvement also greatly increases into something very meaningful. These improvements will be paramount for Web3 ecosystems to address due to the scale of the funding being released from different ecosystems as they grow. These treasury systems will need to be able to scale and still operate effectively in these conditions when the treasury value increases over time and more community funds are at stake. Overall, it is clear that even small incremental improvements to treasury systems represent a massive opportunity for Web3 ecosystems. Increasing the accuracy, speed and overall effectiveness of how communities can manage and distribute their treasuries will be vital for these ecosystems to reach their real potential. Treasuries from Web3 ecosystems will increasingly represent the economic beating heart of many emerging communities across the globe. The better that these treasury systems perform the more accurately the community will be able to select quality funding initiatives that produce impactful outcomes. The higher the impact is from any outcomes produced by these treasury systems the more valuable these ecosystems can become. More impact helps result in making a more valuable ecosystem and a more valuable treasury. Put simply, treasuries will be one of the most important flywheel growth levers for accelerating Web3 adoption. # Approach Outlining the approach, contribution outcomes and process that will be adopted to support and improve treasury systems across Web3 ecosystems {% content-ref url="/pages/KAiqbTVQtl63gonDWWos" %} [Shared learning](/about/approach/shared-learning) {% endcontent-ref %} {% content-ref url="/pages/dobMFp99ELapHW8Tgn2n" %} [Contribution outcomes](/about/approach/contribution-outcomes) {% endcontent-ref %} {% content-ref url="/pages/b3yg9nOlFtPBVST7GkAg" %} [Contribution process](/about/approach/contribution-process) {% endcontent-ref %} # Shared learning Exploring how an approach focussed on shared learnings could be effective for supporting and improving treasury systems How can we increase the rate in which treasury systems are improved across Web3 ecosystems so that they create increasingly impactful outcomes that support and grow their ecosystems more effectively? What complementary approaches could be integrated into an existing team's development process to help them iterate and improve their own solutions more quickly? Shared learning across the industry can help with answering these questions and potentially provide an effective path to increasing the adoption of Web3 technology through the adoption of an efficient and effective approach to improve treasury systems. ## Current problems **Time consuming to keep up to date with industry progress** There are many Web3 ecosystems that each have a treasury to manage and disburse. Projects within these ecosystems also usually require their own solutions for managing and disbursing treasury assets. The vast number of ecosystems and projects that are building treasury systems in parallel makes it increasingly difficult for these teams to have enough time to find out what is happening across the industry. Not having easy access to the progress being made in surrounding ecosystems can make it easier to miss insightful learnings and ideas about how to better approach solving important treasury problems. **Difficulty in determining which solutions are working most effectively** Existing treasury solution builders will often have a limited amount of time to look at other treasury solutions across the industry due to the level of effort it would require to understand and properly analyse these alternative systems and approaches whilst also trying to build their own solutions. A meaningful amount of time is often needed to properly analyse the available data and determine the current impact that those treasuries are currently generating to more confidently identify which approaches might be actually effective or not. **Lost learnings from failed or pivoted projects** Treasury systems are complex and require ongoing iteration and improvement. Ideas can often be trialled and then discarded once the outcomes do not produce the desired result. As each ecosystem executes these experiments in parallel it will be easy for those learnings to get lost by not being documented. A lack of available learnings on what approaches haven’t worked for other ecosystems can lead to situations where different ecosystems end up adopting a similar and ineffective approach due to the lack of available evidence that covers the issues these certain approaches may have.
**Isolated learning & duplicated efforts** Without any collaborative and supportive structures in place most treasury teams could end up learning in isolation on how to improve and iterate on their own solutions. A lack of external collaboration decreases the amount of skill and thought diversity that could have helped with more identifying effective solutions for solving different treasury problems. There is not a large incentive for competing ecosystems to collaborate and support other ecosystems. Less collaboration across the industry results in a reduced flow of information and insights between the teams working on similar treasury problems. Development of treasury systems in isolation due to less collaboration can result in efforts being more easily duplicated across multiple ecosystems concerning research, analysis, development and experimentation of new approaches. ## **Shared learning**
A focus on shared learning means increasing the amount of available educational resources available for teams to use when improving and iterating on their own treasury systems. The goal of shared learning is to help maximise collaboration and any learnings made across the industry. This helps increase the rate in which existing treasury systems can be improved and more widely adopted. Educational resources will focus on providing insights and actionable information for each ecosystem so they can more quickly identify ways to improve their treasury system in being able to manage and distribute community assets. Focussing on collaboration and shared learning creates an opportunity to help the wider industry achieve their goals at a faster rate. Our goal is for our educational resources to eventually become the industry preferred location to learn about treasury systems. A group of contributors focussed on shared learning creates the opportunity for a supportive structure for helping existing teams building treasury solutions. Contributors would directly collaborate with and help existing teams through research, analysis and suggestions that focus on improving the knowledge available about treasury systems. The main [contribution outcomes ](/about/approach/contribution-outcomes)of an approach focussing on shared learning is the creation of educational resources for the benefit of ecosystems building treasury solutions. Over the longer term there is also an opportunity to help with the development of open source software and supporting standardisation efforts. **Advantages** * **Faster learning outcomes** - Bringing together research, analysis and data about the range of treasury systems across the industry will help with identifying the different approaches that exist for solving important treasury problems. These efforts can help to speed up the identification of which approaches are working effectively or not which can help the wider industry in improving their own treasury systems at a faster rate. Creating impactful resources means that teams building treasury solutions will be able to better identify which approaches to avoid, which to explore further and which ones to adopt when improving their own solutions. * **More cost effective** - Insightful and actionable information about treasury systems is beneficial for many blockchains and applications across Web3 ecosystems. A shared learning approach can become highly cost effective for these ecosystems as the cost of the contribution efforts can be split between each of the participating ecosystems. The full outcome of any resources created are available for the benefit of the entire industry. The more that the costs for these types of contributions can be shared across many ecosystems the more cost efficient the industry becomes in improving treasury systems. Reducing these costs also means that each ecosystem is then able to direct more funding to other impactful initiatives rather than doing repeated and similar work by themselves in isolation. * **Reduce duplicated & wasted effort** - Each existing team in the industry won’t need to spend the same amount of time doing deep research and analysis if they can support an approach that effectively creates those outcomes for them. Resources that increase the amount of knowledge available about treasury systems will help existing teams building treasury solutions be able to spend time on unsolved problems and avoid common pitfalls and mistakes. Removing the need for teams to conduct as much research and analysis themselves will help to reduce the duplicated and wasted effort that could happen across the industry. * **Inspire new solution approaches** - Resources that cover a wide range of potential ways that a treasury system could be approached can help with inspiring existing teams with finding new and novel ways to approach solving important treasury problems. More experimentation is greatly beneficial to the wider industry as any outcomes can be recorded and shared across different ecosystems when iterating on their own treasury system. * **Increase collaboration** - Contributors that help with creating treasury educational resources for the wider industry would not be competing with any existing teams building solutions. Ecosystems that financially support shared learning efforts can help to align the incentives for increasing the amount of collaboration between as many teams as possible by enabling contributors to help with creating high quality resources that can generate ongoing impact for those ecosystems. The higher the participation becomes for this shared learning approach the faster that teams across the industry can iterate and improve their own solutions. Increasing the diversity of skills, backgrounds, values and cultures involved in the creation of these knowledge resources can help with generating higher quality and more informed outcomes. Feedback from existing teams will also help to provide an effective path for iterating and improving these resources and increasing their overall impact over time. **Potential issues** * **Collaboration time cost** - Existing communities and projects may not have much time to give and receive feedback on different problem areas they are working on. This could make it difficult to create educational resources with the same detail of information. Although this could be an issue it is not a blocker for making quality educational resources. Most data about the outcomes of many treasury systems is publicly available meaning it wouldn't prevent any contributors from being able to identify the approaches being used and what relevant insights and data points exist that can help identify effective solution approaches. ## **Summary** **Complementary and supportive approach** Contributors focussed on shared learning will be able to provide a complimentary and supportive structure to improve the knowledge and resources available around the focus area of treasury systems. Educational resources can be used across all Web3 ecosystems to help with improving their own treasury system. Incentivising shared learning at a foundational level can help better support existing teams who are building and learning about how to improve their own treasury system rather than working in isolation. A small capital allocation from different Web3 ecosystems towards increasing the amount of shared learning and knowledge available presents a large opportunity to increase the speed that Web3 ecosystems can collectively identify and adopt the more effective solutions. Quality knowledge, learnings and open source software that is readily available for usage and integration by existing project teams can help them to iterate more quickly and save time by reducing duplicated and wasted efforts. **Effectively incentivised collaboration** Contributors working under a shared learning approach are highly incentivised to collaborate with as many existing teams as possible to provide value and share learnings across Web3 ecosystems. Contributors supporting efforts to increase the knowledge around a given problem area are not competing with existing teams making treasury systems. Existing projects that benefit from more educational resources are more incentivised to support and collaborate with that ongoing work and provide feedback or request areas of improvement to further benefit the evolution of their own treasury system. **Scalable knowledge and support structure** Many problems faced by different Web3 ecosystems are shared across every ecosystem. An increasingly comprehensive knowledge base helps provide an economically efficient and scalable structure to support existing teams building treasury systems across multiple Web3 ecosystems. Efficiently identifying and sharing learnings and knowledge across different ecosystems means more funding can be saved and directed towards other important problems and experiments in each of those communities. **Supportive structure for open source software and standardisation** A shared learning approach provides a simple process driven way to increase the amount of knowledge available through ongoing research and analysis about treasury systems. As these resources mature there is an opportunity to create further impact for the industry by identifying areas where open source software could be produced and widely adopted due to identifying an effective approach that is being increasingly adopted. If ecosystems begin to converge on similar approaches to solve a certain treasury problem then the opportunity also emerges to consider how those solutions could be standardised. # Contribution outcomes Listing the different outcomes that will be created from contribution efforts along with their advantages to supporting existing treasury system efforts The following contribution outcomes are how the Web3 Association aim to support and improve treasury systems across the industry. Educational resources and experiments will be some of the main contribution outcome over the short and long term. The other potential areas of contribution we could help with in the future include helping with the development of open source software and the any standardisation efforts. ## **Educational resources** The creation and improvement of educational resources is one of the main outcomes to expect from our contribution efforts. Resources will reviewed, iterated and improved on an ongoing basis as new information and insights become available. **Contribution outcomes** Research * **Data, facts & statistics** - Aggregating the data, facts and statistics that exist about treasury systems and breaking them down into the relevant focus areas of concern. * **Solution research** - Identifying the different treasury system solutions that exist and how those solutions approach solving each problem for the different topic areas. * **Aggregated resources** - Bringing together the relevant existing information about different focus areas which will include any relevant research literature and reports, articles, blogs and any other insightful informational resource. Analysis * **Insights & trends** - Analysing all of the data, facts and statistics that exists to identify trends and insights which could provide useful learnings on the current state of different solutions and how they have been changing over time for different metrics. * **Case studies** - Conducting studies to look into treasury systems either at a high level to do overview comparisons or more deep dives that look in detail at certain focus areas and what is happening across the industry. * **Product analysis** - Exploring how different problems could be solved with different technical, product or design choices and what ramifications those approaches may have on improving treasury systems. Analysis can help with identifying what existing approaches are effective and easy to use and where further experimentation could be made. * **Literature review** - Reviewing the existing literature available against the up to date insights and trends to evaluate how current research could be better applied to existing treasury systems. Alternatively this could also result in identifying when more research could be conducted that could be beneficial to treasury systems due to new learnings from recent insights or real world usage. Suggestions * **Experimentation suggestions** - Applying the results of any previous analysis can help with identifying what new approaches could be explored and trialled in treasury systems. Any results from these experiments can be fed back into the iterative loop of conducting further research and analysis to better understand what the most effective solutions were for different treasury related problems. * **Implementation suggestions** - As certain solutions have a growing amount of evidence of their effectiveness suggestions can be made towards how other existing teams could implement those solutions. These suggestions could be data structures, processes, algorithms, open source software or any other technical factor or product consideration. **Key benefits of these outcomes** * **Aggregated source of knowledge** - Bringing this research and analysis together will create an easy to access source of information and knowledge for existing project teams to use and benefit from. * **Shared learnings** - Looking at each existing solution and bringing together the insights, data and adoption information will help with identifying key learnings in each of the ecosystems. These learnings can then be shared with other teams building treasury solutions. * **Identify areas of alignment** - Comparing how each team is approaching their treasury system will help identify when problems are being solved in similar ways across ecosystems. Spotting areas that are converging over time to a more standardised way of solving a certain problem provides an opportunity to widely share this solution approach, help with any open source software that further supports more adoption and also to support any efforts to standardise these effective solutions. * **Identify main problem areas** - Bringing together and analysing the performance of different solutions in different ecosystems will help make it clearer where the main problems are with each system and which problems are having the largest detrimental impact for each community. This understanding will help guide future efforts on how we and other ecosystems can spend more time to better support and improve these treasury system areas. * **Save existing projects time** - Providing an open and easily available collection of resources and knowledge to existing teams creates more opportunity for them to save time in identifying and adopting effective solutions for different parts of their own system. Any time saved can then be spent solving different or more important problems. ## Experiments Increasing the number of experiments happening across the industry can help with speeding up the rate that ecosystems learn about what systems and processes are most effective for their treasury. **Contribution outcomes** * **Experiment facilitation** - Running experiments can be expensive and take a lot of effort to coordinate. One way that the Web3 Association can help many ecosystems is by helping to facilitate some of these experiments so that they are easier and cheaper to operate and learn from. * **Experiment outcome analysis** - Any experimentation outcomes can be documented and analysed to determine whether a given experiment was successful or not and where further improvements or suggested changes could be made. **Key benefits of these outcomes** * **Shared learnings** - Learnings generated from any of the experiments can be documented to help with sharing that information more widely with the industry. * **Exploring promising ideas & approaches** - Research and analysis about treasury systems can help with identifying the most promising approaches for different ecosystems to experiment with. * **Speed up treasury development** - More experiments and shared learnings about the outcomes of those experiments can help with speeding up the rate in which ecosystems are able to identify the more effective approaches that they can adopt for their own treasury. * **Reduce cost of experimentation** - Many ecosystems could experiment with promising approaches to improve their treasury systems. In these scenarios the efforts from the Web3 Association can help to increase the amount of collaboration and reduce the amount of duplicated effort across the industry. ## **Open source software** The [benefits of open source software](https://www.notion.so/o/jOQu4b6VLDxaQsg2rVwG/s/zQLAwDu1M3Ts4d7syiK4/approach/contribution-outcomes/open-source-software-overview) becomes more clear and obvious when reflecting on some of the most popular services and solutions being used today. **Contribution outcomes** * **Technical specifications** - Technical specifications are worth consideration when solutions emerge that effectively solve certain problems. Drafting a technical specification will revolve around defining each part of the system or process and its purpose. These specifications could be used by teams building similar solutions who could then implement any available technical specifications that match what the type of solution they are looking to build. * **Tools & libraries** - Open source tools or libraries can be created to help address common problems and can simplify the development process for teams that build their solutions with them. An example Web3 related software tool could be one that helps to create or read transactions from the blockchain. Common problem patterns that exist across different treasury systems could also benefit from open source tooling that addresses these problems and then can be integrated into different treasury solutions. * **Reference implementations** - As effective solutions emerge for solving different problem areas an open source reference implementation can be made to help new and existing teams in building their own solution by being able to adopt and integrate an open source example. Making reference implementations will be more effective when there is already an increasing alignment around what solutions are truly at solving different problems. The more popular a solution approach is, the larger the opportunity is that a wide range of teams would be interested in adopting an open source project into their own solution. **Key benefits of these outcomes** The [benefits of adopting open source software](/about/approach/contribution-outcomes/open-source-software-overview) are numerous and include factors such as helping increase the development speed of teams, flexibility in how they integrate solutions, removing vendor lock ins and increasing the rate of innovation [amongst many other benefits](/about/approach/contribution-outcomes/open-source-software-overview). ## **Standards** Standards are an important north star goal to help with development and adoption of important areas in Web3 ecosystems. Although this may be an important goal, establishing new standards could be very challenging. Standards require a thorough understanding of a problem area, the identification and development of an effective solution to solve those problems and then sufficient evidence, usually through real world usage and adoption, to demonstrate that a given solution is both suitable and actually becoming a standardised way of solving those problems. **Contribution outcomes** * **Identify suitable areas for standardisation** - Standardising parts of a treasury system will be more achievable when there is either a high effective solution being widely adopted or when existing solutions are converging around a similar approach to solve the same problems. When these scenarios are identified more effort can be directed towards inviting collaborators to consider how a given solution approach could be potentially standardised. * **Support standardisation** - If there is emerging agreement on a way to standardise a solution to a given problem area then one useful area of contribution will be to support that process of bringing together collaborators, research and information to support that standardisation process. Supporting standardisation could mean helping with documentation, technical specifications, defining terminology or bringing together insights and expertise from the different participants in each community. **Key benefits of these outcomes** The [benefits of adopting standards](/about/approach/contribution-outcomes/standards-overview) are numerous such as how they can help increase efficiency, robustness and interoperability of solutions which adopt them. Any of the contribution outcomes that help support the improvement or adoption of any emerging standards can help with achieving these benefits. # Open source software overview Overview of the importance of open source software and the benefits of its usage and integration Open source software is when the source code is made available to the public, allowing anyone to view, modify, and distribute the software. Open sourcing software can help with the promotion of collaboration and sharing of solutions to different problems. Open source software is typically developed by a community of developers who work together to improve the software and make it available for free. This approach encourages innovation and allows developers to build upon existing software without having to start from scratch. Examples of open source software include the Linux operating system, the Apache web server, and the Firefox web browser. ### **Benefits of open source software** **Development speed** Open source software can be developed more quickly when it is open to a large community of developers that benefit from using the software. Anyone can suggest changes to help resolve any issues or bugs that are identified. Internationalisation and localisation efforts also will help with increasing the speed of usage and adoption of using that software by an increased ease of understanding for people that have different native languages. **Code quality & security** The quality and security of open source software can be improved at a faster rate when more developers are using and testing the software for their own use cases. People who adopt the open source software can inspect the code themselves and discover potential improvements or issues from their own usage that can translate to suggested improvements. Another factor that helps with security is that open source software can be deployed in whatever manner is most suitable to the project using it. This flexibility provides projects more control over the privacy of where the software is run and any data is stored rather than relying on a third party and their own proprietary software. **Transparency** Open source software is openly available for others to view, alter and use themselves. This approach increases the transparency to those considering adopting it who can have more confident that they understand how it works and how it can be used. **Cost effective** Open software is often free to use with licenses that allow projects to freely adapt, reuse and commercialise solutions that adopt the software. This makes open source software highly cost effective to adopt in any software project. **Flexible** Open source software is often compared to proprietary software, which is developed by a single company and kept confidential. While proprietary software can be more polished and feature-rich, open source software is generally more flexible and customisable, making it ideal for developers who want to build their own software solutions or contribute to existing projects. Open source software can be customised to fit the unique needs of an organisation or individual, allowing for greater control over how the software operates. **No vendor lock in** Open source software means there is no vendor lock when adopting the software. This gives development teams the freedom to change the code or change to another solutions as they see fit. Open source software also helps with mitigating the risks of proprietary software services changing the policies, rules or availability of the software their own projects could rely on. **Interoperable & portable** Open source software allows anyone to suggest and implement integrations with other existing open source software helping to make the software easier to use in other contexts and use cases. Efforts can also be more freely made towards increasing compatibility with older hardware or software and this work be integrated and patched into the open source software to make it easier to use in a wider range of operating systems, projects and different environments. **Innovation** Open source software helps to promote more collaboration between projects that adopt the software as everyone benefits from the continuous improvement and maintenance of that software they each rely on. This helps to encourage further development and innovation around the software by the efforts made to improve and build on top of the existing code. **Longevity** Longevity of an open source software project can be more easily increased as the development and improvements can continue beyond the original developers who initially contributed to the source code. More adoption of the software will further help with the longevity of the software through a larger community which benefits and depends on that open source software being continuously maintained and improved. **Education and training** The amount of education, training and resources that are made available to help with the usage and adoption of open source software can easily increase as the adoption of the software increases and the more people there are that would benefit from quality resources. Wider adoption should also increase the number of people who are well informed on how to use the software and its benefits. A larger community would become a more effective support structure for the education and training needed to effectively use the software. ### **Other factors to consider** **1. Ongoing maintenance effort** For standards that get widely adopted it becomes increasingly important to consider the implications of how that standard is maintained and updated when necessary. Usually these changes can be achieved through new versions. However high adoption of a particular version can also mean a high cost to migrating to newer versions of a standard when they get introduced. If a standard becomes complex to maintain and update then the standard could even become the bottleneck for further innovation. Due to this consideration will be needed on how standards are versioned, reviewed and updated. Checks and balances will be needed to determine how a standard is updated to a newer version and based on what factors, evidence and community feedback. Backwards compatibility will be a constant concern for standards that evolve over time. Some standards will have data that could be stored on an immutable blockchain. Considerations will be needed towards how those services are able to be updated and improved over time based on improved standards. ### Examples of **well known or widely adopted open source software** **Linux** [Linux](https://en.wikipedia.org/wiki/Linux) is an open source operating system that is widely used in desktop computers, mobiles and backend servers. Linux currently has over a [2% marketshare for usage on desktop computers](https://gs.statcounter.com/os-market-share/desktop/worldwide) and the Linux Kernel has been used to build other open source software such as the Android mobile operating system. [Linux Kernel source code](https://www.kernel.org/). **Android** [Android](https://www.android.com/) is a mobile operating system that builds on top of Linux Kernel. Android is one of the most widely adopted mobile operating systems in the world with over [70% of the mobile OS market using Android](https://gs.statcounter.com/os-market-share/mobile/worldwide). [Android source code](https://source.android.com/). **WordPress** [WordPress](https://wordpress.org/) is an open source content management system that makes it easier for people to build their own websites. WordPress has over a [40% adoption market share](https://w3techs.com/technologies/overview/content_management) of online websites. [WordPress source code](https://wordpress.org/download/). **Bitcoin** [Bitcoin](https://bitcoin.org) is an open source decentralized blockchain that enables peer to peer payments. Over a [1000 developers have contributed](https://assets-global.website-files.com/614e11536f66309636c98688/63208342664438223226c3de_NYDIG%20-%20Developers%20of%20Bitcoin%202022.pdf) to the Bitcoin Core open source codebase since its inception. [Bitcoin source code](https://github.com/bitcoin/bitcoin). # Standards overview An overview of what standards are and the benefits of adopting them "A standard is an agreed-upon way of doing things. It can be a product specification, a process for producing a good or service, or a process for undertaking any other form of economic activity, such as supplying goods or services." - [Economic benefits of standards, BSI](https://www.bsigroup.com/en-GB/standards/benefits-of-using-standards/research-reports/). Standards are crucial in modern-day life, as many of them are integrated into the products and services we use daily. Various organisations aid in creating, maintaining, and adopting standards on a national or even international scale. One example organisation that assists with internationally adopted standards is the [International Standards Organisation (ISO)](https://www.iso.org/). ### **Benefits of using standards** Standards provide a myriad of benefits to the communities that adopt them. **Efficiency** Standards help create a common framework for processes and systems which enables more uniformity and consistency in the way tasks are performed and how products are produced. This makes it easier to offer educational resources on how to most effectively adopt those standards which saves time and costs for anyone that adopts them. Standards can also help with improving safety by helping to eliminate potential errors which can save time or resources which lead to further efficiency improvements. Projects who adopt standards also benefit from not needing to solve every problem themselves which saves them time by using standards that are already well defined and adopted. Seeing how other projects integrate and use these adopted standards provides another way in which the speed of education and adoption can increase for the projects which are considering adopting a standard. Standards can also often have reference implementations which offer another way to save developers significant time in trialling and integrating standards into their own projects. These factors combine in supporting how standards help to increase the overall efficiency of delivering products and services. **Simplicity** Standards help with providing a common and agreed-upon set of rules and guidelines that ensure interoperability, compatibility, and ease of use across various products and systems. This reduces complexity and confusion by providing a clear and consistent way of doing things, which can make it easier for people to understand, use, and integrate different technologies. As a simple example, a company producing microwave ovens can use electrical plugs that follow existing national adopted standards. Adopting this approach increases the simplicity for the end consumer who receives a product that they are more familiar with how it is used. For companies this simplicity is increased by them being able to simply adopt that standard such as a standard for an electrical plug and then focus more of their efforts on improving their actual product. Combining and using multiple standards within a project can help developers build even more complex applications as more of the foundational aspects of the project may already have solutions which they can use to build on top of to create their own application. **Consistency** Consistency created from adopting standards is beneficial because it reduces confusion, improves reliability, and makes it easier for people to transfer their knowledge and skills from one system to another. Standards improve consistency by helping to establish a common set of rules, specifications, and guidelines that ensure that products, systems, and processes are alike and work in a uniform manner. This leads to greater consistency in how things are done, making it easier for people to understand, use, and integrate different technologies. For software applications this could standardising data structures, storage or coding approaches to find a uniform approach. Consistency in products and services through the adoption of standards results in people being able to learn a small number of standards and apply those skills across any of the different areas or industries which use those standards. Additionally this consistency often leads to improved user experience as people are able to more easily predict how things will behave which reduces frustration and makes it easier to accomplish tasks. Developers who follow a commonly adopted approach are less likely to make mistakes in their own applications as they can rely on highly tested and adopted existing implementations of popular standards. **Interoperable** Providing a consistent set of rules, specifications and guidelines means that products, services and infrastructure can become more interoperable. This is beneficial for systems as they are then better able to share data and resources which helps further eliminate integration complexities. Easier integration between systems and services or having the flexibility to more easily move between them helps with improving the end user experience, the reliability and scalability of these integrated systems and also reduces the risk of incompatibility issues. Standards used across databases and blockchains would help with making it easier for developers to migrate between chains due to common approaches being used in a multiple places which helps applications more easily integrate the right infrastructure suited for each of the use cases. A good example of a standard that is effective for interoperability is Decentralized Identifier (DID) standard which uses a standardised approach to find and retrieve DID documents which has then been implemented on a number of different blockchain ledgers. **Increased competition** Commonly adopted standards help to reduce the cost in delivering certain products and services. The easier they are to deliver the lower the barrier of entry is to offer that product or service. Standards that help increase the ease of delivering products and services will help with increasing the competition between providers. This can then help with driving down prices and increasing innovation. More competition will help with continuously improving the overall user experience due to the heightened need to provide quality products and services in a competitive market. For software projects adopting standards can also allow for people to focus on other areas of their applications and make more specialised feature sets by not needing to worry about problems which are solved by already adopted standards. This increases the speed of development meaning the market can become more fast paced and quickly evolve to meet consumer demand. **Increased robustness** Standards help with defining best practices, processes and guidelines to follow to create reliable and secure systems and processes. Following standards and ensuring each task is correctly executed and tested helps with increasing the overall reliability and security of that system. The more that a standard is adopted the more real life scenarios it could be being used in. Changes can be made to standards that need further refinement and this refinement can help to further increase the robustness of the standard. For standards that are already well refined any increased usage and adoption only further helps demonstrate the robustness of the standard through the services or products which have adopted it and are operating successfully. Consumers can have increased confidence in products and services that utilise standards which are well adopted. Increased adoption of standards also helps with fostering collaboration around the standard on a continued basis. This feedback cycle from real world usage only further helps to refine and improve an existing standard to become a more robust and effective version. Adopting standards also help with increasing robustness for software applications by reducing the amount of code needed in the application to create a solution which reduces the surface area for mistakes that the developers could make if they had to solve that problem and implement a solution by themselves. Well analysed, tested and verified software for a particular standard helps to reduce the chance of errors and flaws being introduced into end user applications that adopt different software libraries that are built on standards. ### Other factors to consider **1. Difficulty in creating a common solution approaches** One of the big reasons that many people are interested in joining the Web3 movement is the diversity of ideas and ways communities are trying to solve different problems. Some markets and problem areas will have a higher amount of diversity than others in the problems that exist and the number of ways those problems can be solved. The more the diversity there is in the potential approaches that can be taken the more difficult it could become to create common standards. There may not be an optimal way to solve a given problem and the trade offs also may not be immediately clear. Plenty of observation, analysis and experimentation will be needed to create standards which are flexible to these scenarios that can handle and respond to the different trade offs. Standards could be have their complexity reduced and instead focus on one particular approach to solving a problem at a time. Multiple standards could be made to cover different approaches to solving a problem rather than trying to condense them into a single approach. Understanding the variations on these standards being created will help with better identifying and sharing any commonalities between the standards and further help reduce duplication where possible. **2. Ongoing maintenance effort** For standards that get widely adopted it becomes increasingly important to consider the implications of how that standard is maintained and updated. Usually these changes can be achieved through new versions. However high adoption of a particular version can also create a higher cost for migrating to newer versions of a standard. If a standard becomes complex to maintain and update then the standard could even become the bottleneck for further innovation. Due to this consideration will be needed on how standards are versioned, reviewed and updated. Checks and balances will be needed to determine how a standard is updated to newer versions and based on what factors, evidence and community feedback. Backwards compatibility will be a constant concern for standards which get more adopted over time. Some standards will have data that could be stored on an immutable blockchain. Considerations will be needed towards how those services are able to be updated and improved over time based on new or changing standards. **3. Importance of open source software** Open source software is an important part of implementing and integrating digital standards into infrastructure and real world applications. Infrastructure and utility libraries can save developers countless hours if they are able to access reference implementations of a standards based solution. Adopting open source software helps with providing increasing levels of security as the software continuously goes through usage and review from other communities that integrate the software. The flexibility and transparency of this software can help to speed up the development of new standards. For instance, if a group of people were working on a standard to help handle and distribute community treasuries then this standard could benefit from integrating existing standards on escrow contracts, invoices or date and time standards like the [ISO 8601 date and format standard](https://www.iso.org/iso-8601-date-and-time-format.html). Developers can then utilise libraries that implement these standards in existing libraries and use them to increase the simplicity and quality of their own implementations of newer standard. The effective adoption and integration of open source software into emerging standards helps create increasingly robust and interoperable applications and services. ### Examples of widely adopted **standards** Hundreds of standards have been adopted globally that have provided significant benefit to how society functions and how we collectively can deliver better products and services. **TCP/IP network protocols** The Internet Protocol (IP) is an address system of the internet. The TCP protocol can be thought of as the puzzle assembler that puts the pieces together in the right order and asks for any missing pieces to be resent. It is due to the international adoption of both TCP and IP networking protocol standards that the internet functions as it does today. TCP & IP are widely known and globally adopted open standards. The most widely adopted internet services rely on these protocols for their own products to function and provide value to the end user. The amount of value these protocols have delivered to people globally through their adoption that anyone can use is unprecedented. It is protocols like these that showcase the potential impact of creating quality standards for important global problems. **ISO 8601 Date and time standard** The [ISO 8601 standard](https://www.iso.org/iso-8601-date-and-time-format.html) is a widely adopted standard that helps with formatting and storing dates. This standard is often integrated into databases and software libraries for creating, maintaining and storing dates. Software developers benefit from these standards due to a reduction in complexity by not needing to allocate as much time towards handling dates in their own services due to being able to adopt an existing approach through an existing standard. **AC Power plug and socket standards** There are a number of different [AC power plug and socket standards](https://en.wikipedia.org/wiki/AC_power_plugs_and_sockets) used across the world. Conforming to a relatively small number of standards helps make it simpler for electronic manufacturers to provide solutions for each country. Some of these standards can be considered more effective than others and it is this reason that spending time on standards is so important. Once certain standards are well adopted it becomes time consuming and potentially costly in resources to change to a new approach. Standardisation of power plugs and sockets has been massively beneficial to simplifying how electronic devices and appliances connect to the electrical grid and can be used safely by the end user. # Contribution process Outlining the process that will be used to generate our intended contribution outcomes The following contribution process outlines the main steps involved for creating the contribution outcomes of educational resources, experiments, open source software and standards. Each step in this process can be started and repeatedly revisited over time as more data and insights emerge. For this contribution process to be truly effective it will also need to have the [right environment](/about/approach/contribution-process/creating-the-right-environment) such as one that helps to increase impact alignment, collaboration and participation diversity.
## **Educational resources (Ongoing priority)** The usefulness of any insights generated by the educational resources created will have a large influence on how much impact the Web3 Association is able to generate when supporting and improving treasury systems. Any educational resources that we create will be revisited on an ongoing basis as new insights, data and feedback emerge. Educational resources are an important contribution for making insightful and actionable information about improving treasury systems. The long term goal will be to create the industry preferred location for resources regarding treasury systems. **1. Identify focus area** Initial contribution outcomes made towards supporting and improving treasury systems will be achieved by selecting one focus area at a time and then starting the iterative process of inviting collaboration, conducting research and analysis and making suggestions. Contributors supporting this shared learning approach will collaborate with teams building treasury systems to identify which areas are the most important to work on in the short term. Some example areas could be defining the types of funding initiatives that can exist with what data is needed for different proposals types, how they could be assessed prior to funding them and also how they can be tracked or measured once funded. Selecting smaller areas of focus will help with speeding up the process of going through the iterative loop of creating educational resources, getting feedback and then repeating the process to keep improving those resources. **2. Invite collaborators** Once a small area of contribution is selected the next step will be to invite collaborators from any teams building treasury solutions. These collaborators could come from existing business and organisations as well as emerging Web3 ecosystems. Invitations for collaboration will include a request for feedback on what areas they believe should be prioritised in the short term and then also some information regarding how these contribution outcomes could benefit their own treasury systems ongoing development. Existing projects will not need to collaborate with the contributors working on these specific areas of work for the contribution outcomes to be generated. Effort should be made to increase the amount of participation wherever possible to help with increasing the diversity of insights and opinion that can be incorporated into the educational resources. **3. Research** After any initial knowledge and insights is gathered from invited collaborators the next step will be to thoroughly research the existing market and collate any available research papers, reports, previous or current implementations and any usage or adoption data into a comprehensive resource. The goal is to find the most useful and insightful information rather than trying to cover every potential source of information. Research should try to cover what is actually happening across the industry or what has previously happened around different solution approaches that existed to solve certain problem areas. After an initial round of research is completed the resource can be shared for feedback to identify if any noteworthy information is missing. **4. Analyse** Analysis can be started once there is a sufficient amount of research around the contribution focus area. Analysis will help with identifying and exploring the problems that exist, where problems have been effectively solved and what solution approaches have been used, what similarities and differences exist between different implementations, the effectiveness of different implementations that exist or that previously existed, any overall trends on what remaining problems need to be solved and also about the usage and adoption of these solutions. This analysis would be shared to identify any factors that may be missing, what misinterpretations may exist or when any further information could be needed to improve or contradict any findings. **5. Make suggestions** Once the focus area is better understood through research and analysis the next step will be to make any initial suggestions on how relevant problems could be solved using existing or improved solution approaches. Suggested solutions could range from being data structures, processes, specifications to formulas or anything else that helps any teams building their treasury solution. Another aspect of these suggestions should be to help identify areas worth exploration due to a lack of experimentation in certain areas. These situations could create opportunities for identifying better approaches to the currently adopted ones. The end goal of this step in the process is to help foster experimentation wherever needed to better solve any of the problems identified and also to suggest good solutions to a problem when they do exist. Collaboration with existing communities will be a vital part for turning these suggestions into experiments when they are new suggestions. When they are suggestions towards effective solutions then any adoption of those suggestions should yield even further insights that either support or reject the suggestion. Multiple iteration loops of continued research, analysis and more suggestions can be expected before the more effective solutions are identified with any level of confidence. This process will help with creating useful insights on the potential tradeoffs of certain process or technical design decisions and where further improvements could be potentially made in the future. ## Experiments (Ongoing priority) Research and analysis about treasury systems will help with identifying the more promising approaches that are worth experimenting with across Web3 ecosystems. After these potential experiments have been identified further efforts can be made to design and execute experiments that can determine how effective these approaches are for Web3 ecosystem treasuries. **6. Facilitate experiments** Contribution efforts can help with the creation and operation of any treasury experiments that happen across the industry. Proposals, onboarding, support, contribution verification, moderation and sentiment & feedback gathering are some of the areas that the Web3 Association could help with. Regardless of whether the Web3 Association helps with an experiment or not one key area of focus will be the analysis of any experiment outcomes so that any learnings can be documented and shared with the wider industry. ## **Open source software (Medium term)** As more educational resources are created and trends begin to emerge we might identify opportunities to develop open source software that will benefit a wide range of teams building treasury systems. It could be years until more effective solutions are established which would create the opportunity to create an open source reference implementation of that solution. The key consideration to make will be from looking at what existing open source software already exists in different ecosystems and then determining how widespread the impact would actually be for those ecosystems if certain open source software were to be developed. **7. Develop software** Once more effective and widely adopted solutions emerge and a higher level of confidence is achieved that they are in fact effective there is a benefit in considering whether developing open source software could be valuable for the range of different ecosystems and teams who are building treasury solutions. Open source reference implementations of effective solutions could be created that can operate on different Web3 ecosystem blockchains and applications. These reference implementations could then be adapted, used and integrated into any existing projects to benefit their own treasury management or solution development. Making it easy to adopt the most effective solutions to different treasury problem areas would help increase the speed in which teams can built out their own solution and also help provide even more real world usage on a given approach. Openly available tooling and solution software can help increase the iteration speed of teams building solutions and give them more time to focus on the other main problem areas that still exist in their treasury system. ## **Standards (Long term)** Establishing standards has a myriad of benefits for improving the efficiency, robustness and scalability of different protocols and applications. An opportunity to support standardisation efforts can emerge if solutions begin converging increasingly towards a similar approach to solve certain treasury problems. Some areas will be more difficult to standardise than others however supporting any efforts when this is the case will be an effective way to further support and improve existing and emerging treasury systems across different ecosystems. **8. Support standardisation** Effective solutions to each problem relevant to treasury systems should emerge over time. Solutions which are increasingly well tested through real world usage will have increasing evidence of their effectiveness. In these situations effort can then be directed towards identifying whether this solution or groups of similar solutions could be potentially standardised. Collaboration can be encouraged from many participants on what data structures, terminology, technical specifications, documentation and further details would be needed to help an existing solution into a technically documented and openly available standard. There can be many ways to solve different treasury problems, each of which can have different levels of complexity on how to solve them. Different levels of experimentation, iteration and adoption might be needed to effectively address and understand whether a solution is truly effective. Due to this any efforts towards supporting standardisation should be seen as a longer term goal so that treasury systems can further mature and become more widely adopted. # Creating the right environment Potential factors to consider that can help create the right type of environment for a learning based approach to work more effectively **Impact based alignment** Contributors working under a shared learning approach will operate more effectively if they are strongly aligned to create the most impact possible. Incentives will be one area that is important in achieving this by ensuring the incentive is sufficient for the skill sets needed and that the responsibilities of those contributors is directly associated with producing the right outcomes that generate the most impact. A shared learning approach will thrive more effectively with a more collaborative environment. Due to this, part of periodically reflecting on impact based alignment will be determining whether the incentives used are encouraging more collaboration to create impactful outcomes or more competition? Another approach for consideration to help with increasing the amount of impact based alignment could be the introduction of a bonus incentives model to reward contributors who make highly impactful work. The intention here would be to even further incentivise people to identify and contribute towards high value areas of work. Contributors that most effectively help with increasing the rate of learning, collaboration between ecosystems and amount of knowledge and resources made available should be sufficiently compensated and rewarded for doing so. Ongoing consideration will also need to be placed on what financial and non financial incentives are effective in helping promote more impactful outcomes under a shared learning approach. Factors that influence how much impact is generated will have a direct influence on the return on investment for ecosystems supporting a shared learning approach so ongoing iteration and focus on this area will be needed. **Flexible collaborative approach** A collaborative working environment will be a foundational part of effectively executing a shared learning approach that supports and improves multiple solutions across Web3 ecosystems. Considerations will be needed on how contributors communicate, make decisions, conduct governance, allocate tasks and record and share information under this approach. Lessons can be taken from how project management tools are used in existing companies and make any needed adaptations to better fit the differences in working environment. Ongoing reflection will be needed on how to best communicate and collaborate with existing teams based on their own processes. Each team could have different time availability and processes that influence how they want to interact with external contributors and any resources made. It will be the responsibility of the contributors working under a shared learning approach to identify and accommodate for these different working approaches and find ways to most effectively collaborate with these projects to provide as much value as possible in helping them improve and iterate their own solutions. **Iterating the contribution process** The knowledge, source code and standards that actually get created and improved by contributors working under a shared learning approach will determine what impact is generated and whether those outcomes yielded a positive return on investment. Defining and iterating on a process to help to generate these outcomes and make that process more repeatable will be valuable in establishing how a shared learning approach could be adopted for other areas of importance in Web3 ecosystems. The more systematic and efficient the process becomes to support these focus areas the more it will become obvious on how easy it will be for this process to be replicated for another purpose. To achieve this a contribution process has been defined which can be improved over time to articulate the steps being taken to create each defined outcome. The value of any outcomes can be verified and justified through seeing how they help existing projects. Value could come in the form of any gains in efficiency or quality to their solutions that were derived from the resources or from support in generating their own impactful outcomes. More experience in contributing to these different areas along with feedback from projects will help with identifying any blind spots and any weaknesses in the existing contribution process so that it can then be improved over time. **Diversity of participation** Another factor that will help with creating a more effective environment for a shared learning approach to thrive is one that is effective at increasing the diversity of participation involved in the contribution process. Creating higher quality outcomes which are well informed can be more easily achieved through the inclusion of a diversity of data, knowledge and opinions. Increasing the diversity of participation involved in a contribution process can help with creating these outcomes by bringing in a diversity of backgrounds, skills and opinions that influence the work being performed. Creating this type of environment can be achieved by collaborating with as many projects as possible to increase the amount of idea generation and feedback given to improve any knowledge base and resources created. Another area of ongoing focus will be to increase the diversity of participation of the contributors working under the shared learning approach. **Ongoing maintenance & support** Creating research, analysis, suggestions, reference implementations and solutions for important problems in Web3 will require ongoing maintenance and support to keep those resources up to date and relevant. Continuous effort will be needed to identify where existing areas of work need to be further updated and improved so that those resources can continue to be effective for the new and existing projects that use them. Considerations will be needed towards how regularly existing solutions should be reviewed to identify changes in approach taken or other technological advances that could provide further data and insights that improve the existing knowledge or resources available. As the capacity of contributors working under a shared learning approach will be limited a balancing act will emerge of determining when existing work should be revisited for further improvement or reflection. Doing this too early risks limiting the impact that any contributions here will provide compared to other more important areas of focus. Doing it too late increases the risk of the existing knowledge and resources becoming out of date and being less effective at supporting any existing projects. Creating an effective environment for a shared learning approach will be one that can effectively prioritise which new or existing areas of contribution represent the bigger opportunity to generate impact for helping existing projects. # Roadmap Our current roadmap plan with what we're working on and a list of other areas of focus that we might prioritise in the future {% content-ref url="/pages/KYTXM4rezyzs5fwXqAFe" %} [Current roadmap plan](/about/roadmap/current-roadmap-plan) {% endcontent-ref %} {% content-ref url="/pages/k617sPWDYDfqpcgtbsf3" %} [Other areas of focus](/about/roadmap/other-areas-of-focus) {% endcontent-ref %} # Current roadmap plan Our current roadmap with the planned contribution efforts for the coming months The Web3 Association is focussed on providing support to existing teams that are building out their own treasury systems and processes. Two main areas of focus are the facilitation of experiments across the industry and by creating and improving our education resources to better document and share any insightful learnings made whilst researching and analysing what is happening across different ecosystems.
Our main current suggestion for experimentation is the adoption of an open source contributor funding process. You can find out more about that here: * [docs.contributors.org](https://docs.contributors.org/) We’re particularly interested in supporting experiments that are focused on funding contributors in their ecosystems to work on impactful initiatives. Open source contributors is one of those suggested funding processes. Beyond contributor funding processes we are also interested in supporting other forms of treasury experimentation. Reach out to us using any of our contact details if there is anything we can help with.
A number of educational resources have already been created: * [docs.treasuries.io](https://docs.treasuries.io/) * [income.treasuries.io](https://income.treasuries.io/) * [funding.treasuries.io](https://funding.treasuries.io/) * [governance.treasuries.io](https://governance.treasuries.io/) * [docs.contributionism.io](https://docs.contributionism.io/) * [web3economy.io](https://docs.web3economy.io/) * [money.web3economy.io](https://money.web3economy.io/) We intend to continue updating these resources with further improvements and any new learnings as we collaborate with different ecosystems across the industry. Any new learnings will be documented and shared across the industry. # Other areas of focus List of the different potential areas of focus that could help with supporting and improving treasury systems The following are some example areas that are worth ongoing research and analysis to discover new approaches and areas of improvement for any existing solutions being used across Web3 ecosystems. This list is not exhaustive and will be updated over time to include more areas that are worth consideration.
💰 **Income** Exploring the ways an ecosystem's treasury could become sustainable over the long term through different sources of income that can then be used to help address ecosystem priorities and support an ecosystem's operation. * **Income approaches** - A Web3 ecosystems network could receive income from a number of different sources, each of these approaches can be important for helping an ecosystem grow or become sustainable over the long term. * **Taxation approaches** - Looking at the different approaches that could be used for network transaction fees. ⚙️ **Operation** Finding out how a treasury can be operated effectively so that an ecosystem can more easily achieve its longer term mission and goals. * **Processes & Scheduling** - The disbursement process and timeline for funding any initiatives will impact what amount of involvement is needed by different actors at each stage of the process. Things to consider include whether the funding is distributed in rounds or is it a continuous process? Should the different stages of funding disbursement use a mix of round based voting and a continuous voting process? * **Roles & Incentives** - The management of treasuries and any funding disbursement process can include a range of roles to help ensure funds are responsibly and effectively managed and disbursed. The incentives and responsibilities that get applied to each of these roles will impact how well they are performed over a longer period of time and also influence how each participating actor could actually behave. Over a longer time horizon effort could be directed towards exploring where certain areas could be automated and where other areas benefit from more human involvement. * **System & Process Changes** - Treasury systems need to be able to change and adapt with improvements and parameter changes to keep up to date and keep functioning effectively. Common treasury systems parameters will need to be well defined so community members understand their implications and how potential changes could impact the management of the treasury and any funding processes. What thresholds and mechanisms are needed to enact any changes will also need to be considered. * **Mission, Principles & Values** - The mission, principles and values of a community can be documented to better inform internal and external community members what an ecosystem is trying to achieve and what is most valued. Other forms of documentation such as policies and guidelines will also need to be considered. 🎯 **Disbursement** Exploring how an ecosystem can create systems and processes that disburse treasury assets to help with generating impactful outcomes for the ecosystem. * **Disbursement Approaches** - There are numerous ways in which funding could be disbursed to impactful initiatives. Comparing the tradeoffs between different approaches can help with identifying where the most promising areas are for further experimentation. * **Incentive Design** - What incentives are created and how they are attached to the disbursement process will have a profound impact on the behaviours and outcomes that get generated by the systems and processes that are used for disbursement. * **Knowledge Systems** - There is a vast amount of information that is relevant to making well informed decisions. Understanding what information could be useful to the disbursement process will help with making voters more well informed. The easier and quicker it is for voters to get access to quality information the easier it will be to scale a governance process that is looking to increase community participation. * **Prioritisation** - Communities should be able to prioritise where they believe more effort and contribution should be directed towards. This influences how funding could be disbursed and what funding processes a community uses to help with addressing the most important priorities. Community priority setting can help with finding out what consensus exists around which problems and opportunities are the most important for the ecosystem. Prioritisation can also require sufficient debate and discussion around the different problems and opportunities that exist to help with making more well informed prioritisation decisions. * **Funding Initiative Types** - Exploring what types of funding initiatives can exist, what they are useful for and what forms of information is required or beneficial for voting. Example proposal types could include ideas, tasks and contributors. * **Proposal Assessment** - Once a good process is established for gathering information about a certain funding initiative type a follow on step will be to determine if those proposals are of sufficient quality or not and whether they have the potential to be impactful. An assessment process can help with addressing this by identifying the merits, opportunities and potential issues applicable to each proposal. * **Decision Making** - A community could adopt a range of approaches for the decision making process when voting on which initiatives to fund. Considerations are needed on when it is useful to adopt a qualitative process to bring community members together to discuss different initiatives. Also considerations are needed for what data and insights could be integrated into the decision process to better inform the voters. * **Funding Categorisations & Weightings** - How funding is made available will have an impact on what initiatives can be funded and the overall effectiveness of the funding process. Treasuries have the option to allocate resources to a range of initiative types and apply different amounts of funding to each type. Creating these categorisations is difficult as any outcomes from these decisions will determine how funding is directed to certain areas and groupings of initiatives. * **Voting Mechanisms & Approaches** - What voting approaches could be used to select and vote on proposals in different funding initiatives? Understanding the tradeoffs of each voting approach will help with the creation of more effective voting systems that can handle the different use cases and types of funding initiatives. The weighting models that get applied to voting will also be a point of consideration, such as when skill or length of contribution time should increase or reduce someone's voting power. Different forms of voting will need to be considered and their trade offs such as for a yes or no system, preference based voting, quadratic voting and other voting mechanisms. * **Funding Distribution Mechanisms** - Funding could be distributed to selected proposals in a number of ways such as through milestones, time based segmentation, all at once or upon completion of the proposals intent. Different funding initiatives may be more suited to different release mechanisms and cadences for distributing funding based on the risks and complexities of the funding initiative type. * **Tracking Progress & Completion** - A community can benefit from being able to measure and verify the progress and completion of any of the funded proposals. Distribution mechanisms used to distribute funding to contributors can also potentially include automated or community based review processes as part of the disbursement process to sign off milestones and completions. Improving this process can help with reducing the loss of treasury funding to time wasters, scams or underperforming proposals. It could also help with identifying the more effective contributors from looking at the execution of their own proposal. * **Measuring Impact** - The community benefits from reviewing completed proposals to reflect on how impactful any generated outcomes were compared against the total amount of allocated resources it took to achieve those outcomes. Understanding the impact generated by each completed initiative will help with improving future funding disbursement decisions if voters are increasingly able to select initiatives that are more likely to create high impact. # Contributors The contributors involved in supporting the Web 3 Association contribution outcomes ## Current contributors {% content-ref url="/pages/NKtRapbUFlHRWXJnDk5p" %} [George Lovegrove](/about/contributors/george-lovegrove) {% endcontent-ref %} ## Become a contributor We're always looking for contributors who want to help with our deep research and analysis resources about treasury systems. If you would like to help make contributions to this work and join the efforts please reach out to us by email () or in our [Telegram](https://t.me/W3Association) chat. # George Lovegrove W3A Contributor **Links** * :briefcase: [Linkedin](https://www.linkedin.com/in/georgelovegrove/) * :man\_technologist: [GitHub](https://github.com/lovegrovegeorge) * :bird: [Twitter](https://twitter.com/lovegrovegeo) **Professional background** Software developer of over 6 years in web and mobile development environments. More details can be found on LinkedIn. **Relevant experience** I have already spent over a year analysing treasury systems with the Web3 Association and shared a number of suggestions that could be highly impactful for Web3 ecosystems to explore. Prior to the Web3 Association I contributed towards the funding process from Cardano called[ Project Catalyst](https://projectcatalyst.io/). I created analytical resources on the topic area of [funding categorisation approaches](https://docs.catalystcontributors.org/funding-categorisation-analysis/) to help with finding more effective solutions. That analysis work led to changes being made to the funding process which even using [conservative estimates resulted in about a 200%](https://docs.catalystcontributors.org/funding-categorisation-analysis/historical-analysis-and-comparisons/categorisation-overall-cost-comparison) return on investment in a single funding round. The Web3 Association was started to continue these efforts with a new focus around collaborating with the wider industry to help improve treasury systems. **Web3 Association contributions** {% content-ref url="/pages/m7gZcasgWzJsxzqAhBuD" %} [Contribution logs](/about/contributors/george-lovegrove/contribution-logs) {% endcontent-ref %} **Contributions** * [Treasury analysis](https://docs.treasuries.io/) * [Funding analysis](https://funding.treasuries.io/) * [Income analysis](https://income.treasuries.io/) * [Open source contributor proposal](https://docs.contributors.org/) * [Funding categorisation analysis](https://docs.catalystcontributors.org/funding-categorisation-analysis/) * [Funding categories](/about/approach/shared-learning) # Contribution logs Recording of any contribution outputs and efforts in each month ## 2025 {% content-ref url="/pages/RLZv7hr5dwmJPF9LEE3a" %} [July 2025](/about/contributors/george-lovegrove/contribution-logs/july-2025) {% endcontent-ref %} {% content-ref url="/pages/6WZQfR3q4HKNzNI9b0Uk" %} [June 2025](/about/contributors/george-lovegrove/contribution-logs/june-2025) {% endcontent-ref %} {% content-ref url="/pages/WD2zhAY3UqX7VnJykykv" %} [May 2025](/about/contributors/george-lovegrove/contribution-logs/may-2025) {% endcontent-ref %} {% content-ref url="/pages/Hs0fknZg8mmSRJrMwfQp" %} [April 2025](/about/contributors/george-lovegrove/contribution-logs/april-2025) {% endcontent-ref %} {% content-ref url="/pages/CsaJzEBigGAnfU1tQFz4" %} [March 2025](/about/contributors/george-lovegrove/contribution-logs/march-2025) {% endcontent-ref %} {% content-ref url="/pages/hEvHCYqaImJJ8EioQEmY" %} [February 2025](/about/contributors/george-lovegrove/contribution-logs/february-2025) {% endcontent-ref %} {% content-ref url="/pages/Uu9lv4sXzKEjJnBOJm0X" %} [January 2025](/about/contributors/george-lovegrove/contribution-logs/january-2025) {% endcontent-ref %} ## 2024 {% content-ref url="/pages/l4XVCVvCyor5Nqb9ED5i" %} [December 2024](/about/contributors/george-lovegrove/contribution-logs/december-2024) {% endcontent-ref %} {% content-ref url="/pages/BIv2x4GLd9xqPIJFJj2F" %} [November 2024](/about/contributors/george-lovegrove/contribution-logs/november-2024) {% endcontent-ref %} {% content-ref url="/pages/FFOqnmGhARspj0JLAai1" %} [October 2024](/about/contributors/george-lovegrove/contribution-logs/october-2024) {% endcontent-ref %} {% content-ref url="/pages/XDEVkBwCfeLLFoGW08W1" %} [September 2024](/about/contributors/george-lovegrove/contribution-logs/september-2024) {% endcontent-ref %} {% content-ref url="/pages/qe7GV9OiQkVI9fE5meg8" %} [August 2024](/about/contributors/george-lovegrove/contribution-logs/august-2024) {% endcontent-ref %} {% content-ref url="/pages/cuwYswURZYiEQSEHHb4N" %} [July 2024](/about/contributors/george-lovegrove/contribution-logs/july-2024) {% endcontent-ref %} {% content-ref url="/pages/BVaWBYLXRhl6lCSV1u9K" %} [June 2024](/about/contributors/george-lovegrove/contribution-logs/june-2024) {% endcontent-ref %} {% content-ref url="/pages/PVrQkot2i7gDRwZUTmwd" %} [May 2024](/about/contributors/george-lovegrove/contribution-logs/may-2024) {% endcontent-ref %} {% content-ref url="/pages/IEspX3kLHaA9JZxSxfgo" %} [April 2024](/about/contributors/george-lovegrove/contribution-logs/april-2024) {% endcontent-ref %} {% content-ref url="/pages/dqh4CrPcu6rye2sFgibA" %} [March 2024](/about/contributors/george-lovegrove/contribution-logs/march-2024) {% endcontent-ref %} {% content-ref url="/pages/BsNhhNzCjiqpOz82gUSU" %} [February 2024](/about/contributors/george-lovegrove/contribution-logs/february-2024) {% endcontent-ref %} {% content-ref url="/pages/hW54mlnwa9Bz6fOWFAnI" %} [January 2024](/about/contributors/george-lovegrove/contribution-logs/january-2024) {% endcontent-ref %} ## 2023 {% content-ref url="/pages/TtDjUd4Q917POPjC2vM7" %} [December 2023](/about/contributors/george-lovegrove/contribution-logs/december-2023) {% endcontent-ref %} {% content-ref url="/pages/775AfPQEG06z336kgNFW" %} [November 2023](/about/contributors/george-lovegrove/contribution-logs/november-2023) {% endcontent-ref %} {% content-ref url="/pages/fa581n6FEm76zjCAo1vX" %} [October 2023](/about/contributors/george-lovegrove/contribution-logs/october-2023) {% endcontent-ref %} {% content-ref url="/pages/H3bKqCdZSeR3hgMEi05H" %} [September 2023](/about/contributors/george-lovegrove/contribution-logs/september-2023) {% endcontent-ref %} {% content-ref url="/pages/dU2MYbfCSi9KMd5KgSwk" %} [August 2023](/about/contributors/george-lovegrove/contribution-logs/august-2023) {% endcontent-ref %} # July 2025 Contributions for July 2025 **Contribution duration** - 7 days ## Overview * Money resource improvements - Reviewed and improved all of the resources where possible. * Demurrage implementation - Brought together all of the suggested ways to implement demurrage into a Web3 network into a single document. * Income resources update - Changed the usage of the word "wealth tax" to "network coin tax" across all the resources. ## Contribution outputs **Documents** Money resources * [Demurrage implementation](https://money.web3economy.io/web3-network-coin/demurrage-implementation) Treasury income resources * [Income approaches](https://income.treasuries.io/approaches/income-approaches) * [Transaction fee approaches](https://docs.web3association.io/) * [Network coin tax approaches](https://income.treasuries.io/approaches/network-coin-tax-approaches) # June 2025 Contributions for June 2025 **Contribution duration** - 21 days ## Overview * Demurrage advantages & opportunities update - Added reduce money based inequality and granular incentive mechanisms as advantages into the resource. * Video interview - Participated in an interview with Josh Sidman talking about Web3 and demurrage. * Is the network coin necessary? - Understanding the importance of the network coin in operating a Web3 network. * Use cases & responsibilities update - Added in contract collateral as an added use case for the network coin. * Importance of network coin demand - Outlining the reasons why demand for the network coin is so important for a Web3 network. * Network coin tax data modelling update - Adding in another data model looking at the implications of yield and price appreciation on implementing demurrage. * Video panel discussion - Participated in a roundtable panel discussion about developing trust based solutions with Web3 technology. * Web3 & demurrage article - Started writing an article that brings together all of the core information from the analysis in a shorter written article format. ## Contribution outputs **Videos** * [A conversation with George Lovegrove](https://www.youtube.com/watch?v=itBZ3vGkTbU\&t=8s) * [Roundtable discussion](https://docs.web3association.io/) **Documents** Money resources * [Demurrage advantages & opportunities](https://money.web3economy.io/web3-network-coin/demurrage-advantages-and-opportunities) * [Is the network coin necessary?](https://money.web3economy.io/web3-money/network-coin-and-tokens/is-the-network-coin-necessary) * [Use cases & responsibilities](https://money.web3economy.io/web3-money/use-cases-and-responsibilities) * [Importance of network coin demand](https://money.web3economy.io/web3-network-coin/importance-of-network-coin-demand) * [Network coin tax data modelling](https://money.web3economy.io/web3-network-coin/network-coin-tax-data-modelling) # May 2025 Contributions for May 2025 **Contribution duration** - 14 days ## Overview * Hoardable vs storable update - The money resources were updated to use the word storable instead of hoardable as this better describes the property of the system. * Goals & concessions update - Rewrote the goals & concessions list based on previous improvements made across the resources. * Stable demand for the network coin update - Added in single asset borrowing and lending into the resource for comparison with the other incentive options. * Network coin supply approaches - Comparing the approaches that could be used for maintianing the supply of the network coin. ## Contribution outputs **Documents** Money resources * [Goals & concessions](https://money.web3economy.io/web3-network-coin/goals-and-concessions) * [Stable demand for the network coin update](https://money.web3economy.io/web3-network-coin/stable-demand-for-the-network-coin) * [Network coin supply approaches](https://money.web3economy.io/web3-network-coin/stable-demand-for-the-network-coin) # April 2025 Contributions for April 2025 **Contribution duration** - 3 days ## Overview * Network coin & tokens update - Added in a comparison of the properties of the network coin and tokens to better understand their differences and why the network coin is inherently desirable as an asset to hold if the monetary policies were the same. ## Contribution outputs **Documents** Money resources * [Network coin & tokens](https://money.web3economy.io/web3-money/network-coin-and-tokens) # March 2025 Contributions for March 2025 **Contribution duration** - Full month ## Overview * Network coins & tokens update - Added in store of value property to the resource comparison. * Income approaches update - Added in more details around the topic of transaction deadweight loss and how the impacts of this can be reduced. * Network coin tax data modelling - Data model exploring the differences between storable and demurrage based network coins. * Stable demand for the network coin update - Added more information about a wealth tax reduction incentive and a transaction fee reduction incentive as mechanisms that could help with generating more stable demand for the network coin. * Web3 network effects - Comparing different approaches that might help with creating more network effects for a Web3 network. * Demurrage is inevitable - Creating a resource that makes the case for why demurrage is an inevitable solution for Web3 networks. * Observations, goals & concessions - Created a separate resource for thinking about the goals and concessions for token based forms of money. * Token money adoption possibilities - Thinking about where token based systems of money could be adopted. * Web3 economic development roadmap update - Reordered treasury funding processes at the top due to their importance for introducing and increasing any taxation rates. * Financial liquidity incentive options - Listing all of the financial liquidity incentive options that a Web3 network has and determining which ones are most suitable for the network coin. * Interest - Updated the money resources after some feedback from Josh Sidman about the resources that cover Silvio Gesell's theories around demurrage ## Contribution outputs **Documents** Money resources * [Network coins & tokens](https://money.web3economy.io/web3-money/network-coin-and-tokens) * [Network coin tax data modelling](https://money.web3economy.io/web3-network-coin/network-coin-tax-data-modelling) * [Stable demand for the network coin](https://money.web3economy.io/web3-network-coin/network-coin-tax-data-modelling) * [Web3 network effects](https://money.web3economy.io/web3-network-coin/web3-network-effects) * [Demurrage is inevitable](https://money.web3economy.io/web3-network-coin/demurrage-is-inevitable) * [Observations, goals & concessions](https://money.web3economy.io/web3-tokens/observations-goals-and-concessions) * [Token money adoption possibilities](https://money.web3economy.io/web3-tokens/observations-goals-and-concessions) * [Financial liquidity incentive options](https://money.web3economy.io/web3-network-coin/stable-demand-for-the-network-coin/financial-liquidity-incentive-options) * [Interest](https://money.web3economy.io/money/interest) Web3 economy resources * [Web3 economic development roadmap](https://docs.web3association.io/) Treasury income resources * [Income approaches](https://income.treasuries.io/approaches/income-approaches) # February 2025 Contributions for February 2025 **Contribution duration** - Full month ## Overview * Money resources - Released first version of the money resources that cover the core pieces of theory to understand the theory behind demurrage. * Facilitating the exchange process - Understanding how the system of money has changed when it moved from a physical system to a digital one. * Use cases & responsibilities - Looking at the different use cases and responsibilities for network coins and tokens. * Network coin & tokens - Outlining the differences between a network coin and tokens. * Demurrage implementation approaches - Comparing the different approaches that could be used to implement demurrage in a Web3 network. * Stable demand for the network coin - Comparing different approaches that could be used to generate long term demand for the network coin. * Goals & concessions - Listing out some ideas for goals and concessions that a Web3 network can adopt when implementing demurrage. * Web3 network development phases - Comparing the differences and requirements that a network has in relation to demurrage at different phases of development. * Demurrage advantages & opportunities - Listing out the advantages and opportunities of adopting demurrage in a Web3 network. * Demurrage risks & challenges - Listing out some of the risks and challenges of adopting demurrage and the counter arguments to those problems. * Governance domain - Adopted a new sub domain for governance related funding process resources. * Voting delegation - Articulating why voter delegation is unavoidable and looking at some approaches for how voting delegation could be implemented. * Web3 Economy domain - Added a new website front page to direct people towards resources about the Web3 economy. * Web3 economic development roadmap - Created a priority list of things that need to be developed to fix the global economy with Web3. ## Contribution outputs **Domains** * [money.web3economy.io](https://money.web3economy.io) * [governance.treasuries.io](https://governance.treasuries.io/) * [web3economy.io](https://web3economy.io/) * [docs.web3economy.io](https://docs.web3economy.io) **Documents** Money resources * [Nature of exchange](https://money.web3economy.io/money/nature-of-exchange) * [Medium of exchange](https://money.web3economy.io/money/medium-of-exchange) * [Incompatibility of the functions of money](https://money.web3economy.io/money/incompatibility-of-the-functions-of-money) * [Interest](https://money.web3economy.io/money/interest) * [Consequences of interest](https://money.web3economy.io/money/consequences-of-interest) * [Demurrage](https://money.web3economy.io/money/demurrage) * [Facilitating the exchange process](https://money.web3economy.io/web3-money/facilitating-the-exchange-process) * [Use cases & responsibilities](https://money.web3economy.io/web3-money/use-cases-and-responsibilities) * [Network coin & tokens](https://money.web3economy.io/web3-money/facilitating-the-exchange-process) * [Demurrage implementation approaches](https://money.web3economy.io/web3-network-coin/demurrage-implementation-approaches) * [Stable demand for the network coin](https://money.web3economy.io/web3-network-coin/stable-demand-for-the-network-coin) * [Goals & concessions](https://money.web3economy.io/web3-network-coin/goals-and-concessions) * [Web3 network development phases](https://money.web3economy.io/web3-network-coin/web3-network-development-phases) * [Demurrage advantages & opportunities](https://money.web3economy.io/web3-network-coin/demurrage-advantages-and-opportunities) * [Demurrage risks & challenges](https://money.web3economy.io/web3-network-coin/demurrage-risks-and-challenges) Funding process governance * [Voting delegation](https://governance.treasuries.io/voting/voting-delegation) Web3 economy resources * [Web3 economic development roadmap](https://docs.web3economy.io/web3-economy/web3-economic-development-roadmap) # January 2025 Contributions for January 2025 **Contribution duration** - Full month ## Overview * Income approaches update - The wealth tax was added into the approaches analysis * Transaction fee approaches update - Simplified the document to only consider fixed fees, finality fees and demand fees. Percentage based transaction fees are no longer necessary due to the opportunity to use a network coin tax. * Wealth tax approaches - Considerations are made about how a wealth tax could be implemented including its coverage, regularity and the amount. * Money resources - Actively working on the first version of some money resources for the Web3 economy website. ## Contribution outputs **Documents** Treasury income resources * [Income approaches](/about/approach/contribution-outcomes) * [Transaction fee approaches](https://income.treasuries.io/approaches/transaction-fee-approaches) * [Wealth tax approaches](https://docs.web3association.io/) # December 2024 Contributions for December 2024 **Contribution duration** - Full month ## Overview * Economic research - Actively researching and understanding more about the ideas of demurrage from Silvio Gesell and starting to apply them to Web3. * Website domain migration - Domains were migrated to .io equivalents. This included web3association.io, treasuries.io and contributionism.io. ## Contribution outputs **Domains** * New domains - [web3association.io](https://web3association.io), [treasuries.io](https://treasuries.io/) and [contributionism.io](https://contributionism.io/) # November 2024 Contributions for November 2024 **Contribution duration** - Full month ## Overview * Economic model - Finished the first version of the economic model called contributionism * Economic theory - Started learning about different economic theories such as Georgism and Gesselism. ## Contribution outputs **Documents** Economic model resources * [Critiques of capitalism](https://docs.contributionism.io/contributionism/critiques-of-capitalism) * [Understanding capitalism](https://docs.contributionism.io/contributionism/critiques-of-capitalism/understanding-capitalism) * [Flawed justifications for unfair contribution treatment](https://docs.contributionism.io/contributionism/critiques-of-capitalism/flawed-justifications-for-unfair-contribution-treatment) * [Contributions are not respected](https://docs.contributionism.io/contributionism/critiques-of-capitalism/contributions-are-not-respected) * [Flawed share governance and incentive rights](https://docs.contributionism.io/contributionism/critiques-of-capitalism/flawed-share-governance-and-incentive-rights) * [Fair compensation often requires ongoing gestures of goodwill](https://docs.contributionism.io/contributionism/critiques-of-capitalism/fair-compensation-often-requires-ongoing-gestures-of-goodwill) * [Risk of stagnant ownership and leadership that isn’t collectively accepted](https://docs.contributionism.io/contributionism/critiques-of-capitalism/risk-of-stagnant-ownership-and-leadership-that-isnt-collectively-accepted) * [Risk of motive, priority and incentive misalignment](https://docs.contributionism.io/contributionism/critiques-of-capitalism/risk-of-motive-priority-and-incentive-misalignment) * [Excessive competition](https://docs.contributionism.io/contributionism/critiques-of-capitalism/excessive-competition) * [Equal opportunity and meritocratic fallacies](https://docs.contributionism.io/contributionism/critiques-of-capitalism/equal-opportunity-and-meritocratic-fallacies) * [Principles](https://docs.contributionism.io/contributionism/principles) - Updated * [Respect contribution](https://docs.contributionism.io/contributionism/principles/respect-contribution) - Updated * [Contributor & public ownership](https://docs.contributionism.io/contributionism/principles/contributor-and-public-ownership) - Updated * [Contributor governed](https://docs.contributionism.io/contributionism/principles/contributor-governed) * [Temporary governance rights](https://docs.contributionism.io/contributionism/principles/temporary-governance-rights) - Updated * [Temporary incentive rights](https://docs.contributionism.io/contributionism/principles/temporary-incentive-rights) - Updated * [Transparent priorities](https://docs.contributionism.io/contributionism/principles/transparent-priorities) - Updated * [Collectively accepted leadership](https://docs.contributionism.io/contributionism/principles/collectively-accepted-leadership) - Updated * [Characteristics](https://docs.contributionism.io/contributionism/characteristics) * [Permanent records of contribution](https://docs.contributionism.io/contributionism/characteristics/permanent-records-of-contribution) - Updated * [Equal opportunity](https://docs.contributionism.io/contributionism/characteristics/equal-opportunity) - Updated * [Cooperative & competitive environments](https://docs.contributionism.io/contributionism/characteristics/cooperative-and-competitive-environments) - Updated * [Economic model](https://docs.contributionism.io/contributionism/economic-model) - Updated * [Organisations](https://docs.contributionism.io/contributionism/economic-model/organisations) - Updated * [Ownership](https://docs.contributionism.io/contributionism/economic-model/organisations/ownership) - Updated * [Consumer & donor ownership](https://docs.contributionism.io/contributionism/economic-model/organisations/ownership/consumer-and-donor-ownership) * [Mixed contribution ownership](https://docs.contributionism.io/contributionism/economic-model/organisations/ownership/mixed-contribution-ownership) * [Governance](https://docs.contributionism.io/contributionism/economic-model/organisations/governance) - Updated * [Incentives](https://docs.contributionism.io/contributionism/economic-model/organisations/incentives) - Updated * [Exchange](https://docs.contributionism.io/contributionism/economic-model/exchange) - Updated * [Market failures](https://docs.contributionism.io/contributionism/economic-model/exchange/market-failures) * [Government](https://docs.contributionism.io/contributionism/economic-model/governments) - Updated * [Capitalism vs contributionism](https://docs.contributionism.io/contributionism/capitalism-vs-contributionism) * [Critiques of contributionism](https://docs.contributionism.io/contributionism/critiques-of-contributionism) * [Path to adoption](https://docs.contributionism.io/contributionism/path-to-adoption) * [Contribution table](https://docs.contributionism.io/resources/contribution-table) * [Roadmap](https://docs.contributionism.io/resources/roadmap) # October 2024 Contributions for October 2024 **Contribution duration** - Full month ## Overview * Economic model - Continued our work on new economic model ## Contribution outputs **Documents** Economic model resources * [What is contributionism?](https://docs.contributionism.io/contributionism/what-is-contributionism) - Updated * [Other definitions & usage of the term Contributionism](https://docs.contributionism.io/contributionism/what-is-contributionism/other-definitions-and-usage-of-the-term-contributionism) - Updated * [Principles](https://docs.contributionism.io/contributionism/principles) - Updated * [Respect contribution](https://docs.contributionism.io/contributionism/principles/respect-contribution) - Updated * [Contributor & public ownership](https://docs.contributionism.io/contributionism/principles/contributor-and-public-ownership) - Updated * [Temporary governance rights](https://docs.contributionism.io/contributionism/principles/temporary-governance-rights) - Updated * [Temporary incentive rights](https://docs.contributionism.io/contributionism/principles/temporary-incentive-rights) - Updated * [Transparent priorities](https://docs.contributionism.io/contributionism/principles/transparent-priorities) - Updated * [Collectively accepted leadership](https://docs.contributionism.io/contributionism/principles/collectively-accepted-leadership) - Updated * [Cooperative & competitive environments](https://docs.contributionism.io/contributionism/characteristics/cooperative-and-competitive-environments) - Updated * [Permanent records of contribution](https://docs.contributionism.io/contributionism/characteristics/permanent-records-of-contribution) * [Equal opportunity](https://docs.contributionism.io/contributionism/characteristics/equal-opportunity) * [Economic model](https://docs.contributionism.io/contributionism/economic-model) - Updated * [Organisations](https://docs.contributionism.io/contributionism/economic-model/organisations) - Updated * [Ownership](https://docs.contributionism.io/contributionism/economic-model/organisations/ownership) - Updated * [Governance](https://docs.contributionism.io/contributionism/economic-model/organisations/governance) - Updated * [Incentives](https://docs.contributionism.io/contributionism/economic-model/organisations/incentives) - Updated * [Exchange](https://docs.contributionism.io/contributionism/economic-model/exchange) - Updated * [Government](https://docs.contributionism.io/contributionism/economic-model/governments) - Updated * [Money](https://docs.contributionism.io/contributionism/economic-model/money) - Updated * [Complimentary models](https://docs.contributionism.io/contributionism/economic-model/complimentary-models) - Updated * [Implementation](https://docs.contributionism.io/contributionism/implementation) - Updated * [Contribution tables](https://docs.contributionism.io/contributionism/implementation/contribution-tables) - Updated * [Loans](https://docs.contributionism.io/contributionism/implementation/loans) - Updated * [Leadership contracts](https://docs.contributionism.io/contributionism/implementation/leadership-contracts) - Updated * [Organisation parameters](https://docs.contributionism.io/contributionism/implementation/organisation-parameters) - Updated * [Data modelling](https://docs.contributionism.io/contributionism/implementation/data-modelling) - Updated # September 2024 Contributions for September 2024 **Contribution duration** - Full month ## Overview * Economic model - Continued our work on new economic model ## Contribution outputs **Documents** Economic model resources * [What is contributionism?](https://docs.contributionism.io/contributionism/what-is-contributionism) * [Other definitions & usage of the term Contributionism](https://docs.contributionism.io/contributionism/what-is-contributionism/other-definitions-and-usage-of-the-term-contributionism) * [Principles](https://docs.contributionism.io/contributionism/principles) * [Respect contribution](https://docs.contributionism.io/contributionism/principles/respect-contribution) * [Contributor & public ownership](https://docs.contributionism.io/contributionism/principles/contributor-and-public-ownership) * [Temporary governance rights](https://docs.contributionism.io/contributionism/principles/temporary-governance-rights) * [Temporary incentive rights](https://docs.contributionism.io/contributionism/principles/temporary-incentive-rights) * [Transparent priorities](https://docs.contributionism.io/contributionism/principles/transparent-priorities) * [Collectively accepted leadership](https://docs.contributionism.io/contributionism/principles/collectively-accepted-leadership) * [Cooperative & competitive environments](https://docs.contributionism.io/contributionism/characteristics/cooperative-and-competitive-environments) * [Economic model](https://docs.contributionism.io/contributionism/economic-model) * [Organisations](https://docs.contributionism.io/contributionism/economic-model/organisations) * [Ownership](https://docs.contributionism.io/contributionism/economic-model/organisations/ownership) * [Governance](https://docs.contributionism.io/contributionism/economic-model/organisations/governance) * [Incentives](https://docs.contributionism.io/contributionism/economic-model/organisations/incentives) * [Exchange](https://docs.contributionism.io/contributionism/economic-model/exchange) * [Government](https://docs.contributionism.io/contributionism/economic-model/governments) * [Money](https://docs.contributionism.io/contributionism/economic-model/money) * [Complimentary models](https://docs.contributionism.io/contributionism/economic-model/complimentary-models) * [Implementation](https://docs.contributionism.io/contributionism/implementation) * [Contribution tables](https://docs.contributionism.io/contributionism/implementation/contribution-tables) * [Loans](https://docs.contributionism.io/contributionism/implementation/loans) * [Leadership contracts](https://docs.contributionism.io/contributionism/implementation/leadership-contracts) * [Organisation parameters](https://docs.contributionism.io/contributionism/implementation/organisation-parameters) * [Data modelling](https://docs.contributionism.io/contributionism/implementation/data-modelling) # August 2024 Contributions for August 2024 **Contribution duration** - Full month ## Overview * Contributor funding - Improving the existing resources that have been created. Added a experiment time & cost estimates resource. * Contributor funding example - Improved the existing example resources that have been created already. * Treasury analysis updates - Updated the analysis in the treasuries and Web3 treasuries sections. * Economic model - Started working on a new economic model. ## Contribution outputs **Documents** Contributor funding resources * [Objectives](https://funding.contributors.org/contributor-funding-experiment/objectives) - Updated * [Development roadmap](https://funding.contributors.org/contributor-funding-experiment/development-roadmap) - Updated * [Experiment setup](https://funding.contributors.org/contributor-funding-experiment/experiment-setup) - Updated * [Templates](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates) * [Guides](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/guides) * [Voter guide](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/guides/voter-guide) - Updated * [Funding operator guide](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/guides/funding-operator-guide) - Updated * [Time & cost estimates](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/time-and-cost-estimates) Contributor funding experiment example * [Community guide](https://example.contributors.org/contributor-funding-guides/community-guide) - Updated * [Contributor guide](https://example.contributors.org/contributor-funding-guides/contributor-guide) - Updated * [Contribution attestation guide](https://example.contributors.org/contributor-funding-guides/contribution-attestation-guide) - Updated * [Voter guide](https://example.contributors.org/contributor-funding-guides/voter-guide) - Updated * [Funding operator guide](https://example.contributors.org/contributor-funding-guides/funding-operator-guide) - Updated Treasury resources * [Purpose & responsibilities](https://docs.treasuries.io/treasuries/purpose-and-responsibilities) - Updated * [Impact of treasuries](https://docs.treasuries.io/treasuries/impact-of-treasuries) - Updated * [Functional processes](https://docs.treasuries.io/treasuries/functional-processes) - Updated * [Opportunities & concerns](https://docs.treasuries.io/web3-treasuries/opportunities-and-concerns) - Updated * [Operating process ](https://docs.treasuries.io/web3-treasuries/operating-process)- Updated * [Funding responsibilities](https://docs.treasuries.io/web3-treasuries/funding-responsibilities) - Updated # July 2024 Contributions for July 2024 **Contribution duration** - Full month ## Overview * Voting score approaches - Looked at the different parts of score voting approaches to determine what combination of approaches could be the most effective for Web3 ecosystems. Expressive approval voting emerged as a suggestion for ecosystems to explore. * Contributor funding - The goals and objectives of a contributor funding process were documented along with a development roadmap and a experiment setup guide. The experiment setup guide suggested the tech stack, provided some templates, outlined the parameters and approaches and also made some time and cost estimations. * Contributor funding example - An example resource was made to showcase what a contributor funding experiment could look like. The suggested tools were created and filled in with some example data to give a good idea of what the funding process could look like in practice. ## Contribution outputs **Documents** Treasury resources * [Score voting approaches](https://docs.treasuries.io/voting/score-voting-approaches) * [Points allocation approaches](https://docs.treasuries.io/voting/score-voting-approaches/points-allocation-approaches) * [Maximum points allocation approaches](https://docs.treasuries.io/voting/score-voting-approaches/points-allocation-approaches/maximum-points-allocation-approaches) * [Maximum proposal allocation factors for consideration](https://docs.treasuries.io/voting/score-voting-approaches/points-allocation-approaches/maximum-points-allocation-approaches/maximum-proposal-allocation-factors-for-consideration) * [No maximum allocation](https://docs.treasuries.io/voting/score-voting-approaches/points-allocation-approaches/maximum-points-allocation-approaches/no-maximum-allocation) * [Quadratic allocation](https://docs.treasuries.io/voting/score-voting-approaches/points-allocation-approaches/maximum-points-allocation-approaches/quadratic-allocation) * [Fixed maximum allocation](https://docs.treasuries.io/voting/score-voting-approaches/points-allocation-approaches/maximum-points-allocation-approaches/fixed-maximum-allocation) * [Points allocation factors for consideration](https://docs.treasuries.io/voting/score-voting-approaches/points-allocation-approaches/points-allocation-factors-for-consideration) * [Voting power per decision](https://docs.treasuries.io/voting/score-voting-approaches/points-allocation-approaches/voting-power-per-decision) * [Number of proposals multiple points per decision](https://docs.treasuries.io/voting/score-voting-approaches/points-allocation-approaches/number-of-proposals-multiple-points-per-decision) * [Available positions single point per decision](https://docs.treasuries.io/voting/score-voting-approaches/points-allocation-approaches/available-positions-single-points-per-decision) * [Available positions multiple points per decision](https://docs.treasuries.io/voting/score-voting-approaches/points-allocation-approaches/available-positions-multiple-points-per-decision) * [Multiple points per decision](https://docs.treasuries.io/voting/score-voting-approaches/points-allocation-approaches/multiple-points-per-decision) * [Multiple points per proposal](https://docs.treasuries.io/voting/score-voting-approaches/points-allocation-approaches/multiple-points-per-proposal) * [Single point per proposal](https://docs.treasuries.io/voting/score-voting-approaches/points-allocation-approaches/single-point-per-proposal) * [Applying the score voting examples to these approaches](https://docs.treasuries.io/voting/score-voting-approaches/applying-the-score-voting-examples-to-these-approaches) * [Voting approach improvement ideas](https://docs.treasuries.io/voting/score-voting-approaches/voting-approach-improvement-ideas) * [Expressive approval voting with decision disapprovals](https://docs.treasuries.io/voting/score-voting-approaches/expressive-approval-voting-with-decision-disapprovals) Contributor funding resources * [Objectives](https://funding.contributors.org/contributor-funding-experiment/objectives) * [Development roadmap](https://funding.contributors.org/contributor-funding-experiment/development-roadmap) * [Experiment setup](https://funding.contributors.org/contributor-funding-experiment/experiment-setup) * [Tech stack](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/tech-stack) * [Templates](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates) * [Guides](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/guides) * [Community guide](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/guides/community-guide) * [Contributor guide](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/guides/contributor-guide) * [Contribution attestation guide](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/guides/contribution-attestation-guide) * [Voter guide](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/guides/voter-guide) * [Expressive approval voting guide](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/guides/voter-guide/expressive-approval-voting-guide) * [Funding operator guide](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/guides/funding-operator-guide) * [Forms](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/forms) * [Contributor proposal form](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/forms/contributor-proposal-form) * [Contribution log form](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/forms/contribution-log-form) * [Contribution attestation form](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/forms/contribution-attestation-form) * [Questionnaires](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/questionnaires) * [Contributor proposal submission feedback](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/questionnaires/contributor-proposal-submission-feedback) * [Contributor selection decision feedback](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/questionnaires/contributor-selection-decision-feedback) * [Contributor peer review and feedback](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/questionnaires/contributor-peer-review-and-feedback) * [Voter experiment feedback](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/questionnaires/voter-experiment-feedback) * [Contributor experiment feedback](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/questionnaires/contributor-experiment-feedback) * [Google Sheets](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/templates/google-sheets) * [Contributor voting sheet](https://docs.google.com/spreadsheets/d/1vxd9KvrnAJX378e_2sJmo00CKzRZF3t1Efj5_FJ1jJA/edit?gid=0#gid=0) * [Approach and parameter decisions](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/approach-and-parameter-decisions) Contributor funding experiment example * [Community guide](https://example.contributors.org/contributor-funding-guides/community-guide) * [Contributor guide](https://example.contributors.org/contributor-funding-guides/contributor-guide) * [Contribution attestation guide](https://example.contributors.org/contributor-funding-guides/contribution-attestation-guide) * [Voter guide](https://example.contributors.org/contributor-funding-guides/voter-guide) * [Funding operator guide](https://example.contributors.org/contributor-funding-guides/funding-operator-guide) * [Priority suggestions](https://example.contributors.org/current-funding-round/priority-suggestions) * [Contribution board](https://example.contributors.org/current-funding-round/contribution-focus) * [Funded contributors](https://example.contributors.org/current-funding-round/funded-contributors) * [Alice Adams](https://example.contributors.org/current-funding-round/funded-contributors/alice-adams) * [June 2024](https://example.contributors.org/current-funding-round/funded-contributors/alice-adams/june-2024) * [Candidates](https://example.contributors.org/current-funding-round/candidates) * [Alice Adams](https://example.contributors.org/current-funding-round/candidates/alice-adams) * [Bob Baker](https://example.contributors.org/current-funding-round/candidates/bob-baker) * [Charlie Collins](https://example.contributors.org/current-funding-round/candidates/charlie-collins) # June 2024 Contributions for June 2024 **Contribution duration** - Full month ## Overview * Voting power approaches - Compared different voting power approaches and how they can be combined together over the long term to create a hybrid solution. * Voting approaches - Compared the different high level voting approaches that a Web3 ecosystem could adopt such as majority, plurality, proportional, preference and score voting systems. * Approach comparison methodology - Documented how we do our approach comparisons and why this methodology is effective. Updated all comparison factors for consideration documents to point to this methodology. * Identity project research - Researched different identity projects in the industry to explore potential partnerships for working on contributor funding related infrastructure. ## Contribution outputs **Documents** Treasury resources * [Voting power approaches](https://docs.treasuries.io/voting/voting-power-approaches) * [Voting power factors for consideration](https://docs.treasuries.io/voting/voting-power-approaches/voting-power-factors-for-consideration) * [One person one vote](https://docs.treasuries.io/voting/voting-power-approaches/one-person-one-vote) * [Wealth based](https://docs.treasuries.io/voting/voting-power-approaches/wealth-based) * [Locked wealth based](https://docs.treasuries.io/voting/voting-power-approaches/locked-wealth-based) * [Ecosystem contributions](https://docs.treasuries.io/voting/voting-power-approaches/ecosystem-contributions) * [Financial contributions](/about/roadmap/other-areas-of-focus) * [Tax contributions](https://docs.treasuries.io/voting/voting-power-approaches/tax-contributions) * [Voting approaches](https://docs.treasuries.io/voting/voting-approaches) * [Voting factors for consideration](https://docs.treasuries.io/voting/voting-approaches/voting-factors-for-consideration) * [Plurality voting](https://docs.treasuries.io/voting/voting-approaches/plurality-voting) * [Majority voting](https://docs.treasuries.io/voting/voting-approaches/majority-voting) * [Proportional voting](https://docs.treasuries.io/voting/voting-approaches/proportional-voting) * [Preference voting](https://docs.treasuries.io/voting/voting-approaches/preference-voting) * [Score voting](/about/roadmap/other-areas-of-focus) * [Approach comparison methodology](https://docs.treasuries.io/analysis/approach-comparison-methodology) # May 2024 Contributions for May 2024 **Contribution duration** - 4 days ## Overview * Funding the network, protocol and application layers - Added extra analysis to explore the importance of network funding depending on what part of the ecosystem the initiative is focused on. ## Contribution outputs **Documents** Treasury resources * [Idea token vs contributor network funding](https://docs.treasuries.io/funding/idea-token-vs-contributor-network-funding) - Updated * [Funding the network, protocol and application layers](https://docs.treasuries.io/funding/idea-token-vs-contributor-network-funding/funding-the-network-protocol-and-application-layers) # April 2024 Contributions for April 2024 **Contribution duration -** Full month ## Overview * Contribution verification - Updated with more information about current landscape, recording & measuring contribution efforts and individual contribution logs * Contribution verification approaches - Updated with more factors for consideration * Contribution verification videos - Added videos that cover the contribution verification information * Idea token vs contributor network funding - Improved existing analysis by making an approach comparison with a number of factors being considered. * Communication - Shared individual contribution logs suggestion across a number of ecosystems ## **Contribution outputs** **Documents** Disbursement resources * [Contribution verification](https://disbursement.treasuries.io/contributions/contribution-verification) * [Current landscape](https://disbursement.treasuries.io/contributions/contribution-verification/current-landscape) * [Recording & measuring contribution efforts](https://disbursement.treasuries.io/contributions/contribution-verification/recording-and-measuring-contribution-efforts) * [Individual monthly contribution logs](https://disbursement.treasuries.io/contributions/contribution-verification/individual-monthly-contribution-logs) * [Contribution verification approaches](https://disbursement.treasuries.io/approaches/contribution-verification-approaches) - Updated Treasury resources * [Idea token vs contributor network funding](https://docs.treasuries.io/funding/idea-token-vs-contributor-network-funding) * [Circular economy ideas](https://docs.treasuries.io/funding/idea-token-vs-contributor-network-funding/circular-economy-ideas) - Updated * [Web2 protocol & software library examples](https://docs.treasuries.io/funding/idea-token-vs-contributor-network-funding/web2-protocols-and-software-library-examples) - Updated * [Ecosystem funding factors for consideration](https://docs.treasuries.io/funding/idea-token-vs-contributor-network-funding/ecosystem-funding-factors-for-consideration) * [Idea token funding](https://docs.treasuries.io/funding/idea-token-vs-contributor-network-funding/idea-token-funding) * [Contributor network funding](https://docs.treasuries.io/funding/idea-token-vs-contributor-network-funding/contributor-network-funding) **Videos** Contribution verification videos * [Contribution verification](https://www.youtube.com/watch?v=mlP4zgfO-As) * [Current landscape](https://www.youtube.com/watch?v=n8U_Sb4_0Vg) * [Recording & measuring contribution efforts](https://www.youtube.com/watch?v=Df3oEbs3Ffk) * [Individual monthly contribution logs](https://www.youtube.com/watch?v=MMtOkD9o9Q0) # March 2024 Contributions for March 2024 **Contribution duration** - Full month ## Overview * Current funding landscape video - Added a video covering contributor proposal content * Tech comparison with Web3 video - Added a video covering contributor proposal content * Open source contributor funding video - Added a video covering contributor proposal content * Income approaches - Compared different approaches that treasuries could use to generate income * Transaction fee approaches - Compared different approaches for handling transaction fees * Website - Created a treasury income page to add new education resources * Communication - Reached out to entire industry to share and discuss open source contributor funding process proposal ## Contribution outputs **Documents** Income resources * [Income approaches](https://income.treasuries.io/approaches/income-approaches) * [Transaction fee approaches](https://income.treasuries.io/approaches/transaction-fee-approaches) **Videos** Contributor proposal videos * [Current funding landscape](https://youtu.be/ZWo9qNm3mvs) * [Tech comparison with Web3](https://youtu.be/f3fP2bjf6rY) * [Open source contributor funding](https://youtu.be/NHKEMhQJ9d4) **Systems & operation** * [income.treasuries.io](https://income.treasuries.io) - Setup GitBook resource page # February 2024 Contributions for February 2024 **Contribution duration** - Full month ## Overview * Misaligned, partially aligned and fully aligned incentives - Exploring the differences between misaligned, partially aligned & fully aligned incentives. * Project token vs base network circular economies - Looking at how the positioning of circular economies can have a large impact on the incentives within an ecosystem. * Self sovereign identity opportunities - Listing example opportunities for Web3 ecosystem to explore for self sovereign identity solutions. * Treasury funding responsibilities - Listing out the different responsibilities that a Web3 ecosystems treasury could have. * Open source contributor funding proposal - Created a proposal that suggests a open source contributor funding process as a potentially impactful funding process that Web3 ecosystems could experiment with. * Websites - Setup new website for contributor resources. * Design - All websites and resource design assets have been overhauled with an improved design. ## Contribution outputs **Documents** Treasury resources * [Misaligned, partially aligned and fully aligned incentives](https://docs.treasuries.io/incentives/misaligned-partially-aligned-and-fully-aligned-incentives) * [Project token vs base network circular economies](https://docs.treasuries.io/incentives/project-token-vs-base-network-circular-economies) * [Treasury funding responsibilities](https://docs.treasuries.io/web3-treasuries/funding-responsibilities) Disbursement resources * [Self sovereign identity opportunities](https://disbursement.treasuries.io/contributors/self-sovereign-identity-opportunities) Contributor resources * [Open source contributor funding process proposal](https://docs.contributors.org/proposal/open-source-contributors) **Systems & operation** * [contributors.org](https://contributors.org) - Setup overview page and GitBook documentation # January 2024 Contributions for January 2024 **Contribution duration** - Full month ## Overview * Refactored disbursement resources - Moved the separate incentive resources content into the incentive approaches analysis and also cleaned up the knowledge, priority, idea and contributor process resources. * Impact measurement approaches - Explored how impact could be measured through the priorities, ideas and contributors that get selected by the ecosystem. * Decision approaches improvements - Merged the contributor vs idea selection voting comparison analysis into these resources. * Incentive approaches improvements - Added income stability and contribution flexibility factors an also added other incentive resources and merged them into this comparative analysis. * Idea cost approaches improvements - Improved analysis and visualisation of comparisons made between different idea cost approaches * Suggestions improvements - Overhauled the suggestions resources to include the main suggestions that have come out of the disbursement analysis and also listed a number of considerations that can be made when creating a disbursement process. * Updates to all resources - Improved information structure and wording across many resources. * Websites - Added two simple informational website overviews * Design - Added some documentation page headers * Analytics - Added Google analytics across GitBook and website ## **Contribution outputs** **Documents** Disbursement resources * [Disbursement process differences](https://funding.treasuries.io/process/disbursement-process-differences) - Updated * [Decision approaches](https://funding.treasuries.io/approaches/decision-approaches) - Updated * [Incentive approaches ](https://funding.treasuries.io/approaches/incentive-approaches)- Updated * [Idea cost approaches](https://funding.treasuries.io/approaches/incentive-approaches/idea-cost-approaches) - Updated * [Proposal submission incentives](https://funding.treasuries.io/approaches/incentive-approaches/proposal-submission-incentives) - Updated * [Maintenance of information incentives](https://funding.treasuries.io/approaches/incentive-approaches/maintenance-of-information-incentives) - Updated * [Impact measurement approaches](https://funding.treasuries.io/approaches/impact-measurement-approaches) * [Ecosystem areas for impact measurement](https://funding.treasuries.io/approaches/impact-measurement-approaches/ecosystem-areas-for-impact-measurement) * [Contributor areas for impact measurement](https://funding.treasuries.io/approaches/impact-measurement-approaches/contributors-areas-for-impact-measurement) * [Impact measuring factors for consideration](https://funding.treasuries.io/approaches/impact-measurement-approaches/impact-measuring-factors-for-consideration) * [Priority impact measurement](https://funding.treasuries.io/approaches/impact-measurement-approaches/priority-impact-measurement) * [Idea impact measurement](https://funding.treasuries.io/approaches/impact-measurement-approaches/idea-impact-measurement) * [Contributor impact measurement](https://funding.treasuries.io/approaches/impact-measurement-approaches/contributor-impact-measurement) * [Contribution measurability](https://funding.treasuries.io/contributions/contribution-verification) * [Knowledge process](https://funding.treasuries.io/knowledge/adoption-of-knowledge-systems) * [Priority process](https://funding.treasuries.io/priorities/independent-priority-process) * [Idea process](https://funding.treasuries.io/ideas/idea-process) * [Contributor process](https://funding.treasuries.io/contributors/independent-contributor-process) * [Idea execution considerations](https://funding.treasuries.io/ideas/idea-execution-considerations) Treasury suggestion resources * [Disbursement suggestions](https://suggestions.treasuries.io/funding/funding-suggestions) * [Disbursement process considerations](https://suggestions.treasuries.io/funding/funding-process-considerations) General updates * [Information structure and wording changes throughout resources](https://github.com/orgs/web3association/repositories) **Systems & operation** * [web3association.io](https://web3association.io) - Added website overview * [treasuries.io](https://treasuries.io) - Added website overview # December 2023 Contributions for December 2023 **Contribution duration** - Full month ## **Overview** * Contribution approaches - Exploring the different approaches for enabling contributors to submit information into a disbursement process. * Voter preferences & opinions - Understanding the importance of enabling voters to express their preferences and opinions at all times throughout disbursement. * Contributor vs voter idea selection - A comparison looking at the differences between having contributors or voters handle idea selection. * Voter outcome influence - Looking at how the amount of influence a voter has on the outcome can change depending on the requirements and needs of the decision being made. * Contribution verification approaches - Exploring how the efforts made by contributors could be verified to ensure that the outcomes generated are as intended. * Incentive approaches - Exploring how and where the incentives could be attached in disbursement and the implications and trade offs of these different approaches. * Updates to all resources - Fixed a number of typos and made wording and structure improvements. ## Contribution outputs **Documents** Disbursement resources * [Contribution approaches](https://disbursement.treasuries.io/disbursement-approaches/contribution-approaches) * [Contribution factors for consideration](https://disbursement.treasuries.io/disbursement-approaches/contribution-approaches/contribution-factors-for-consideration) * [Fully combined submission](https://disbursement.treasuries.io/disbursement-approaches/contribution-approaches/fully-combined-submission) * [Idea & contributor combined submission](https://disbursement.treasuries.io/disbursement-approaches/contribution-approaches/idea-and-contributor-combined-submissions) * [Independent submissions](https://disbursement.treasuries.io/disbursement-approaches/contribution-approaches/independent-submissions) * [Disbursement process data handling](/about/roadmap/other-areas-of-focus) * [Voter preferences & opinions](https://disbursement.treasuries.io/outcome-influence/voter-preferences-and-opinions) * [Contributor vs voter idea selection](https://disbursement.treasuries.io/outcome-influence/contributor-vs-voter-idea-selection) * [Voter outcome influence](https://disbursement.treasuries.io/outcome-influence/voter-outcome-influence) * [Contribution verification approaches](https://disbursement.treasuries.io/disbursement-approaches/contribution-verification-approaches) * [Contribution verification factors for consideration](https://disbursement.treasuries.io/disbursement-approaches/contribution-verification-approaches/contribution-verification-factors-for-consideration) * [Task milestone based contribution logs](https://disbursement.treasuries.io/disbursement-approaches/contribution-verification-approaches/task-milestone-based-contribution-logs) * [Project time based contribution logs](https://disbursement.treasuries.io/disbursement-approaches/contribution-verification-approaches/project-time-based-contribution-logs) * [Individual time based contribution logs](https://disbursement.treasuries.io/disbursement-approaches/contribution-verification-approaches/individual-time-based-contribution-logs) * [Importance of contribution measurability](https://disbursement.treasuries.io/disbursement-approaches/contribution-verification-approaches/importance-of-contribution-measurability) * [Incentive approaches](/about/roadmap/other-areas-of-focus) * [Unsuitable incentive approaches](/about/roadmap/other-areas-of-focus) * [Incentive factors for consideration](/about/roadmap/other-areas-of-focus) * [Priority milestone incentives](https://disbursement.treasuries.io/disbursement-approaches/incentive-approaches/priority-milestone-incentives) * [Priority time incentives](https://disbursement.treasuries.io/disbursement-approaches/incentive-approaches/priority-time-incentives) * [Idea milestone incentives](/about/roadmap/other-areas-of-focus) * [Idea time incentives](/about/roadmap/other-areas-of-focus) * [Contributor time incentives](https://disbursement.treasuries.io/disbursement-approaches/incentive-approaches/contributor-time-incentives) General updates * [Fixed typos, and made wording and structure changes throughout resources](https://github.com/orgs/web3association/repositories) # November 2023 Contributions for November 2023 **Contribution duration** - 4 days ## **Overview** * Roadmap - Updated current roadmap * Decision approaches - Improved the disbursement approaches analysis to narrow in on disbursement decision approaches * Contribution & incentive approaches - Started planning out contribution and incentive approaches for future analysis * Disbursement resources - Updated disbursement documentation structure * Communicated with many Web3 ecosystems and offered support to help with improving their own disbursement processes! ## **Contribution outputs** **Documents** Disbursement resources * [Disbursement decision approaches](https://funding.treasuries.io/approaches/decision-approaches) * [Disbursement documentation](https://funding.treasuries.io/) - Rearranged existing resources, older links may now not work! # October 2023 Contributions for October 2023 **Contribution duration -** Full month ## **Overview** * Analysed how incentives could be used across each of the disbursement processes * Analysed how idea costs could be handled for when independent disbursement processes are used * Made improvements to existing analysis * Created suggestions for how the Project Catalyst funding process could be improved ## **Contribution outputs** **Documents** Disbursement resources * [Proposal submission incentive approaches](https://disbursement.treasuries.io/incentives/proposal-submission-incentive-approaches) * [Execution incentive approaches](https://disbursement.treasuries.io/incentives/execution-incentive-approaches) * [Knowledge incentives](https://disbursement.treasuries.io/knowledge/knowledge-incentives) * [Priority incentives](https://disbursement.treasuries.io/priorities/priority-incentives) * [Idea incentives](https://disbursement.treasuries.io/ideas/idea-incentives) * [Execution incentives](https://disbursement.treasuries.io/execution/execution-incentives) * [Approaches for handling idea costs](https://disbursement.treasuries.io/ideas/approaches-for-handling-idea-costs) * [Disbursement approaches](https://disbursement.treasuries.io/disbursement-process/disbursement-approaches) - Updated * [Approaches for developing knowledge sources](https://disbursement.treasuries.io/disbursement-process/disbursement-approaches/approaches-for-developing-knowledge-sources) # September 2023 Contributions for September 2023 **Contribution duration** - Full month ## Overview * Compared different disbursement approaches * Analysed the tradeoffs of adopting an independent priority or execution process * Discussed different impactful disbursement outcomes * Analysed the benefits of adopting knowledge systems for disbursement * Analysed different idea ownership approaches * Added some initial treasury suggestions based off the analysis so far ## **Contribution outputs** **Documents** Disbursement resources added * [Impactful disbursement outcomes](https://disbursement.treasuries.io/disbursement-process/impactful-disbursement-outcomes) * [Disbursement process information](https://disbursement.treasuries.io/disbursement-process/disbursement-operating-process/disbursement-process-information) * [Disbursement approaches](https://disbursement.treasuries.io/disbursement-process/disbursement-approaches) * [Factors for consideration](https://disbursement.treasuries.io/disbursement-process/disbursement-approaches/factors-for-consideration) * [Fully combined process](https://disbursement.treasuries.io/disbursement-process/disbursement-approaches/fully-combined-process) * [Idea & contributor combined process](https://disbursement.treasuries.io/disbursement-process/disbursement-approaches/idea-and-contributor-combined-process) * [Independent processes](https://disbursement.treasuries.io/disbursement-process/disbursement-approaches/independent-processes) * [Passive idea selection process](https://disbursement.treasuries.io/disbursement-process/disbursement-approaches/passive-idea-selection-process) * [Delegated idea selection process](https://disbursement.treasuries.io/disbursement-process/disbursement-approaches/delegated-idea-selection-process) * [Adoption of knowledge systems](https://disbursement.treasuries.io/knowledge/adoption-of-knowledge-systems) * [Independent priority process](https://disbursement.treasuries.io/priorities/independent-priority-process) * [Independent execution process](https://disbursement.treasuries.io/execution/independent-execution-process) * [Idea ownership approaches](https://disbursement.treasuries.io/ideas/idea-ownership-approaches) * [Factors for consideration](https://disbursement.treasuries.io/ideas/idea-ownership-approaches/factors-for-consideration) * [Owned ideas with fixed leadership](https://disbursement.treasuries.io/ideas/idea-ownership-approaches/owned-ideas-with-fixed-leadership) * [Owned ideas with distributed leadership](https://disbursement.treasuries.io/ideas/idea-ownership-approaches/owned-ideas-with-distributed-decisions) * [Shared ideas with elected leadership](https://disbursement.treasuries.io/ideas/idea-ownership-approaches/shared-ideas-with-elected-leadership) * [Shared ideas with emergent leadership](https://disbursement.treasuries.io/ideas/idea-ownership-approaches/shared-ideas-with-emergent-leadership) Suggestion resources * [Create a list of information sources & systems](https://suggestions.treasuries.io/disbursement/create-a-list-of-information-resources-and-systems) * [Determine how prioritisation should be handled](https://suggestions.treasuries.io/disbursement/determine-how-prioritisation-should-be-handled) * [Determine which disbursement approaches to experiment with](https://suggestions.treasuries.io/disbursement/determine-which-disbursement-approaches-to-experiment-with) * [Document the ecosystems mission, principles & values](https://suggestions.treasuries.io/disbursement/document-the-ecosystems-mission-principles-and-values) General updates * [Updated some existing pages](https://github.com/orgs/web3association/repositories) **Systems & operation** * [suggestions.treasuries.io](https://suggestions.treasuries.io/) - Setup documentation for treasury suggestions # August 2023 Contributions for August 2023 **Contribution duration -** Full month ## Overview * Setup the initial documentation websites on [treasuries.io](http://treasuries.io) * Added some initial overview resources talking about existing treasury systems and then comparing them with Web3 treasury systems covering areas such as the problems, differences, opportunities and concerns. * Created a high level operating process to help with thinking about how treasury systems operate and then applied this to disbursement to better think about its operating process. * Created further analysis about the disbursement operating process to cover areas such as rate of change, ranking of importance, delegation of disbursement decisions and complexity of the different operating processes involved in disbursement. ## Contribution outputs **Documents** Treasury resources * [Definition, purpose & responsibilities](https://docs.treasuries.io/treasuries/definition-purpose-and-responsibilities) * [Functional processes](https://docs.treasuries.io/treasuries/functional-processes) * [Importance of treasuries](https://docs.treasuries.io/treasuries/importance-of-treasuries) * [Example treasuries](https://docs.treasuries.io/treasuries/example-treasuries) * [Problems & differences](https://docs.treasuries.io/web-3-treasuries/problems-and-differences) * [Opportunities & concerns](https://docs.treasuries.io/web-3-treasuries/opportunities-and-concerns) * [Stakeholders](https://docs.treasuries.io/web-3-treasuries/stakeholders) * [Operating process](https://docs.treasuries.io/web-3-treasuries/operating-process) Disbursement resources * [Disbursement operating process](https://disbursement.treasuries.io/disbursement-process/disbursement-operating-process) * [Disbursement process rate of change](https://disbursement.treasuries.io/disbursement-process/disbursement-operating-process/disbursement-process-rate-of-change) * [Disbursement processes ranking of importance](https://disbursement.treasuries.io/disbursement-process/disbursement-operating-process/disbursement-processes-ranking-of-importance) * [Delegating disbursement process decisions](https://disbursement.treasuries.io/disbursement-process/disbursement-operating-process/delegating-disbursement-process-decisions) * [Disbursement process complexity](https://disbursement.treasuries.io/disbursement-process/disbursement-operating-process/disbursement-process-complexity) **Systems & operation** * [treasuries.io](http://treasuries.io) - Setup GitBook documentation website for general treasury educational resources * [disbursement.treasuries.io](https://disbursement.treasuries.io/) - Setup GitBook documentation for disbursement educational resources # Links & contact information * :heavy\_multiplication\_x: [X](https://twitter.com/W3Association) * :video\_camera: [YouTube](https://www.youtube.com/@Web3Association) * 💬 [Telegram](https://t.me/Web3Association) * :computer: [GitHub](https://github.com/web3association) * :e-mail: # Contributor funding operator Contributor funding operator services
Our [funding analysis](https://funding.treasuries.io/) helped to highlight the opportunity for Web3 ecosystems to experiment with a contributor funding process. A [open source contributor funding ](https://docs.contributors.org/proposal/open-source-contributors)proposal has been shared publicly to highlight the advantages of this suggested funding process. The objectives, development roadmap and setup process for trialling a [contributor funding process](https://funding.contributors.org/contributor-funding-experiment/overview) has been documented. An [example contributor funding process](https://example.contributors.org/) resource is also available to showcase what the process could look like in practice. Our suggested contributor funding experiment would cost less than $10,000 to operate and execute from start to finish. This costing includes any usage of tools and services as well as the [funding operator contribution costs](https://funding.contributors.org/contributor-funding-experiment/experiment-setup/time-and-cost-estimates). If you're interested in running a contributor funding experiment please[ reach out to us](/about/links-and-contact-information) at any time. # Web3 treasury consulting Web3 treasury consulting services
Our goal is to help accelerate the development and improvement of Web3 treasury systems and funding processes. We’re particularly interested in supporting ecosystems with improving their funding processes. Even small improvements could generate very meaningful returns on investment for the ecosystem. We're interested in evaluating any part of your funding process to help with identifying any trends, suggestions and areas for improvement. Some areas we could help with include: * **Reviewing funding outcomes** - Outcomes generated by the funding process can be reviewed to better understand what actual impact has been generated. * **Data planning** - The only way to truly know whether a funding process has been improving over time or not is to record, measure and analyse enough data. We can help with reviewing what data should be collected so that it becomes easier to make decisions about how to evolve and iterate the funding process. * **Data analysis** - Funding processes can produce a lot of data. Collecting and aggregating these data sources can help with identifying trends and creating reports about what has actually been happening. We can take this data to explore any similarities or differences that exist with other funding processes across the industry. Example areas that could be explored could include the rates of completion or fraud, stakeholder feedback and current sentiments and investigations into what the total participation time and cost estimations currently are for the funding process. * **Identifying suggestions** - Some of the most impactful suggestions we can make will come in the form of identifying low cost and high impact experiments that could be trialled in the ecosystem. Suggestions that could become long term solutions if successful. Another area of focus is to better understand what is already happening across the industry and then identify and suggest already adopted solution approaches that have already demonstrated their effectiveness. * **Industry research & trends** - We can conduct research and analysis to help with identifying any key trends about what is happening across the industry. Efforts could be focused on identifying best practices or creating new data sources for further analysis. Creating more tailored reports about more specific topic areas could also be another area of focus. If you’re interested in collaborating with us in any way to improve your treasury systems and funding process please [reach out to us](/about/links-and-contact-information) at any time.