| BRANCH | AZURE PIPELINES | TESTS | CODE COVERAGE |
|---|---|---|---|
| MASTER |  |
 |
|
| DEV |  |
 |
EBridge is an effortlessly Bridging You in and out of the aelf Ecosystem
Before cloning the code and deploying the contract, command dependencies and development tools are needed. You can follow:
The following command will clone EBridge Contract into a folder. Please open a terminal and enter the following command:
git clone https://github.com/eBridgeCrosschain/ebridge-contracts.aelfThe next step is to build the contract to ensure everything is working correctly. Once everything is built, you can run as follows:
# enter the Launcher folder and build
cd src/AElf.Boilerplate.BridgeContract.Launcher
# build
dotnet build
# run the node
dotnet runIt will run a local temporary aelf node and automatically deploy the bridge contract on it. You can access the node from localhost:1235.
This temporary aelf node runs on a framework called Boilerplate for deploying smart contract easily. When running it, you might see errors showing incorrect password. To solve this, you need to back up your aelf/keysfolder and start with an empty keys folder. Once you have cleaned the keys folder, stop and restart the node with dotnet runcommand shown above. It will automatically generate a new aelf account for you. This account will be used for running the aelf node and deploying the bridge contract.
You can easily run unit tests on bridge contracts. Navigate to the EBridge.Contracts.Bridge.Tests and run:
cd ../../test/EBridge.Contracts.Bridge.Tests
dotnet test