Harnessing Decentralization's Avant-Garde
ICE CUBE distinguishes itself by granting users control over their own canister to store all information, ensuring no external interference. Users exclusively interact with their own canister, enabling a seamless and rapid experience, unaffected even during high user volumes. ICE CUBE also features an open database, allowing anyone to freely query any data, breaking away from the data silos seen in Web2 applications.
On another note, ICE CUBE incorporates a unique incentive mechanism for creators through the Bonding Curve. ICE CUBE tokenizes posts and publicly issues them, providing returns to purchasers.
Essentially, every post can be "tokenized," with tokens issued in a manner akin to fungible tokens, where the price of each share gradually increases with the quantity purchased.
By offering contributors an expected return on investment, ICE CUBE encourages spontaneous early donations to valuable public goods. The entire process of asset issuance and returns is governed by smart contracts, ensuring transparency and openness.
Introduction to technical architecture
ICE CUBE embraces the Actor model, continuously exploring technologies for decentralized application (DApp) built entirely upon Actor model principles.
The foundational unit of ICE CUBE is the canister(Canister is the Internet Computer’s smart contract), a concept we believe aligns synergistically with the Internet Computer. DApps constructed upon this architectural paradigm may emerge as the prevailing norm, unlocking myriad possibilities for innovation derived from this powerful concept.
Detailed description of technical architecture
ICE CUBE incorporates modular design, an open database, user cloud terminals, and a creator incentive mechanism.
- Modular Design: Categorizes canisters based on functionality, each with its designated role.
- Public Database: An open database allowing anyone to directly publish and access content.
- User Cloud Terminals: Each user possesses their small independent server (canister), offering on-chain private services.
- Creator Incentives: Assigns "tokens" to post, distinguishing outstanding content.
Its architecture is designed based on the actor model provided by IC. Decentralized collaboration among canisters facilitates information flow, with users needing only to query canisters for all relevant information.In essence, users interact solely with their own canister at the frontend, leaving subsequent collaboration tasks to be gradually completed by the canisters.
We create a Feed canister for each user to store their personal information flow, serving as their private space. Users can save posts in their own canister (Feed canister), and no one else can delete them besides the user.
Interactions between users and the public area are automatically handled by the Feed canister. Users can simply query their Feed canister to obtain the latest information flow from those they follow. Posting, commenting, and liking interactions are also automatically completed by the Feed canister in subsequent operations.
Overall, ICE CUBE can be divided into four modules: User, Feed, Post, and Fetch.
- User canister: The user zone responsible for recording user information and relationships. It stores user profiles and follower relationships.
- Post canister: The public zone that stores all publicly posted content. The Root Post canister can create numerous Bucket canisters to store posts.
- Feed canister: The information stream storing a user's personal information flow. The Root Feed canister creates a Feed canister for each user.
- Fetch canister: The intermediary station responsible for pushing the latest information flow of a specific user. It records posts, comments, or likes that the user's Feed canister has not fetched.
Users can also incorporate advanced custom features by deploying an independent Feed canister to interact with the public zone. For example, sending posts point-to-point to specific Feed canisters to create private social circles or connecting to AI for automatic posting. Any functionality is achievable, with the community having the flexibility to develop and expand various features, such as adding a point-to-point private messaging feature.
The advantage of this approach is that users only need to query their Feed canister to access posts from those they follow. It is convenient, swift, and all backend processes are decentralized collaborations between canisters, completely decoupled. The system continues running even if several canisters go offline.