> For the complete documentation index, see [llms.txt](https://docs.berrystore.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.berrystore.net/berry-4.0-architecture/podr-smart-algorithm.md). # PoDR Smart Algorithm The key algorithm of Berry 4.0 is the PoDR(Proof of Donation Relationship) smart algorithm that connects online relationships through P2P personal BERRY coin transactions. PoDR algorithms are the most transparent proof of relationships to solve the problem of unproven vertical following of traditional centralized social media. In particular, existing online relationships do not form any link factor due to random connections that have no proof, and remain only in one-sided vertical relationships by top followers. This vertical relationship is dependent on the top influencer, making it difficult to maintain its influence as a sustainable platform over time. ![](/files/fApu0sKzQGtWYxYZh3KN) The PoDR smart algorithm is largely divided into Berry 4.0 Auth server, Contents server, Following server, and Blockchain server. The linkage of each server group is based on the blockchain transaction hash value, including the recently generated new data, and all records performed on and off-chain are processed so that cannot be falsified in real-time validity between servers and databases is adjusted. In particular, Auth and Content are converted to userId and references values, which are the criteria for the first consensus, and the Auth state is changed to Giver(Follower), a BERRY coin donor (or sponsor), and finally approved to the Following Server that handled the P2P relationship. At the same time, connecting the relationship with the Taker(Following), who be donated(or be sponsed), and converts the result of the relationship in to a hash value and records it in the final blockchain. Therefore, the interrelations recorded in the blockchain are strongly dependent on as the eternal relationship. Berry 4.0 to develop our own smart algorithm at first to establish as a media platform that leads the future-oriented Web 3.0 decentralized social donation culture. Beyond traditional Ponzi-type mining techniques, the PoDR algorithm sets the criteria for proof in an online user-to-user relationship, and demonstrates the relationship clearly through free individual donation/sponsorship transactions and establishes a strong connection between users. This berry-connected relationship can be merged with uploaded donation content to lead to the popularization of donation culture. The final intent of the PoDR algorithm is to: * In order to increase my follower (Giver), continue to produce donation activities contents. * Sponsor by BERRY(Taker) to connect with users who produce continuous donation activity content. * Users participate actual donation activities in daily lives to connect more relationships between donors. * Activate the Berry Economy through mutual BERRY coin donation (sponsorship). * Berry Foundation only provides a playground(platform) for donors and does not control their relationship. * The ultimate goal is to form a community of global donors and those who support them. --- # 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, and the optional `goal` query parameter: ``` GET https://docs.berrystore.net/berry-4.0-architecture/podr-smart-algorithm.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.