World Attendee

This project started from the idea of creating a decentralized, permissionles hub for the Web3 ecosystem, with easy event discovery and embedded proof of personhood for authentic community connection.

Once you scan the QR code and open the World App, the latest version of the project features the following:

(included in the navbar):

• Events Dashboard, with a filter system, and display of Featured events, as well as all the other events. There are also "World Approved" events which are meant to mark where the World team will be attending.
• A "Contribute" page, which is in the works for enabling all users to submit their own event.
• A Bookmarks page, where users can find the events they are interested in, (have "saved")
• A "Profile" section, which is to be expanded for users to customize their profile details (image, name, etc)
• An admin section, where the admin is able to manage the existing events, as well as create more new events, either as drafts or to be published immediately. These can be marked as featured, "World approved".

The initial step for starting the project was using the public template wld-mini-apps-101, and initializing everything needed using the MiniKit - World App SDK.

Up until the "admin detection" commit, there was even broader functionality than in the current version. (https://github.com/iwimarin/World_Events/commit/173d1a6f803652dfa4d18aa0623aa0630eaca4ef) What changed is the decision to move from ngrok to vercel, as the miniapp was not loading anymore and it was impossible to check the build; however, this proved to be a major setback, as most of the project was already set up and properly working otherwise, and the change to vercel broke this functionality.

Particularly, logging in using WorldID within the miniapp, and the admin panel (which had the functionality of creating and editing new events, once the user was recognized as admin). From the admin panel, users were able to add new events, edit events (change details, mark as World Approved, as featured, etc)

The plan was to allow WorldID-verified users to create an event, then only after the event received 10 "approvals" from other verified users, for the event to be published on the platform.