TaleVault

Demo

About

The problem it solves TaleVault empowers creators to directly connect with audiences, build loyal followings, and monetize their work by minting narratives as NFTs. Creators can choose the blockchain network for payments, set prices, and define genres and POVs. TheGraph Client continuously monitors token metadata events, ensuring seamless updates in the "View POVs" section until a publisher purchases the token. ghts to develop the narrative into content like videos or animations. Publishers use Lens Profiles to manage their activities, including following others, posting, and commenting. To post content, they select the associated NFT, upload files to IPFS, and generate content metadata. Pinata’s PinToIPFS service creates a contentURI, which is published on-chain via Lens's `postOnchain` method, forming a Lens Publication linked to the publisher's profile. Viewers log in with their Lens handles to explore content, view the original POV in markdown format, comment, and vote for their favorites. These interactions incentivize both creators and publishers, promoting engagement. TaleVault's DAO framework fosters community-driven governance, enabling creators, publishers, and audiences to collaboratively shape the platform's evolution. This decentralized approach ensures a transparent and inclusive ecosystem for content creation and distribution.

How it's made

Challenges we ran into **CCIP Integration with Hardhat** Initially, we encountered issues while importing libraries and deploying contracts in Hardhat. However, by referring to the Chainlink documentation, we resolved these challenges by configuring the appropriate network settings and installing required packages such as `@chainlink/contracts` and `@chainlink/contracts-ccip`. **Lens Client** The documentation initially pointed to `@lens-client@alpha`, an outdated version using Polygon Mumbai, which is now deprecated. After exploring the npm repository, we identified `@lens-client@latest` as the appropriate version for Polygon Amoy. **Lens Profile Manager** We were unaware that activating the Lens Profile Manager was necessary for creating publications or following users. Through further research and a deep dive into the Lens documentation on *Gasless and Signless* transactions, we learned that enabling the dispatcher is essential. Before processing any transaction, it is crucial to verify that the user's profile has this functionality activated. **Lens PostOnChain** For submitting a publication as a post, we initially misunderstood the requirements and used the file's IPFS URI directly. We later realized that the correct approach involves pinning the metadata to IPFS and attaching the metadata URI, not the file URI, to the publication.