Skip to main content

Using Weaver

The easiest way to understand how Weaver works is to run it at a small scale:

  • First, launch a set of basic test networks built on Fabric, Corda and Besu. These networks offer the most basic capabilities of their DLT platforms and run toy applications (contracts and Layer-2) that can easily be tracked and debugged. You can launch these networks in one of several different ways: building Weaver components and dependencies locally or importing pre-built ones from Github packages, running core components in the host or in Docker containers. The choice depends on whether you just want to get these networks up and running or if you wish to customize the setup by modifying source code and configurations.
  • Once the test networks are launched, you can test two distinct kinds of interoperation modes:
    • Data sharing: all combinations of Fabric and Corda networks supported
    • Asset exchange: all pairs of network types from {Fabric, Corda, Besu} are supported
    • Asset transfer: all combinations of Fabric and Corda networks supported
  • (To bring down the test networks, go back to the "Setup" pages and follow instructions in the respective "Teardown" sections.)
  • After you run these tests and get a flavor of how the system and protocols work, you will be ready to move on to "real" networks, enhancing them with interoperation capabilities by incorporating Weaver into them. Check out the guidelines and templates for Fabric, Corda, and Besu networks.

If you wish to go further and understand Weaver specifics, dig into the code, or contribute to the open-source project, check out the project repository. For specific information about individual Weaver components, see:

The Weaver RFCs contain detailed specifications of the models, data structures, protocols, and message formats.