Date
Attendees
- Bartek Nowotarski (Stellar)
- Jed McCaleb (Stellar)
Goals
- Kick-off Mifos Stellar integration. Reach agreement on rough architecture and division of labor and answer questions.
Notes
| Item | Who | Notes |
|---|---|---|
| Rough Agenda | Markus Geiß | |
| Java SDK | Bartek Nowotarski |
Comments on API welcome since it is very new. Mifos can ignore Backwards compatibility: Stellar will work towards compatibility within their Java API. |
| Testing in global vs. test vs standalone network | Jed McCaleb Bartek Nowotarski | Live public network: https://horizon.stellar.org Global network passphrase: NETWORK_PASSPHRASE="Public Global Stellar Network ; September 2015" Test network: https://horizon-testnet.stellar.org We can create our own network for tests purposes. Creating a horizon server is not strictly necessary; we can use theirs. |
| Implementation of a federation server | Jed McCaleb Bartek Nowotarski | https://www.stellar.org/developers/learn/concepts/federation.html Bartek will create the federation server An implementation already exists at https://github.com/DominikTo/stellar-federation Jed informed us that it is out-of-date. The Protocol has changed slightly since it was created. Question still open: global or customer installation based federation server? Account domain should be configurable per Mifos tenant. |
| Future communication | Jed McCaleb | Bartek will assist Myrle. His preferred communication is via slack channel. Jed will set up a slack channel. Bartek is in Poland, so in the same time zone. |
| Testing worse case scenario | Jed McCaleb | The worst case scenario is 5 transactions/second. Horizon should be the bottleneck and not the Connector. |
| Miscellaneous | Within Stellar we create one account per tenant. The account within the tenant that should receive/ has sent funds is part of their memo information. |
Action items
- Get decision on global vs. per customer installation of federation server
- Provide feedback on API.
- Setup communication channel between Bartek and Myrle