Set CI badge to track master branch
This commit is contained in:
parent
80e5706b05
commit
4487ad9e5a
|
@ -1,4 +1,4 @@
|
|||
[![CircleCI](https://circleci.com/gh/k1rill-fedoseev/eth-to-bnc-bridge/tree/dev.svg?style=svg)](https://circleci.com/gh/k1rill-fedoseev/eth-to-bnc-bridge/tree/dev)
|
||||
[![CircleCI](https://circleci.com/gh/k1rill-fedoseev/eth-to-bnc-bridge/tree/master.svg?style=svg)](https://circleci.com/gh/k1rill-fedoseev/eth-to-bnc-bridge/tree/master)
|
||||
|
||||
## Ethereum to Binance Chain bridge
|
||||
|
||||
|
@ -21,4 +21,4 @@ Collecting confirmations for the Binance Chain is made in form of mutlisig walle
|
|||
|
||||
At this version the tool for TSS is used as is. It is assumed that later part of TSS orchestration will be moved to the orchestration contract. So far, the orchestration contract is used as a database to keep data required by TSS parties during the signature generation.
|
||||
|
||||
Read [an instruction how to run a demo](DEMO.md) for the bridge.
|
||||
Read [an instruction how to run a demo](DEMO.md) for the bridge.
|
||||
|
|
Loading…
Reference in New Issue