-
Notifications
You must be signed in to change notification settings - Fork 448
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 2023 - Upvote Token #7305
Comments
Some difficulties compiling, fix ASAP!
GitHub handles to add:
|
@InvictusRMC Last week we have created a fork of the project and added our own submodule. Each one of us managed to compile the application and run the new submodule. For this sprint we have added the following features:
Currently we have not tested sending tokens with two physical devices yet. However, sending (and receiving) the token did work when one of us used an emulator and someone else joined as a peer. |
Great progress! Next sprint:
|
For the second sprint we came up with the following token design and we wanted to check if we are heading in the right direction. We asked @InvictusRMC to provide some insight on the following: Token data structure:
On the personal trustchains we would like to store:
In the database we would like to store:
Reply from @InvictusRMC: |
@InvictusRMC, for this sprint we have discussed the following things and/or added the following features:
Questions:
|
See work of other group on simple token: |
@InvictusRMC Hereby our update for sprint 3. This sprint we worked on finishing the token design and trustchain implementation. We made the following decisions regarding this: For the Trustchain implementation:
For the Token design:
All changes are currently on the master branch. I have created a PR to the trustchain repository but it does not seem to create an APK yet. We look forward to your feedback this afternoon! As pointers to next sprint we want to do:
|
Great design ideas! Next steps:
--> Great content checkin by ChrisSBras/trustchain-superapp#1 (comment) hacking Tribler/trustchain-superapp@bd8f42d |
@InvictusRMC Hereby the update for this week: We have implemented 4 ways of recommending videos:
Regarding the torrent:
What we did for these 2 stories was:
The obstacle encountered was: the function call sessionManager.fetchMagnet(magnet, 10) returns null instead of the byte data needed to decode into a torrentInfo object which can be used to download the mp4 video |
Great work! Next sprint
Deliverables
|
@InvictusRMC Hereby the update for this week: Torrent seeding & Incentives for content providers:
|
Prioritization
Meetings
|
@InvictusRMC Hereby the update for this week. Benchmarking:
Previous merge to main:
README:
|
@InvictusRMC Hereby the final (small) update for this week. Application:
Benchmarking:
Unit tests:
Examination:
TODO:
|
You have a solid report, guys! Great work. Minor points:
|
@InvictusRMC Thank you for the review! We have incorporated the feedback in the report and made some small adjustments and extentions. Currently we are in the process of adding a code coverage badge to the repository. The tests that we have written cover ~18% of the lines in the main package (including the UI code). The build that you approved passed and produced an APK which can be found here: APK |
Hi guys, great work! Can you also post your slides here? |
@InvictusRMC Thank you for your time and the guidance during the course! Below I have attached the slides we had used during the presentation. |
Upvoting token. Each user can give away an infinite amount of ❤️ tokens. Content creators are rewarded with ❤️ tokens, boosting their visibility. Content gathering lots of ❤️ will get more attention and go viral. Content creators can see in real-time who is giving them a ❤️ token. The ❤️ token economy design and implementation is your responsibility. Part of your demonstration will be a wipe-based UX implementation which favours viral content. Fraud and manipulation of your token economy such as the Sybil attack can be ignored. Bonus background reading: The like economy: Social buttons and the data-intensive web.
The text was updated successfully, but these errors were encountered: