# DB+TW Sprint

## Context

### What is Pokemol and what happened with v1?

- Started with Pokemol v1
- Tech wasn't quite there
- Skills weren't quite mature
- Users didn't want it!
- Didn't see the value in account abstraction, was watering down the web3: self-custody
- Wanted to use Metamask wallet on desktop
- Now tech has changed
- New self-custodial wallets using browser and OS for encryption
- New web3/web2 hybrid auth flows
- Users now want more mainstream (web2-esque) onboarding flows

### Where did the Reboot idea come from?

- Users asking for better UX
- Users want mobile-first
- The DAO feature set opens up lots of opportunities for new tools

### Pokemol Core Features

- Mobile-first Moloch DAO summoning
- ⭐️ **Accomplished through a PWA** (progressive web application)
- We should avoid building native apps, problems with providers: fees, ownership, less dependencies, better for open source, reduces maintenance if built for platform agnosticism

### Inventory of Primitives
All the moving parts considered in Dekan's design


- TCR "Signal" app
- Demos:
- Summoner
- Admin
- DUCE (decentralized universal comment emitter): A commenting primitive
- Yeeter: A crowdfunding primitive than onboards supporters to a DAO
- SILO: Retroactive DAOification for NFT projects to join a DAO
- Token related stuff
- Snapshot using Moloch loot tokens (TCR, soft veto)
- Fixed loot: fixed total supply instead of continuously minting (AMM stuff).
- AMMs provides a token trading pair. Price emerges from their fixed relation.
- Bonding loot: A curve between loot share supply and market demand to automate price
- Delegate Manager: unilateral control of treasury
- Products:
- DIN: publishing
- Yeeter: crowdfunding
- SILO: NFT onboarding
- New Pokemol: mobile access to the whole suite of apps?
- Web3 Reddit: an evolution of the DUCE primitive
- SigSesh: an evolution of the TCR primitive with a business model
- Admin Pro: an evolution of the Admin app with business model
- Summoner Pro: evolution of Summoner app with a business model

### DIN
Details of how some of the parts connect to for a community. At a high level, a group of content creators mint their work as NFTs. Collectors purchase the NFTs and serve as governors of a DAO formed around speculating on the content, which launches a token. Speculators buy the token, which also carries loot shares to the DAO. Token holders are able to comment, upvote, and downvote on new meme ideas. This has the potential to set off another flywheel to start the whole process over again.


- A top level curator DAO
- Any kind of content can be made by the community
- DIN DAO determines if its publishable or not
- When published:
- the author gets an NFT
- collectors can buy the NFT: split between DIN DAO and the authors
- split can be determined by the community
- While collectors buy the article, outside speculators are motivated to buy the meme token
- meme token on a bonding curve
- A new DAO is formed around the meme token community (speculators)
- MEME DAO receives a txn fee for selling/transferring. Fee goes into the MEME DAO
- Collectors are voting (member) share holders and Meme token holders are non-voting-share (loot) holders
- Loot holders can participate in DUCE, upvoting and downvoting in a conversation. Community memes emerge from this participation.
- Loot holder can participate in a token-gated forum channel. New memes that are generated in the forum have the potential to become new content, publishable into a new DIN/author DAO, to start the flywheel all over again.

---

# Convergence

## DUCE

- Competitive Analysis (async)
- Technical description of how it works: will help separate the protocol from the product
- Problem
- Persona
- User Stories

Goal: generate all the content we need to generate lo-fi wires

### Necessary Metadata

- Content
- Title
- Description
- External Link
- Tags
- Author
- Time
- Parent Node: Ref
- Category: Ref
- Version
- UUID
- Hash (to verify the author)

## DIN

- Competitive Analysis
- Start by reviewing Dekan's rage hack
- Problem Statement
- Personas
- User Stories
- Review Typtos Figma UI

Goal: TW will go home and make a new UI

## Signal App

