- Prerequisites
- Installation
- Smart Contract Development Lifecycle
- Extension commands
- License and telemetry
The IBM Blockchain Platform extension helps developers in create, test, and deploy smart contracts, and connect to Hyperledger Fabric environments.
We're working hard developing this extension, and we've got a lot planned before the v1.0 release, but if you find a bug, want to make a suggestion, or want to track the features we're working on, check our Github repository. If you have any questions or queries, create a question on Stack Overflow.
To get started with this extension quickly, follow the Quickstart Guide to learn how to develop, test, and deploy smart contracts using VSCode.
You will need the following installed in order to use the extension:
- VSCode version 1.31 or greater
- Node v8.x or greater and npm v5.x or greater
- Yeoman (yo) v2.x
- Docker version v17.06.2-ce or greater
- Docker Compose v1.14.0 or greater
- Windows 10 Enterprise, Pro, or Education at 1607 Anniversary Update or later, Linux, or Mac are currently the only supported operating systems.
If you are using Windows, you must also ensure the following:
- Docker for Windows is configured to use Linux containers (this is the default)
- You have installed the C++ Build Tools for Windows from windows-build-tools
- You have installed OpenSSL v1.0.2 from Win32 OpenSSL
- Install the normal version, not the version marked as "light"
- Install the Win32 version into
C:\OpenSSL-Win32on 32-bit systems - Install the Win64 version into
C:\OpenSSL-Win64on 64-bit systems
Please note: If a smart contract was created before version 0.1.0 of this extension, the package.json file must contain a dependency on [email protected].
If you require sudo/root to install npm modules, you must manually install the yeoman generator used to create smart contract projects using the following command: npm install -g yo generator-fabric
To install the IBM Blockchain Platform VSCode extension, click here or visit the Visual Studio Code Marketplace for more information.
The expected smart contract development lifecycle follows several broad points, all possible entirely within VSCode using this extension:
- Creating and packaging a smart contract.
- Connecting to an instance of Hyperledger Fabric.
- Running and debugging a smart contract.
The first step of developing a smart contract is to create and package the smart contract into the correct format for deploying to an instance of Hyperledger Fabric. Creating and packaging a smart contract has three key steps:
- Create a smart contract project
- Write smart contract functions
- Package the smart contract for deployment
A smart contract project is a directory containing all the relevant contract and metadata files that define a smart contract. This extension currently supports creating TypeScript and JavaScript smart contract projects.
To create a smart contract project:
- Use the
Create Smart Contract Projectcommand from the command palette in VSCode. - Select a programming language for your smart contract, currently this extension supports TypeScript and JavaScript smart contracts.
- Select the directory in which to store the smart contract project.
- The extension will create a skeleton smart contract project, including a basic smart contract, unit tests, and a
package.jsonmetadata file.
When creating a smart contract project, a basic smart contract file is created in the lib or src directories. Smart contract functions can be added to and edited within this file to create the terms of your smart contract.
To write a smart contract:
- Open the basic smart contract created by default in the smart contract project. The basic smart contract file in the
libdirectory if it's a JavaScript smart contract, or thesrcdirectory if it's a TypeScript smart contract. - Edit, update, or add new smart contract functions. For information on smart contract best practice and writing smart contracts, see the [Hyperledger Fabric documentation](linkety linkety link).
- Save your smart contract ready for packaging.
Once the smart contract has been created and the smart contract functions have been written, the smart contract project must be packaged before it can be deployed.
To package a smart contract project:
- Use the
Package a Smart Contract Projectcommand from the VSCode command palette or click Add in the extension explorer view. - Select the smart contract project to package.
- The extension will package the smart contract project into a single Hyperledger Fabric smart contract package file, using the standard Hyperledger Fabric chaincode deployment specification format.
- The smart contract package file can now be deployed to an instance of Hyperledger Fabric.
### Connecting to Fabric
This extension provides two methods for connecting to an instance of Hyperledger Fabric. Firstly, the extension includes a local instance of Hyperledger Fabric known as the local_fabric connection. Secondly, you can provide connection details for a running instance of Hyperledger Fabric and connect to that for service discovery purposes.
The local_fabric connection is a local implementation of Hyperledger Fabric contained in a Docker container. It can be used to rapidly develop and iterate on smart contracts.
To start the local_fabric connection:
- Ensure that Docker is running.
- From the IBM Blockchain Platform extension screen, click the local fabric runtime listed under the Local Fabric Ops pane.
- The extension will download and deploy the pre-configured Hyperledger Fabric instance.
To stop or teardown the local_fabric connection:
- From the IBM Blockchain Platform extension screen, click the ellipsis icon in the Local Fabric Ops bar.
- Select Stop or Teardown.
If the local Hyperledger Fabric instance is stopped, the data is maintained, if teardown is selected, the data will not be recoverable.
Using this extension you can connect to your own Hyperledger Fabric instance. If you choose to connect to your own Hyperledger Fabric instance, it must be running Hyperledger Fabric v1.4.0 or later. From extension version 0.2.0 and later, you can use a file system wallet to import identities to connect with. Alternatively, provide a name, user certificate and private key and the extension will generate a new file system wallet. In either case, this file system wallet can be used by your Blockchain applications.
Please note: v0.3.0 has restructured fabric connections to fabric gateways, so you will need to add any connections created with previous releases again in order to use them.
When using the pre-configured local instance of Hyperledger Fabric named local_fabric, the extension will automatically pull and use the correct Docker images.
If you want to start and connect to your own Hyperledger Fabric instance, ensure that you are using Hyperledger Fabric v1.4.0 or later by following the Fabric documentation here:
https://hyperledger-fabric.readthedocs.io/en/release-1.4/install.html
To connect to the local Fabric instance using the default identity:
The local instance of Hyperledger Fabric has a default gateway identity: [email protected].
To connect using the default gateway identity:
- After starting the local Fabric instance, expand the local_fabric heading in the Fabric Gateways pane.
- Click the identity listed [email protected].
After connecting
Gateways and their wallets can be edited by right-clicking and selecting Edit Gateway in the Fabric Gateways panel. This will open User Settings, with the gateway available for editing. This is not available for the local_fabric runtime.
### Running and debugging a smart contract
some text
Smart contract packages are installed on Fabric peers. Start local_fabric, find a peer under Nodes in the Local Fabric Ops panel and right-click to select Install Smart Contract. Alternatively click on + Install or right-click Installed under Smart Contracts in the Local Fabric Ops panel.
Start local_fabric, find a channel under Channels in the Local Fabric Ops panel and right-click to select Instantiate Smart Contract. Alternatively click on + Instantiate or right-click Instantiated under Smart Contracts in the Local Fabric Ops panel. You will be asked to select from a list of open projects, smart contract packages or smart contracts installed on peers in the channel.
It is useful to think of installing on peers as the first step and instantiating on a channel as the second step of deploying a smart contract package.
Once connected to a Fabric gateway in the Fabric Gateways panel, right-click a transaction under an instantiated smart contract and click Submit transaction. This will submit a transaction to a smart contract.
Debugging your smart contract allows you to run through the smart contract transactions with breakpoints and output, to ensure your transaction works as intended. To debug your smart contract follow these steps:
- Ensure you are connected to the
local_fabricruntime and that thelocal_fabricpeer is in development mode. Development mode is indicated by an infinity symbol on a peer, underNodesin theLocal Fabric Opspanel. To toggle development mode, right-click the peer and selectToggle Development Mode. - Open your smart contract project in your workspace.
- Open the debug view in Visual Studio Code using the left-hand navigation bar.
- Select the
Debug Smart Contractconfiguration by using the dropdown in the upper-left. - Package and install the smart contract by clicking the play button.
- Add breakpoints to the smart contract by clicking on the relevant line numbers in your smart contract files.
- Click Instantiate in the
Local Fabric Opspanel. In theFabric Gatewayspanel, you can now right click on transactions to submit them, execution will be paused on any breakpoints you've defined.
To make iterative changes to your smart contract while debugging, after making your changes click the restart button. Restarting debugging means you don't need to instantiate the contract again. Please note, as this stores the smart contract in local memory, for many changes to large smart contracts, you may need to reinstantiate the smart contract.
Right-click a package and select the Export Package option. You can select where the package is exported to. Use this to take the packages you have made and deploy them somewhere else, using other tools, such as the Fabric CLI (peer chaincode install command).
The IBM Blockchain Platform extension provides an explorer and commands accessible from the Command Palette, for developing smart contracts quickly:
| Command | Description |
|---|---|
| Add Gateway | Add a Hyperledger Fabric instance gateway |
| Add Identity To Wallet | Add an identity to be used when connecting to a Hyperledger Fabric gateway |
| Connect Via Gateway | Connect to a Hyperledger Fabric blockchain using a gateway |
| Create Smart Contract Project | Create a new JavaScript or TypeScript smart contract project |
| Debug | Debug a Smart Contract |
| Delete Gateway | Delete a Hyperledger Fabric instance gateway |
| Delete Package | Delete a smart contract package |
| Disconnect From Gateway | Disconnect from the blockchain gateway you're currently connected to |
| Edit Gateway | Edit connection profile or wallet used for connecting to a blockchain gateway |
| Export Connection Details | Export connection details for the a Hyperledger Fabric instance |
| Export Package | Export an already-packaged smart contract package to use outside VSCode |
| Generate Smart Contract Tests | Create a functional level test file for instantiated smart contracts |
| Install Smart Contract | Install a smart contract package onto a peer |
| Instantiate Smart Contract | Instantiate an installed smart contract package onto a channel *Note: This currently doesn't work with IBM Blockchain Platform Enterprise plan - Coming soon! |
| Open Fabric Runtime Terminal | Open a terminal with access to the Fabric runtime (peer CLI) |
| Package a Smart Contract Project | Create a new smart contract package from a project in the Explorer |
| Refresh Fabric Gateways | Refresh the Fabric Gateways view |
| Refresh Smart Contract Packages | Refresh the Smart Contract Packages view |
| Restart Local Fabric Ops | Refresh the Local Fabric Ops view |
| Start Fabric Runtime | Start a Hyperledger Fabric instance |
| Stop Fabric Runtime | Stop a Hyperledger Fabric instance |
| Submit Transaction | Submit a transaction to a smart contract |
| Teardown Fabric Runtime | Teardown the local_fabric runtime (hard reset) |
| Toggle Development Mode | Toggle the Hyperledger Fabric instance development mode |
| Upgrade Smart Contract | Upgrade an instantiated smart contract |
| View Homepage | View the extensions homepage |
The source code files are made available under the Apache License, Version 2.0 (Apache-2.0), located in the LICENSE file.
The extension uses telemetry reporting to track usage data and help improve future extension versions.
For instructions on how to disable telemetry reporting, please visit the visit the Visual Studio Code FAQ.
This software uses the IBM Plex Sans font licensed under the SIL Open Font License, Version 1.1. Copyright © 2017 IBM Corp. with Reserved Font Name "Plex"
This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is copied below, and is also available with a FAQ at: http://scripts.sil.org/OFL