# Abstract Releap Protocol aims to provide creators with ownership of their relationships with their community, establishing a completely composable, decentralized social network. This is accomplished by permitting users to construct profiles and engage with each other through these profiles. In this context, "Profile" pertains to Releap profiles, whereas "user" pertains to standard crypto-wallets. The protocol is designed with modularity as a fundamental concept. At present, the Releap Protocol is administered by a multisig, which will eventually transition to a broader DAO that can design, and vote on new modules and expanded features. *** ### Architecture Firstly, let's examine the creation and publishing of profiles. Users are required to establish a profile on the hub, after which they receive an NFT sequentially linked to their profile. This NFT regulates the profile, effectively making the user the profile's controller. Profile owners have the ability to: * Publish to the profile with three types of publications: * Posts, which are standard content pieces * Comments, which are standard content pieces linked to another publication * Set the profile's image URI * Set the profile's "delegator", which is an address that can act on behalf of the profile's owner by publishing to the given profile and setting its URI *** ### Tokenization Releap Protocol involves tokenzation through NFT that are fully composable. The Releap Hub upgradeable contract is the main point of entry for most interactions within the protocol. It also acts as a Sui contract for profile NFTs, which are created when a user creates a profile. *** Releap Protocol is a social graph protocol that is designed to be owned by the community and continuously evolving. It empowers its users to determine how they want their social graph to be constructed and how it can be monetized, if they so choose. In addition, the protocol is built with modularity in mind, which means that it can support a wide range of use cases. From a user's perspective, this means that they have a new way of customizing and owning their social graph, which would not have possible or affordable with Web2 technology. --- # Agent Instructions: 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://docs.releap.io/releap-protocol/abstract.md?ask= ``` 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.