# Cabin Meeting Questions

1) What is "Census" (We do know what "a census" is, but is "Census" software? a DB? something else?)
2) An individual profile is a passport, the census is the collective of passports
3) Confirm assumptions for art requirement for roles (assume it means design collateral)
4) Confirm assumptions for discord landing pad (assume it means special automated channels)

## Cabin Vision

* **Epicenter dApp**
*Aggregates data from*:
* Web2 Off-Chain Data
* Cabin Token
* Hats Protocl
* Otter Space Badges

Trying to build a member directory web app that aggregates all onchain token data sources + offchain data into a single place that represents membership in the dao.

One layer is extremely decentralized: tokens; Cabin, Role NFTs, Passport Stamps. Composable onchain data sources

One layer is offchain, private information that we want people to add on.
Comfortable with web2 offchain shtuff.

## Raidguild Engagement Requirements

What they need help with is implementation of the web app.

- Front End
- Sign In With Ethereum
- Consumes & Interacts with Hat Protocol
- Consumes & Interacts with Otterspace Badges
- Consumes & Interacts Cabin's Token
- Integrate with custom backend
- Design Spec provided by Cabin
- Specific Features
- Token Gate content to exclusively Cabin Token holders
- Twitter-like PFP (Select Held NFT or Upload custom)
- Display ENS/Address when connected
- Display Role (Provided by Hat Protocol)
- Display Badge Collection (Provided by Otterspace)
- Display Cabin coin holdings
- Display Fellowship data
- Multiple Feeds (Governance, All Activity)
- Back End
- User Profiles
- Recommended Supabase for reduced Back End maintenance costs
- Profile Picture
- Contact Information (Email, discord, telegram, wallet)
- Bio, interests, experience, neighborhood affiliations
- Job Offers
- Neighborhood
- Task
- Pay Rate
- Poster (User)
- Contact (User)
- Service Offers
- Neighborhood
- Skill
- Pay Rate
- Post (User)
- Contact (User)