- Competitive Analysis
- Review current v1 mvp: figure out whats there and whats missing
- Re-skin the UI: TW will modify, DB will execute
- UX interviews and feedback sessions:
- DH family first
- RG extended family next
- Supplemented by frens from outside our walled garden

#### Potential Feature Roadmap

- On-chain action:
- If a DUCE can do a multicall. The results of a signal session distributes funds, redistributes shares, etc. Using the Tally function.
- Use case: election. Public Haus could use it to elect champions. Signal Sesh > Tally to execute.
- AI / chatGPT integration:
- Use of-chain tally functions
- Create an index of all the content from a signal/retro session. UI allows users to query the index with specific questions to receive meaningful answers.
- Auto generate a scaffolding/outline for the composition of a piece of written content.

## Autopoietic Economy (Whitepaper)

- DH community to come together to sprint on sustainable economics for our ouwn protocol and product roadmap
- Combines elements of CCR
- with PCO is a strong references
- DIN has its own economic ideas
- LP DAO: create liquidity, create yield rewards, reminds DH members to consider sustainable economics in everything we do
- Is DH a platform? A protocol? A product launcher? A community?
- Connected to a revistation of our vision and values as a DAO
- Having strong declaration of our committment sustainability would support everyone's collective and individual endeavors

---

# Notes Generated from the Transcript

## Transcript 1 Organization and Analysis

**Participants:**
- TW (Travis Wyche)
- Dekan (Dekanbro)

**Discussion Summary:**

#### 1. Origins and Evolution of Pokemol
- **TW Initiates Discussion:**
- **Topic:** Pokemol reboot, initially conceptualized as a mobile-first UI for DAOhaus (Pocket Moloch).
- **Background:** DAOhaus evolved from the idea of launching Moloch DAOs through Pokemol.

- **Dekan Expands on Pokemol's History:**
- **Initial Version:** Aimed to create wallets in-browser for a user-friendly PWA (Progressive Web App).
- **Challenges:** Technical limitations led to issues like losing wallets.
- **User Feedback:** Initially positive, but users later preferred using their Web3 wallets for transparency and security (e.g., MetaMask).

#### 2. User Preferences and Technological Limitations
- **Dekan on User Feedback:**
- **Web3 Native Users:** Preference for transparency, self-custody, and familiarity with Web3 practices.
- **Challenges with Abstraction:** New users didn't value the abstraction; existing users preferred existing Web3 tools for their security and history.

- **TW Inquires About User Feedback:**
- **Focus:** Understanding why users preferred certain features (like MetaMask) and their views on the abstraction of Web3 elements.

#### 3. Revisiting Pokemol Concept
- **Dekan's Perspective:**
- **Evolution of Technology:** New solutions for self-custodial wallets and hybrid Web2-Web3 flows.
- **User Trends:** Shift towards more mainstream, mobile-first interactions.
- **Middle Ground:** Balancing Web2 familiarity with Web3's distinct features.

- **TW Suggests Focusing on Core Pokemol Features:**
- **Current Objective:** Identifying and differentiating the core features of Pokemol from additional features.
- **Importance of Mobile-First Approach:** Emphasizing Pokemol as primarily mobile-centric.

#### 4. Core Features and Framework of New Pokemol
- **Dekan on Pokemol's Core Features:**
- **Importance of DAO Framework:** Core features facilitate the creation of new, diverse products.
- **Experimental Nature:** Core features are still experimental and need refinement.
- **PWA vs. Native Apps:** Prefers PWA for broader compatibility and avoiding dependencies and market restrictions.

- **TW Clarifies Pokemol's Functionality:**
- **Core Functionality:** Inquiring whether Pokemol is essentially the DAOhaus SDK and its apps optimized for mobile users.

**Conclusion:**
- The discussion centered around revisiting the concept of Pokemol, understanding user preferences, technological advancements, and identifying the core features crucial for its reboot. Emphasis was placed on creating a mobile-first experience while balancing the distinct needs of Web2 and Web3 users.