0xhabitat/kiezdao

Tool sharing and rental app for local communities

kiezdao's Issues

Create reputation_system.md and community_fund.md

Bounty

Describe the content and functionality of a reputation system and of the community fund.

Scope

• set up md file and images for better explanation
• link to files if each of them is mentioned in the other documents

Deliverables

two .md files explaining each concept

Gain for the project

Better understanding of our USP and our ideas of digital tribe/community.

Roles

bounty gardener: @MaxKuck / 10%
bounty worker: @MaxKuck / 80%
bounty reviewer: @DistributedDoge / 10%

Pitch deck for Submission

Bounty

Create a pitch deck to present our purpose, the app + features and the big picture of future communities.

Scope

• gdrive presentation
• 1min intro to deora and purpose and how KiezDAO is alligned with it
• integration of smart contract functionality and cello integration
• concentrate on the core features of the app - more like a sells pitch on the impact of the app, rather than the single features as covered in issue #10

Deliverables

• gdrive presentation as pitch

Gain for the project

Requirement for the submission

Roles

bounty gardener: @MaxKuck / 10%
bounty worker: @MaxKuck / 80%
bounty reviewer: @DistributedDoge / 10%

Find answers for market/product related questions

Bounty

(Using points as estimate of effort) Organizers suggested a list of questions to guide us as we build, let's answer them.

Scope

Find brief answers to the following questions suggested by hackaton and put them in written form. You are welcome to chip in, of course!

Size of target market?
Similar solutions?
Demographics we serve?

What is your product's value proposition?
What is your distribution and go-to-market strategy? Who can you partner with?
What are the risks associated with your solution?
What is the impact of your solution? How will it be measured?
Define the technical specifications and development roadmap

I am excluding questions that are answered by #1 bounty. And obviously proper long-form tech spec + roadmap is a question for next week.

Deliverables

Gain for the project

Roles

bounty gardener: @DistributedDoge
bounty worker: @DistributedDoge
bounty reviewer: name / share

Video Demo of the click dummy with voice over

Bounty

Create a video demo (with voice over) of the clickdummy

Scope

• define user flow ("director" role)
• feature walkthrough
• (create text for voice over)
• (contact a friend: Charles Thorburn who has speaker experience)
• 4 min max video
• create background visuals and mobile mockup see CD from BSIC
• let's do it like we did for volt --> @cyan-one

Deliverables

• video with app demo

Gain for the project

hackathon requirement for submission

Roles

bounty gardener: @MaxKuck / 10%
bounty worker: @MaxKuck 50% / @cyan-one 20%
bounty reviewer: @zschavi / 20%

Create pepo video

Bounty

create a video better than these from the competition ;) - https://pepo.com/communities/bsic

Scope

• create idea an concept of a 30sec max video
• either define vision of kiezDAO or show process of renting/borrowing
• make a pepo video

Deliverables

• pepo video

Gain for the project

Roles

bounty gardener: @MaxKuck / 10%
bounty worker: @zschavi / 80%
bounty reviewer: @johannbarbie / 10%

clickdummy for mobile web application

Bounty

Once the mockups are ready we need a presentation read click dummy that feels like a web application

Scope

• clickable mockups
• create consistent and understandable user flow

Deliverables

• figma clickdummy

Gain for the project

better presentation of the tool

Roles

bounty gardener: @MaxKuck / 10%
bounty worker: @cyan-one / 80%
bounty reviewer: @MaxKuck / 10%

Threat model for kiezDAO

Bounty

Creating an app to manage common community budget is fun, but it wouldn't be very fun to watch said funds being stolen by criminals or eaten by fraudsters. Let us think of possible external and internal threats and ways to address those.

Don't expect rough throwaway hackaton model to hold water in real-world scenario.

Scope

• What are we building? (Components, attack surface)
• What can go wrong? (STRIDE threat model)
• What are we going to do about that?
• Did we do a good job when modeling?

Deliverables

Lightweight document on possible threats and how to prevent them.

Gain for the project

Angry users not asking where the money went?

Roles

bounty gardener: @DistributedDoge
bounty worker: @DistributedDoge
bounty reviewer: name / share

Weekly Deliverables (02.03.2020) Design Document

Bounty

Till monday, 02.03.2020 we should have the following three things submitted to repository (as pdf/md file), I think it makes sense to lump those three deliverables in single design document, and have this particular bounty pair-programmed.

