Update use cases authored by Aleksandra Grabowska's avatar Aleksandra Grabowska
...@@ -16,9 +16,10 @@ ...@@ -16,9 +16,10 @@
**UC 1** **UC 1**
A Exchange user sends cryptocurrency and wants to receive Euro. A Exchange user sends cryptocurrency and wants to receive Euro.
1. An operation in the blockchain includes a receiver IBAN account. 1. *An exchange user makes a transfer using the Exchange interface*
2. A memo description (with IBAN account) is encrypted. 2. An operation in the blockchain includes a receiver IBAN account.
3. A transaction is processed with a standard path in the Exchange: 3. A memo description (with IBAN account) is encrypted.
4. A transaction is processed with a standard path in the Exchange:
a. The transaction scanner in the source blockchain recognizes an operation and takes an appropriate action (as now) – sends it to SEPA-plugin a. The transaction scanner in the source blockchain recognizes an operation and takes an appropriate action (as now) – sends it to SEPA-plugin
b. SEPA-plugin or CBS recognizes whether it is an internal transfer (to IBAN account in the Dan’s bank) or external transfer (to IBAN account not in the Dan’s bank): b. SEPA-plugin or CBS recognizes whether it is an internal transfer (to IBAN account in the Dan’s bank) or external transfer (to IBAN account not in the Dan’s bank):
i. If it is internal transfer, then it is processed in SEPA-plugin or CBS i. If it is internal transfer, then it is processed in SEPA-plugin or CBS
...@@ -46,13 +47,14 @@ To be discussed: ...@@ -46,13 +47,14 @@ To be discussed:
*After meeting:* *After meeting:*
*Remarks:* *Remarks:*
*1. There is no functionality that allows to check a user account balance in cryptocurency for accounts other than Dan’s. Why? It is useless, because balance can change.* *1. There is no functionality that allows to check a user account balance in cryptocurency for accounts other than Dan’s. Why? It is useless, because balance can change.*
*2. Sending Euro requires dedicated application for creating Euro transfer.*
*We can see two possible solutions for UC2 and UC3:* *We can see two possible solutions for UC2 and UC3:*
*First solution:* *First solution:*
1. *An exchange user makes a transfer using the Exchange interface.* 1. *An exchange user makes a transfer using the Exchange interface (or rather a dedicated interface of IB).*
2. *CBS registers a transaction.* 2. *CBS registers a transaction (similarly to blockchain registering a transaction).*
3. *SEPA-plugin transaction scanner checks via CBS if there are any new incoming transactions on Dan’s account.* 3. *SEPA-plugin transaction scanner checks via CBS if there are any new incoming transactions on Dan’s account (same as for any crypto/blockchain).*
4. *If there are any, SEPA-plugin transaction scanner fetches those transactions and processes them.* 4. *If there are any, SEPA-plugin transaction scanner fetches those transactions and processes them (same as for any crypto/blockchain).*
*Then the standard execution path is followed in the Exchange: a record is created and processed.* *Then the standard execution path is followed in the Exchange: a record is created and processed.*
... ...
......