TightKnit

Our goal is to weave meaningful relationships, so that a trace of them may endure forever.

TightKnit

Created At

ETHGlobal Prague

Project Description

Our app is aiming at promoting the data persistence and decentralization of web3 to new users, by focusing on preserving and celebrating important relationships in our lives. The app itself will connect (for now) two users, be it a couple or friends in an interchangeable game of saving precious memories on-chain (with off-chain decentralized storage for larger data packets). The users will take turns posting memories/photos/posts that they each shared or good deeds that one did for another. With the help of AI *-to-image agents these memories will be transformed into a unique visual story, representing and reimagining their relationship’s important moments that will remain in their shared possession for as long as they would like. The aim is to show that relationships take work and mutual engagement and cooperation, which in today’s more individualist world we sometimes forget. Idea was to represent this concept by a scarf that gets longer and longer, each time one of the users adds a new patch to it. Slowly we would add more and more customization, so that users will feel that the scarfs are really their own and unique. At certain milestones they will have a chance to create a pair of NFTs (socks) that will be generated using all the previous patches and giving them two unique pieces of a whole that could be shared and exchanged between different users of the app. Random combinations could push people to interact more in the wider community on our app and not just with their close friends/partners. In the future the goal is that these two pieces (NFTs) could be combined, creating new combinations and wacky pieces. In the future there could also be the possibility of an online shop, selling merch that is created from the NFTs in user possession, porting their web3 interactions into the real world. Patches should be exported as cross stitch design or SEW files.

How it's Made

We wanted to create a react-native(expo) Dapp and we can say we regret our decision. Unfortunately web3 integration for mobile development is really yet there, where it would be a project for more novice developers. Contracts were written in solidity, built with hardhat and ignition. We decided to to deploy on Flow-EVM testnet, since we were convinced on their presentation about low fees, but we were a bit afraid to make a project in cadence since it would be a completely new experience. There are 3 contracts on the “backend” side, each of them is made for creating and managing its own type of NFT token, which are all interconnected and nested. For example our SCARF Token built with ERC721(they all are) serves as kind of a root node for all the interactions between two people, holding mostly settings for the interaction logic. They are also just stored on the contract and all the decisions must be made and agreed by both parties (even though for now, just the creation logic is fully horizontally managed). Our MEM or memory tokens serve as the name says memory holders. On the frontend they are represented as embroidery patches, holding the ai-transformed pictures. pictures are stored on IPFS via lighthouse. And Lastly are our ACH or achievement tokens which are given for free when users reach certain milestones. They are always minted in pairs and given to both. They are completely on-chain base64 encrypted, utilizing FLOWS low gas costs. A lot/most of the assets on the frontend side were drawn and curated by our member all during the hackathon, as well as the images that stability.ai with their style-transfer model. The contracts are fully functional and deployed on testnet for now, unfortunately we didn’t have time to deploy our frontend, so for now it only works with development tool expo go. notice: most of our work was done on our Develop branch.

background image mobile

Join the mailing list

Get the latest news and updates