-
Notifications
You must be signed in to change notification settings - Fork 446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blockchain Engineering Class of 2020: Delft-DAO - Create your own currency (Team II) #5144
Comments
@InvictusRMC @brian2509 @MKuijpers @PJvanderLaan
Future sprint ideas:
|
Related:
|
We would like to tell what we have done last week and what questions we have for the current meeting. Done this week:
Questions:
|
This week's APK file |
Next sprint comments:
|
Initial design idea for the next sprint (not very specific): Onboarding
Transaction
Known issues that are ignored (for now)
|
good stuff! |
For integrating work of all teams with the existing codebase, we have decided to take the super app approach. To separate IPv8 library from the app, we have moved |
Progress update:
APK:Screenshot: |
Sprint feedback:
|
No problem, TUDelft has .73 dollar to spend on science 😄 |
Actually, the latest info I got is that your script is likely to be huge and cost at least $10 per transaction.. Industry expert: you probably need a week to compress it, once you have it working. |
Progress updateUI/Trustchain:
Bitcoin:
APK(still not integrated in the superapp) Screenshots |
Sprint progress:
|
Done this week (2020-03-18 - 2020-03-25)
Example multisig transaction:(With an entrance fee of 10.000 satoshi) Create wallet as the first person. Add the first person. Make payment to another address. Pay 1000 to |
Sprint progress:
|
Progress last week (25-03-2020 - 01-04-2020)Super app fork:https://github.com/InvictusRMC/trustchain-superapp/ DocumentationProgress
|
|
This week's progress:
|
This weeks apk: app-debug.zip Note: there are some navgraph conflicts causing some navigation to not be behaving as planned |
Sprint progress:
|
Sprint progress:
|
This week's progress
|
Progress
|
near final sprint comments:
|
Final Release |
Delft-DAO
What is a DAO? Within the coming decade the future of jobs, employment and the nature of the firm will change profoundly. Automation, AI, and robots will replace many of today's jobs. A new type of company is a company without any employees, without any machines or physical infrastructure. A Decentralized Autonomous Organizations, DAO, only exists in software. It goes beyond smart contracts, it is a complete company inside software. DAO development is still in the experimental stage.
Within this course you can create your very own autonomous organisation, the Delft-DAO. Learn to engineer a decentralised autonomous organisation, use the existing tools, and understand the security risks. The aim is to alter the nature of the firm in the Internet age, see the Nobel prize winning theory. Production cost become essentially cost-free. An organisation which exists purely in cyberspace. The Delft-DAO is designed to be the first sustainable DAO. How can we empower leaderless organizations? How can it earn money from manipulating bits?
Advisor: J.A. Pouwelse, TUDelft blockchain lab founder (weekly meetings on Wednesdays)
Several teams from the class will create running code (requirements for a passing grade..) for one of the following functionalities. Four teams together create the building blocks of the complete Delft-DAO (time consuming integration step is outside our scope).
Create your own currency
First step of building a DAO is creating money. This enables the Delft-DAO micro-economy. Mark Zuckerberg is creating his own currency for a few billion users, called "Facebook Libra". For this assignment you will also create your own currency in 10 weeks, almost from scratch! Obviously security and usability is somewhat limited. You will investigate methods for minting and transfer of tokens. You will designate yourself as "trusted nodes", able to generate cash. Mandatory starting point for your code is this Kotlin app
Team II
The text was updated successfully, but these errors were encountered: