Built as a part of ethOnline 2021. Planned releases on emptyyourmug.com and pullmythread.com with tampopo.eth serving as the web3 gateway.
Overview
Ever seen Harry Potter? There is a scene where Albus Dumbledore uses his wand to remove a memory from his mind to empty into the Pensive. Tampopo does exactly that, but with all the benefits of web3, ie, it incentivises you to outpour your stories [read: empty your cups] onto the platform. The stories are represented as the balls of coloured yarn that they usually are, by having them displayed in the form of interactive, clickable links. As the reader clicks, parts of the story are revealed. Think of it as pulling the threads of the yarn ball, and as the reader pulls more, you earn* more; because web3.
How it works*
*will work
A lot of merkle trees essentially. The network is built as a L2 sidechain with optimistically mined tokens being rolled up on NFT purchases on mainnet. Core [read: old] web3 projects are* used (ethereum, ipfs, the graph, rarible) along with some from the hackathon sponsors (superfluid, ethblockart, web3.storage) for enhancing user experience. More interestingly, and in the future, integrations with OpenAI, for convenience and UX, and NGOs, for storyteller assistance (think whistleblower, activism, etc.) are planned. The project is also designed to be modular, so highly extensible and customisable, and accessible, ie, easy and less code, well informed docs, etc.
Repository Details
Three main branches, in increasing order of technical prerequisites [read: lower accessibility] —
i. takeoff : the release branch, where users or visitors stumble upon
ii. land : the staging branch, where public users are invited to test new features
iii. runway : the master branch, where devs are invited to test new features
iv. hangar : the dev branch, where devs actually do the dev
Current Interesting files
All files in /docs are laboriously written for the reader's convenience. They serve to provide an overview of the project, the network, and its protocol parameters, from the design inspirations to the nitty gritty numbers. Any and all constructive feedback on the docs would be greatly appreciated. The next two steps is to build and release 0-hack.1-main.0, along with 0-hack.0-docs.z by the end of the hackathon.