Scope

• Persona(s) for users (boat-owners in Berlin)
• Pain Points (Lack of tools? Lack of trust for sharing? Why bother with kiezDAO?)
• User Stories (AS boater I WANT TO rent repair tool SO THAT my roof stops leaking etc.)

Deliverables

Could be markdown/google docs for easy collaborative writing. What matters is that final result uploaded to repository and not just linked, as everything needs to be within a repository.

We are not aiming for length, but rather usefulness, so no need to overthink it. Don't worry about following particular style or format of the deliverables, just stick with whatever makes sense for us and is easy to read.

Gain for the project

Roles

bounty gardener: @DistributedDoge
bounty worker: name / share
bounty reviewer: name / share

To Celo or not to Celo?

KiezDAO could use Celo blockchain so that we can take part in bonus track entitled Peace & Prosperity just skimming whitepaper:

Benefits:

• Linking identity to phone-number, verify ownership of phone number via SMS
• Stablecoins (DAI-equivalent), also fees paid in stablecoins
• Under the hood there is still EVM, so we can use solidity contracts

Risks:

• Learning about Celo takes time
• If Celo flops we will be left without settlement layer
• I did not find security audit for the network and algorithms

In conclusion, for real-life use at this time I would rather go with bare Ethereum, but I think it might be worthwhile to prototype some functionality using Celo (especially due to phone<->identity link) and see how user/developer experience compares to typical dApp.

Since stakes are low, and deadline is far away, I signed up for the contest track on gitcoin, as we can always change our minds later.

If you have any opinions on why Celo or why not Celo, I would be interested in hearing them.

Smart Contracts Dev & Deployment

Bounty

We need to show a proof-of-concept with super simple processes.

Scope

• develop a smart contract to exchange tool against a set token price from lender
• develop smart contract that holds token tribute (community fund)
• how can we include layer-2 here?

Deliverables

deployed smart contracts in solidity

Gain for the project

Roles

bounty gardener: name / share
bounty worker: name / share
bounty reviewer: name / share

Overview of kiezDAO mechanics - flow chart

Bounty

Visualize kiezDAO functions and features in a flow chart diagram for easier understanding and user flow (touchpoints)

Scope

• google drawing
• feature list of an MVP
• listing extra features and

Deliverables

.md file in the github rep

Gain for the project

general understanding of the user flow and functionality of the application

Roles

bounty gardener: @MaxKuck / 10%
bounty worker: @MaxKuck / 80%
bounty reviewer: @DistributedDoge / 10%

Info Dump

If you find anything interesting relevant to the project toss it here:

Item renting app with QR codes

https://github.com/UnSciPreneur/sharingDApp

Bogner, A., Chanson, M., & Meeuw, A. (2016). A Decentralised Sharing App running a Smart Contract on the Ethereum Blockchain. Proceedings of the 6th International Conference on the Internet of Things - IoT’16. doi:10.1145/2991561.2998465 (https://doi.org/10.1145/2991561.2998465)

Paper showing privacy problem

Liu, Z., Li, Y., Liu, Y., & Yuan, D. (2018). Sharing Economy Protocol with Privacy Preservation and Fairness Based on Blockchain. Lecture Notes in Computer Science, 59–69. doi:10.1007/978-3-030-00021-9_6 (https://doi.org/10.1007/978-3-030-00021-9_6)

Peer2Peer rental app backed by Smart Contract, super relevant

https://files.ifi.uzh.ch/CSG/staff/Rafati/Purchase-Rental-APP-SC.pdf

mobile mockups

Bounty

We came up with first screen ideas let's translate this into real mockups.

Scope

• develop mockups in solarpunch design
• write down possible features on the screens (that are needed or nice to have)
• see screen ideas
• check user_scenarios and product_market for inspiration

Deliverables

Screen ideas as mockups.

Gain for the project

first visualisation of the UX of kiezDAO

Roles

bounty gardener: @MaxKuck / 10%
bounty worker: @cyan-one / 80%
bounty reviewer: @zschavi / 10%

Survey with pilot users

Bounty

Target group survey

Scope

• create a survey with 5-8 questions
• interview people we know
• make 3-4 interviews

Deliverables

• pdf with different answers to each question

Gain for the project

insights about our pilot users

Roles

bounty gardener: @MaxKuck / 10%
bounty worker: @zschavi / 80%
bounty reviewer: @DistributedDoge / 10%