Saga-Poa

What inspired us

For creators, there’s nothing more powerful than a fan and what fans crave most is meaningful interaction and connection. Almost all creators host in person or live streamed events, which serve as a vital element to drive creator-fan connection. Another key driver of creator-fan connection is rewarding fans for investing in supporting creators which can be anything from redistributing the creators' content to collaboration and co-creation.

We believe that incentivizing and rewarding proof of attendance and proof of achievement (POAA) will increase creator-fan connection through co-creation, co-distribution and co-monetization.

We know that fans find engaging with their creators intrinsically valuable and we believe with the right features we can magnify their drive, turning it into both a revenue and redistribution channel for creators. Fans want equity and rewards for being loyal fans and supporting their creators.

We want to create a mini Proof of Attendance / Achievement product as part of the ICP Hackathon that would live inside the Sagaverse app. The product would be two sided:

serve event or challenge creators with a basic CMS for creating and managing event attendance or challenge completion.
Allow users to check in at events or complete challenges to receive an NFT reward.Additionally POAA (Proofs of Attendance or Achievement) serve as digital mementos and collectables.

Detailed Description

Proof of Attendance / Achievement can be seen as the same thing because they it involves:

a) setting up criteria that a user has to meet b) checking to see that relevant criteria are met c) issuing an NFT reward

How we built it

By combining multiple systems, and leveraging on the Internet Computer blockchain, we’re able to store important data on the chain.

We started out with trying to get the libraries running in the React Native environment(for iOS), and spent some time playing around with Motoko and doing local development. As we got more familiar with both the dfinity/agent-js libraries and the Motoko language, aswell as canister, we started fletching out more of the smart contract Canister. We then went to the next stage, which was connecting the external backend(Azure + Amazon S3 for simple file storage), the canisters and the React Native frontend into one. We then deployed the smart contract canister with the asset canister(Internet Identity ‘proxy’ for mobile auth), and started doing actual transaction of data between the app and the deployed canisters.

Challenges we ran into

The main challenges we ran into was figuring out workarounds for the technical cases where the React Native environment was missing in typical browser functionality. More specifically these cases: - BLS Signature validation(Slow, requires WASM as well) Using Internet Identity in an in app browser, and being able to fetch and use the identity with the dfinity/agent library. There was also multiple minor technical difficulties, most of them were resolved through using the forums.