Overview
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.
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 ID 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.
- Mirrors, which are comparable to traditional "shares" as they contain no content but instead refer to another publication. As comments and mirrors comprise references, they trigger the "reference module" logic of the pointed publication, if any.
- Set the profile's "follow module," a logic contract that determines what occurs when a wallet attempts to follow the profile. For instance, some followers may be required to pay a fee to the profile owner via the fee follow module contract.
- Set the profile's image URI.
- Set the profile's "dispatcher," which is an address that can act on behalf of the profile's owner by publishing to the given profile and setting its URI.
Standard wallets can:
- Follow profiles, which triggers the profile's "follow module" logic, if any. Following mints the wallet a "follow NFT" that is exclusive to that profile and is sequentially ID'd. Profile owners can set a custom URI for follow NFTs.
- Collect publications, which triggers any logic contained in the publication's "collect module." If the publication is a mirror, this process is performed on the original mirrored publication with a referral. Collecting mints the collecting wallet a "collect NFT" that is unique to that publication and is sequentially ID'd. Collect NFT URIs point to the URI of the collected publication.
Releap Protocol involves tokenzation through NFT that are fully composable and comply with OriginByte standards.
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.
When a publication is collected for the first time, a unique
CollectNFT contract is created for that publication through minimal proxy cloning. This contract represents the collected publications and is also a Sui NFT.It's important to note that follow and collect NFT contracts are only created upon the first follow or collect, respectively. This helps reduce gas overhead for profile creation.
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 been possible or affordable with Web2 technology.
Last modified 1mo ago