Open Jumba opened 7 years ago
katiaas
commented
7 years ago Question: How does the borrower know when an investor has sold his investment? The borrower needs a way to know that he needs to pay another investor instead of the original investor.
Jumba
commented
7 years ago We spoke with Martijn about our problems with getting dispersy running. After some explanation we got dispersy up and running with the market community.
TODO: Update dispersy docs and make a pull request.
Furthermore he wondered if we should store authentication data in the blockchain, as opposed to in dispersy. We explained that we haven't really thought about how dispersy can be used in this application, as in what we would put on the blockchain, and what we would use the dispersy database for.
He suggested storing transactions and documents on a personal blockchain (for each user) because the blockchain can not be tampered with, and use dispersy for other messages that require less 'integrity'.
Jumba
commented
7 years ago We need to remember to write about related problems.
Jumba
commented
7 years ago It has been decided to hold another standup at the end specifically to identify problems.
Name | Done | Doing | Problems | Approach
Arthur | Nothing | Controller voor login screen | Still figuring out how it all works | Invest time until he figures it out
Katia | Fixed and made screens and worked on the api | Working on the API | She's feeling ill and is not sure how to implement unit tests | -
Seu | Fixed and made screens and worked on the api | Working on the API | Is feeling ill as well (Katia is the vector)
Calvin | Did some cryptography work, api and tests. Had short meeting with Martijn, got dispersy working!!!!! | Learning about PyQT | NOTHING DISPERSY IS WORKING. Feeling a bit ill though. | Vitamin C
Daily Standup
Name | Done | Doing | Problems
Arthur | Models & define API, flowcharts | Implement dispersy encryption functions in software | Python is a bit complicated
Calvin | Models & define API, flowcharts, implement mock database/backend/models | Encryption | Dispersy is still a pain
Katia | Flowcharts, functions for API | Not sure yet, may make screens or work on the API | Not exactly sure what to do
Seu | Flowcharts, functions for API | No clue | No idea what she has to do
After a short meeting we have decided that:
Arthur: Generate code for login screen, add listeners to pass path of private key to API. Calvin: Enable 'registering' by generating keys Seu & Katia: Fix screens and furthermore work on API