forked from hyperledger-cacti/cacti
-
Notifications
You must be signed in to change notification settings - Fork 0
/
use-case-sequence-diagram-blockchain-migration.puml
122 lines (96 loc) · 3.24 KB
/
use-case-sequence-diagram-blockchain-migration.puml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
@startuml
skinparam ArrowFontStyle italic
title Hyperledger Cactus\nSequence Diagram - Blockchain Migration
actor Consortium_Member_A as a
actor Consortium_Member_B as b
box Cactus
entity "API" as api
entity "Validator(s)" as v
end box
box "Ledgers"
database Ledger1 as d1
database Ledger2 as d2
end box
autoactivate on
== Agreement Phase ==
a -> b: Propose Blockchain Migration
Note right
Off-chain procedure
end note
return Send Endorsement
a -> api: Sign Transaction to Endorse Blockchain Migration
return Request Confirmed
b -> api: Sign Transaction to Endorse Blockchain Migration
return Request Confirmed
autoactivate off
api -> a: Ready to Proceed
api -> b: Ready to Proceed
autoactivate on
== Initialization Phase ==
a -> api: Sign Transaction to Initialize Blockchain Migration
api -> v: Deploy Interoperability Support Data\n(smart contracts and configuration files) on Ledger1
v -> d1: Deploy Support Data as Consortium_Member_A
return Data Deployed
return Data Deployed
return Ready to Initiate Migration
b -> api: Sign Transaction to Initialize Blockchain Migration
api -> v: Deploy Interoperability Support Data on Ledger1
v -> d1: Deploy Support Data as Consortium_Member_B
return Data Deployed
return Data Deployed
return Ready to Initiate Migration
a -> api: Initialize Blockchain Migration
api -> v: Initialize Consortium_Member_A's view\non exisitng assets and data
v -> d1: Query Ledger 1 as Consortium_Member_A
return Return Results
return Return results
return Initialize Blockchain Migration Success
autoactivate off
api -> api: **processes query and builds Consortium_Member_A's**\n**view on existing assets and data**
return
api -> a: Send Consortium_Member_A's view on L1
a -> api: Confirm View
return OK
autoactivate on
b -> api: Initialize Blockchain Migration
api -> v: Initialize Consortium_Member_B's view\non exisitng assets and data
v -> d1: Query Ledger 1 as Consortium_Member_B
return Return Results
return Return results
return Initialize Blockchain Migration Success
autoactivate off
api -> api: **processes query and builds Consortium_Member_B's**\n**view on existing assets and data**
return
api -> b: Send Consortium_Member_B's view on L1
b -> api: Confirm View
return OK
api -> api: Merge views
Note right
Optional: This process merges the views of
Consortium_Member_A and Consortium_Member_B
into a consolidated view
end note
return
autoactivate on
api -> a: Merged View
return Accept merge
api -> b: Merged View
return Accept merge
== Migration Phase ==
a -> api: initiate Blockchain Migration
api -> v: Execute Migration to Ledger 2
v -> d2: Execute transactions\non Ledger 2 as Consortium_Member_A
return Transactions Successfully Executed
return Success
return Success
b -> api: initiate Blockchain Migration
api -> v: Execute Migration to Ledger 2
v -> d2: Execute transactions\non Ledger 2 as Consortium_Member_B
return Transactions Successfully Executed
return Success
return Success
autoactivate off
api -> api: **Perform final adjustments, e.g., submit**\n**missing transactions**
api -> a: Migration Process Completed
api -> b: Migration Process Completed
@enduml