The problem COMET solves

In the context of shared experiences and today's forms of collaboration (co-working, co-founding, co-living, co-riding), we realized that co-writing is missing.

A creative, shared experience in this field, with the possibility of monetization, would meet an emerging need. With today's technological access, everyone is becoming a creator, and it's time for this to happen collaboratively in the writing domain as well, where co-creation and co-monetization are currently lacking.

We believe that co-writing with peers fosters shared knowledge, playful creativity, and diverse perspectives. It enhances social interaction, creates lasting memories and unique stories, relieves stress, and sharpens communication skills.

Overall, the COMET project makes co-writing more accessible and inclusive, contributing to new forms of expression and enabling fair co-monetization by hosting this process through innovative and incentivized social media tools in a decentralized manner.

Challenges we ran into

• We spent some time trying to understand why the frame example on onchainkit’s docs page was not working. We created an issue and opened a PR (https://github.com/Zizzamia/a-frame-in-100-lines/pull/18) with the fix, but it was not approved yet.
• Importing onchainkit directly to our NextJS project did not work at first because of conflict between the Javascript module type in use and the expected one by Onchainkit. We solved that by creating a package to isolate onchainkit and then used it indirectly through the package.
• We spent some time until we found an effective local dev environment for the development of the warpcast frame for our Dapp. FrameGear did not handle transactions. Warpcast validator required use to use ngrok to expose publicly a local frame server. Fortunately FrameJS has a debugger that handles onchain transaction and also works with a local frame server.