A demo of swaps in an auction scenario with three distinct Corda Networks. This worked example is an implementation of the design presented at CordaCon2021. The slides from this presentation outlining the architecture are available here in the repo.
The example simulates an Auction scenario with potentially distrusting parties spread across distinct Cordapp domains (Corda Networks). For brevity, the example uses a single Cordapp to encapsulate the artwork and consideration states (ArtworkState, TokenType-GBP, TokenType-CBDC) and their associated contracts and flows; additionally, a single Spring/Orchestration layer is used to coordinate and execute cross-network interactions between an organization's Auction Network identity, and their associated consideration network identity.
In a more "REAL" deployment you can imagine the structure of the total solution would include three distinct Cordapps (Auction, GBP, CBDC) as well as individual off-ledger orchestration services managed, and controlled exclusively by each party.
The key to this 'simulation' is that we have limited these actions to operate completely independently and disjoint from each other. Whereby, the Gallery can only receive a result or instruction from its own identity on another network, and the same holds for the Bidding parties. Additionally, in the Cordapp a ContractState and its associated flows cannot transact or interact directly with another ContractState or its flows. Any evolutions based on data from an asset represented on another network will receive its instruction or payload via the orchestration service triggered from the source network.
This demo sidesteps the problem of inter-chain identity, discovery and messaging by co-ordinating all actions via an independent controller, the Spring Boot service which also provides the REST API used by the front-end. Thus, instead of the Bidder on the Auction network sending a message directly to the Buyer on a Token network, instructing it to send encumbered tokens, the controller first uses Corda RPC to run a flow on the Bidder, then makes a second Corda RPC call to the Buyer instructing it to run the flow which sends encumbered tokens, passing across the details retrieved from the first call. The controller also holds (via up-front configuration) all the details of the various networks and parties.
- Alice: an art seller
- Bob: buyer with CBDC consideration
- Charlie: buyer with GBP (fiat) consideration
- Alice (as Gallery)
- Bob (Bidder)
- Charlie (Bidder)
- Alice (Seller)
- Bob (Buyer)
- Alice (Seller)
- Charlie (Buyer)
** Note: That each identity across distinct networks with the same identifier is owned/controlled by the same organization.
gallery-contracts - ContractState, Contract, and asset def/models
gallery-workflows - Business logic and services
buildSrc - Docker and K8s deployment builder classes
deploy - Local Cordformation configuration/tasks, Azure K8s configuration and Dockerfiles
frontend - Frontend sources and associated proxies
spring-api - Spring api controller and orchestration services
Warning: Because the solution requires three separate networks running in parallel, we recommend for best performance to use a machine which has 32GB of Ram. You may still run the demo with less, but if you encounter problems you may have to adjust or tweak your docker resource settings or additionally reinitialize a downed node periodically.
- Docker and docker-compose installed. See /deploy/README.md for further details.
- Java 1.8
./gradlew prepareAllDockerNodes- Generates persistent node file structures and docker-compose yaml configuration.
./gradlew allNetworksUp- Brings up Auction, GBP, and CBDC networks locally via docker-compose.
./gradlew runSpringApp- Launches Spring Orchestration service and REST controller.
See /frontend/galleryapp/README.md
After installing, the frontend will be available at http://localhost:3000
To bring Gallery Artwork and Buyer tokens on ledger, click the Reset Data tab in the configuration menu of the Frontend.
- Alternatively you could target the initialization directly via a curl or browser request to http://localhost:3000/network/init
