Wis3

Decentralised course platform, people can create, sell, buy course all in decentralised ecosystem. It allows seemless integration among SDK.

Refunds can be held by any centralised authority or instructor. To handle this we made a DAO with a twist. Twist is that not every vote is equal, the person who has reached further in course has higher vote weightage, giving an emphasis who has more data.

But how does the data in tamper proof? Well answer to that is that the timestamps is not generated by the user but by a backend server. In ComposeDB only the creator the data can modify it. So it prevents from tampering of data/certificates. The data/certificates to help users. We also used an existing data model basicProfile. Dao inherits this model so to have a better understanding

Aim is not only to help students to the content creator with help of Soul Bounded Tokens

We also proposed a solution so that course authors can conduct token gated livestreams thorugh Huddle01. Ceramic, Lighthouse.Storage, Huddle01 fit seemlessly. Data interoperability is the key in web3!

It is made with the help of Ceramic, Huddle01, Lighthouse.Storage. Thing I used Ceramic differently as to create content for the front-end. Rendering dynamic websites just got easier. A simple GraphQL all it takes.

As course-content creator we needed a service to share screen as well as record. Huddle01 suited our requirement.

Lighthouse.Storage was really helpful from encrypting roomID to entire video and token gate them.