Skip to content

Commit 604781d

Browse files
committed
add diagram
1 parent 9e11a02 commit 604781d

File tree

7 files changed

+64
-89
lines changed

7 files changed

+64
-89
lines changed

Advanced/README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@ and [OwnableState](https://docs.corda.net/docs/corda-os/api-states.html#ownables
99
<img src="./auction-cordapp/snaps/setup.png" alt="Corda" width="600">
1010
</p>
1111

12+
### [Due Diligence Cordapp](./duediligence-cordapp):
13+
An capital market themed app that depicts an ideal shareable due diligence process between banks. It uses advance feature attachment functionality to whitelist the trusted auditors.
1214

1315
### [Negotiation Cordapp](./negotiation-cordapp):
1416
An application that depicts the businsess negotiation and communication process over a distributed ledger system.
@@ -21,6 +23,10 @@ A simple i-owe-you application illustrates all of the steps of creating an oblig
2123
This is an imlementation of Secret Santa using Corda as a tool to store multiple game states.It has a material-ui frontend that lets users create and self-service their own secret santa games. The frontend is implemented in ReactJS and the backend is implemented with a Spring Boot server and some corda flows. It is also equipped with an external emailing package(sendgrid), which you can utilze and turn the app into a live app and send the secret santa assignments to your friends'
2224
emails.
2325

26+
<p align="center">
27+
<img src="./secretsanta-cordapp/clients/src/main/webapp/src/Components/img/secret_corda.png" alt="Corda" width="200">
28+
</p>
29+
2430
### [Snake and Ladder Game Cordapp](./snakesandladders-cordapp):
2531
This sample implements a simple Snakes And Ladder Game on Corda. This cordapp demonstrate the use of multiple features, including Corda Account Library and Oracle service.
2632
<p align="center">

Advanced/duediligence-cordapp/README.md

Lines changed: 15 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,14 @@
1-
# due-diligence-cordapp
2-
<p align="center">
3-
<img src="./image.png" alt="Corda">
4-
</p>
1+
# Due Diligence Cordapp
2+
3+
This cordapp is an example of how blockchain can work in the capital market industry. Due diligence is commonly the first step of any action in the capital market. In many of the industry, it is also required by the regulators to prevent fraudulent and risky transactions. Each firm will have its own due-diligence process and standards, but at the same time, the cost of executing due diligence is also bared by them individually.
4+
5+
## App Design
6+
7+
8+
The above picture is a high level mock overview of a shareable due diligence DLT app. BankA will initiate the original Corporate Records auditing with an autitor. Then it will share the auditiing report with BankB to save BankB's cost on getting the same report. Wise versa, BankB can work with a different auditor and produce a different report and share with BankA. In the implmentation of this sample cordapp, we will only cover one type of the file auditing.
9+
10+
Notes: another key feature of this app is whitlisting trusted auditors. It is done by utilizing attachment function in Corda. More samples on how to use attachment can be found in the [Features samples folder](../../Features)
11+
512

613
## Pre-running the app
714

@@ -24,7 +31,7 @@ Step #2: Go to the Trusted Auditor Node, validate the auditing request(This step
2431
flow start ValidateCorporateRecordsInitiator linearId: <XXXX-XXX-XXXX-XXXXX-XXXXXX>
2532
```
2633

27-
Step #3: Go to PartyA, Do a query to confirm that the request has been validated. You should see the variable `qualification=true`.
34+
Step #3: Go to PartyA, Do a query to confirm that the request has been validated. You should see the variable `qualification=true`.
2835

2936
```
3037
run vaultQuery contractStateType: net.corda.samples.duediligence.states.CorporateRecordsAuditRequest
@@ -33,18 +40,19 @@ Then, we will instruct PartyA to share a copy of the auditing result with PartyB
3340
```
3441
flow start ShareAuditingResultInitiator AuditingResultID: <XXXX-XXX-XXXX-XXXXX-XXXXXX>, sendTo: BankB, trustedAuditorAttachment: "8DF3275D80B26B9A45AB022F2FDA4A2ED996449B425F8F2245FA5BCF7D1AC587"
3542
```
36-
This flow will return the LinearId of the copy of auditing report, you would need this in Step #6.
43+
This flow will return the LinearId of the copy of auditing report, you would need this in Step #6.
3744

3845
Step #4: Go to PartyB, do a query to confirm the delievery of copy of the Auditing Report.
3946
```
4047
run vaultQuery contractStateType: net.corda.samples.duediligence.states.CopyOfCoporateRecordsAuditRequest
4148
```
42-
As of now, the sharing of the trusted auditing report is done. What left now for both PartyA and PartyB in this use case is to upload the Corporate Records auditing report into a due-diligence list, which they can share with a regulator.(You can again alter this step to suit any other use cases).
49+
As of now, the sharing of the trusted auditing report is done. What left now for both PartyA and PartyB in this use case is to upload the Corporate Records auditing report into a due-diligence list, which they can share with a regulator.(You can again alter this step to suit any other use cases).
4350

4451

4552
Step #5: Go to PartyA, Attach the Corporate Records auditing report into a due-diligence checklist and report to the Regulator. Again, the approvalId is the linearId returned in Step #1.
4653
```
4754
flow start CreateCheckListAndAddApprovalInitiator reportTo: Regulator, approvalId: <XXXX-XXX-XXXX-XXXXX-XXXXXX>
55+
4856
```
4957
Step #6: Go to PartyB, Attach the copy of the Corporate Records auditing report into a due-diligence checklist and report to the Regulator. You would need the linearId that is return from Step #5
5058
```
71.6 KB
Loading
-306 KB
Binary file not shown.

Basic/cordapp-example/.idea/gradle.xml

Lines changed: 2 additions & 2 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)