dApp: Event management system (for gno launch party)

[moul]

We need an event management system to organize Gno events, starting with the Gno Launch Party. This issue is critical for the launch party and serves as a blocker alongside launching the chain.

Let's analyze existing systems (e.g., lu.ma for web2, and web3 alternatives) and define specifications for an MVP.

Submit your findings and a proposed architecture in plain English or pseudocode. This includes:

• Event creation/configuration with multi-role support
• Event discovery and reading ("live", upcoming, archives)
• Ticketing
  • free via invite or by request
  • CB-powered (dApp: credit card payments for minting tokens #3483)
  • custom: like automatically distributed by a contract when finishing a CTF/hackathon)
• Speaker profiles integration (e.g., via r/profile (feat: r/profile dapp #1983)?)
• hybrid POAP-style system considerations for newcomers (dApp: hybrid POAP-like token system #3486)

Let's discuss the proposals and refine before implementation begins.

[zxxma]

Just to give visibility, on our side (Teritori core team) we already studied and started a product fitting with this need.
We'll continue our works independently, since our scope and vision is probably larger than described here.

Basically, we want to address our own needs first (Paris P2P Festival, Samouraï Film Grants, Samouraï Parties, several small meet-ups, Alternative Music/Club gigs, Rave Parties, and all kind of events we organize for years), and then make this product available for all, including progressively most of our gno core contributions (DAO management tooling, etc.).
We believe it could be a great way to demonstrate and use most of our past works/tools/realms for communities.

Our goal is also to make it mainstream compatible, professional organizers, and not only for Gno friends.
Maybe our works could fit with this, or not, so obviously we'll be glad to share it once we're ready!

[moul]

Sounds awesome, we can probably find a way to reuse parts of your work.
Let's try to see how we can work together, maybe?

[JJOptimist]

I think the most popular combination used by event organizers is Crypto Nomads with Luma. Crypto Nomads serves as an easy way to discover and find a specific category/type of an event you are interested in which redirects you later to the official Luma page of the event where users can sign up for the tickets. It would be much better to have one solution for both with a built-in POAP system using GRC721 for example. I'm interested in the product Teritori team is building.

[zxxma]

Research Report status:

Our team made a first internal hackathon with one target:

• Build an MVP of a simple and basic event ticketing product fitting with our needs.
• Make the experience radically simple for both organizers and participants to register
• We abstract the gno wallet creation for them, and they can just register to an event with an email
• We wanted to make it as a standalone product rather than a Teritori OS feature, to avoid too much complexity, and experiment for the first time the "product rush oriented" approach. (new stack, laser focus on user experience and real life concrete use case). It's 100% built by the same Teritori task force team (Samouraï Coop dev crew), but we make it independent for easier "product" focus.

MVP Architecture:

• Nextjs frontend and a go monolith as backend
• Our front end use onchain datas only
• The current source of truth for business logic is a centralized database but users and events are deployed as DAOs on a custom gno network and all actions are replicated on-chain. This allows us to iterate fast (especially before gno mainnet) without thinking about on-chain backward compatibility. We can thrash and recreate all the on-chain data at will.
• Our admin address is admin on all DAOs and users for now to allow gas-less interactions but in the future organizers and users can reclaim full control over their accounts and DAOs. When an user participate to an event, an abstract account is created and is added on the event DAO with the participant role.

Product Demo:
https://zenao.io/event/5

Product Manifesto:
https://zenao.io/manifesto

---

Context:
Since we finished this first step, we freeze cause we currently want and need to remain focus on gnocore contributions and priorities for betanet and mainnet scope (GovDAO implem proposal, gnovm, etc. - details here -).

---

Next Steps:

Pro Events

• Paid Events
• Connect your Stripe Account
• Generate POAP

Organize your events crew:

• Customize your Gno Organization and Gno User Profile
• Manage your Organization crew & community on Gno similarly to a Web2 experience
• Manage your Organization funds
• Make your Organization tracking transparent
• Allow simple community votes and polls
• Create custom and modular Organizations levels (ex: an organization can manage several events with its own DAO model)

[n2p5]

@zxxma and @JJOptimist , thank you both for your input. I'm working on some project planning proposals around how we could approach these projects in parallel. I'll also give feedback on other system requirements that have come up with various stakeholders, but I think we should keep the ideas coming in the meantime.