> For the complete documentation index, see [llms.txt](https://chainedx.gitbook.io/chainedx-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chainedx.gitbook.io/chainedx-protocol/6.-conclusion.md).

# 6. Conclusion

 The whitepaper has proposed a protocol for creating a unified, universally accessible, decentralized social graph and an associated ecosystem of software services and applications. A modern social media company is highly complex, with many different components requiring a wide variety of deep expertise. From technical components such as software clients, caching services, and recommendation engines,\[13] to more businessoriented concerns such as moderation, advertising sales, and regulatory compliance, each piece is a critical component of the network. This protocol enables coordination between services to build the complex ecosystem required to sustain modern social media without the liabilities of centralization. The next step is to create a comprehensive protocol specification leveraging the significant technical work already in progress. 

Creating a complete system with so many components can be difficult but not impossible as technology tends to improve exponentially when all functionality must occur inside a single organization. By unbundling the social network, an entire ecosystem can be created to operate at the scale of global social media and allow a diverse array of experts to address the pressing challenges created by malicious actors in the network. With a public broadcast model of protocol events, new services can be created to provide simple interfaces and data layers to create and consume data. These SaaS (Software as a Service) tools can provide an infrastructure layer that clients can leverage in unique combinations for different use cases. Figure 8 illustrates a hypothetical ecosystem of independent components that leverage the protocol to create a complete social networking system. 

A diversity of approaches, leveraging the interoperability of common data formats and discovery, minimize the effort to create new experiences. Graph indexing services can take on the load of parsing and storing graph events from the blockchain to provide easy access to graph data, including mechanisms to handle encrypted events. Content indexing services can enable content feed building, message threading, search results, trending topics, or caching, and, since all Announcements provide the information needed to authenticate the content, can combine trust and convenience. Content moderation and fact checking can be provided by multiple separate services for different use cases or interest groups, enabling more reliable, comprehensive, and transparent moderation. Given the open nature of the network, developers can offer different revenue models that can exist side by side, such as advertising, subscription, or direct payment, while allowing all experiences to interoperate directly.

<figure><img src="/files/BrMQ2clAGr78FsuP4DyP" alt=""><figcaption><p><mark style="color:yellow;"><strong>Figure 8: SaaS Ecosystem</strong></mark></p></figcaption></figure>

The protocol allows for the same underlying information to be available to everyone independent of intermediaries. Separating responsibilities encourages competition while better aligning incentives with user interest. The range of possibilities is difficult to predict, but by ensuring user data ownership and decentralizing the interaction model, the protocol allows for an entire ecosystem of participants to innovate and flourish.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://chainedx.gitbook.io/chainedx-protocol/6.-conclusion.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.