-
Notifications
You must be signed in to change notification settings - Fork 454
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
A Mobile and Generic Asset Exchange using Liquidity Pooling [intergroup communication] #6001
Comments
Group 2 e-mailed about their intent to look into multi-sig wallets and implementing basic transactions in the superapp. |
The past few days, we have been thinking about how each group can develop a distinct app/project. Some possibilities that we consider:
We are curious to hear about your ideas and thoughts! :D |
Proposal for next week sprint:
|
@Group1 we are working on a basic GUI interface, for now the idea is to have a page simply for viewing your balance for all the wallets (within this project mainly bitcoins and euro tokens) and another page for exchanging your assets for another. For bitcoin we have used bitcoinj to create a wallet for the user. We are also looking into doing the same for euro tokens. We are working in this fork |
@Group2 Sounds good! Are you guys available tomorrow (Friday) at 10:00 to meet up and synchronize? |
Yes! I will send a mail with a link to a Zoom meeting for tomorrow. |
@kchong97 and @EmielBoss, notice that the group1/2 mentions are notifying random users, of which one seems to be unused and the second seems to be owned by some Chinese users. They both might not appreciate being tagged randomly in this issue :P |
We created BTC multi-sig functionality and created a small demo. Check it out here: #5988 (comment). We are working on a seperate branch and created a seperate debug fragment where we (group 1) can work on the without annoying you guys |
https://hummingbot.io/ and https://margin.de/ |
Could you give me access to the fork of group 2? :D |
Hmmm I had already invited you but it seems you hadn't accepted it. I will try to resend it. |
My bad! I glanced over it. Thank you :D |
Meeting 23/03/2021
|
BTC multi-sig implementation update (branch: https://github.com/chrislemaire/trustchain-superapp/tree/multi-sig-wallets-implementation):
The implementation is made on top of what code group 2 has presented last week. This means it only has partial trustchain integration. It required quite some refactoring, so it will look a bit different than what was presented to us. I do think that in its current state, group 2 should be able to use the current BTC implementation, to be able to complete their BTC-EURotoken demo. Meanwhile, group 1 (us), will create a seperate fragmant in which we will contain and implement our BTC-ETH demo. This should allow us to work more independently from now on. Of course, please communicate any questions regarding BTC multi-sig with us. |
Tribler/trustchain-superapp#75 PR is merged, closing the issue |
We (group 1) suggest to use this issue in order to facilitate communication and coordination between the two groups.
The separate issues for notes for each group are: #5988 and #5996.
@devos50 I do not seem to be able to assign the correct labels and assignees/participants to this issue. If you could do so, it would be appreciated :)
The text was updated successfully, but these errors were encountered: