Skip to content
  1. Jul 28, 2020
  3. Jul 27, 2020
    • Hernando Castano's avatar
      Allow Multiple Bridge Pallet Instances (#226) · 639b7664
      Hernando Castano authored 
      

* Add Instance type parameter to pallet

* Sketch out what the runtime could look like

* Allow runtime to compile with multiple bridge pallets

* Cargo Fmt

* Allow an instance of a PoA chain to be used with currency-exchange

I specify that it's only _an instance_ instead of _instances_ since the currency-exchange
pallet does not support multiple instances itself. What this commit does is make it so
that the different instances of the PoA chains we currently have are compatible with the
currency-exchange pallet through the implementation of the PeerBlockchain trait.

* Add Instance type parameter to Currency Exchange pallet

* Wire up currency exchange intances in runtime

* Rust Fmt

* Show sccache

* Allow Eth pallet to use a default instance

* Use a default instance in Eth pallet tests

* Remove Rialto and Kovan feature flags

Through some discussions it has been decided that the `bridge-node` should, like
Substrate's `node-template`, be a showcase of the different pallets available in
a project. Because of this I've removed the feature flags for the Rialto and Kovan
networks in favour of having both of them included in the runtime.

* Update the chain_spec to use both Rialto and Kovan configs

* Update pallet level calls used by Substrate client

Allows the project to compile. However, it should be noted that in reality
we shouldn't be hardcoding the pallet we're calling.

* Allow currency-exchange pallet to use a default instance

* Support benchmarking an instance of the Eth pallet

* Update currency exchange benchmarks to work with instances

* Fix test helpers which now need a PoA instance

* Remove Actions for checking Rialto and Kovan features

* Add missing comments

* Update Runtime API string constants

* Add issue number for generic chain support in relay

* Add Runtime APIs for instances of the currency-exchange pallet

* Rust Fmt

Co-authored-by: default avatarDenis S. Soldatov aka General-Beck <[email protected]>
      639b7664
    • Svyatoslav Nikolsky's avatar
      Auto relay exchange transactions (#227) · 4e919b8d
      Svyatoslav Nikolsky authored 
      

* auto relay exchange transactions

* docker + auto-relay-tx

* clippy

* jsonrpsee in Cargo.lock ???

* fix tests compilation

* Show sccache

* mute clippy

* move

* Update relays/ethereum/src/exchange.rs

Co-authored-by: default avatarHernando Castano <[email protected]>

* finish comment

* (bool, String) -> StringifiedMaybeConnectionError

* Update deployments/rialto/docker-compose.yml

Co-authored-by: default avatarHernando Castano <[email protected]>

Co-authored-by: default avatarDenis S. Soldatov aka General-Beck <[email protected]>
Co-authored-by: default avatarHernando Castano <[email protected]>
      4e919b8d
    • dependabot-preview[bot]'s avatar
      Bump serde_json from 1.0.56 to 1.0.57 (#235) · a98a1e23
      dependabot-preview[bot] authored
      a98a1e23
    • dependabot-preview[bot]'s avatar
      Bump sysinfo from 0.14.13 to 0.15.0 (#234) · 2b0ff1e5
      dependabot-preview[bot] authored
      2b0ff1e5
  5. Jul 21, 2020
    • Hernando Castano's avatar
      Add Prometheus and Grafana to Docker Compose (#221) · d284b84f
      Hernando Castano authored 
      * Add Prometheus and Grafana to Docker Compose

* Expose relay's Prometheus metrics port

* Use Docker network references intead of localhost

When you have containers on the same network they don't communicate
over localhost, they instead refer to their container names

* Move dashboard components into deployment folder

* Update folder structure for Grafana and Prometheus config files

The new folder structure more closely matches the expected defaults
by Grafana and Prometheus, which allows us to clean up the paths
in our docker-compose file a bit.

* Add documentation about Prometheus and Grafana

* Refer to Prometheus server instead of node
      d284b84f
  7. Jul 20, 2020
  9. Jul 17, 2020
    • Svyatoslav Nikolsky's avatar
      Relay dashboard (#191) · 6be18c57
      Svyatoslav Nikolsky authored 
      * expose metrics for Prometheus

* added preconfigured configs for Prometheus and Grafana

* metrics-related cli args

* fix compilation
      6be18c57
    • Tomasz Drwięga's avatar
      Rialto test network setup (#163) · 010c65be
      Tomasz Drwięga authored 
      

* Dockerfile for OpenEth.

* Add relayer dockerfile.

* Add docker-compose.

* Working on the relay.

* Bump a bunch of deps.

* Change relay branch.

* Running a 3-validators poa network.

* Add bridge nodes.

* Conditional compilation of bridge configs.

* Fix genesis hash.

* Disable features build.

* Disable empty steps.

* Work on sub2eth

* Add some logs.

* More logs.

* Fix compilation.

* Add chain-id parameter to relay.

* Unify bridge-hash.

* Update the hash.

* Ditch sub2eth for now.

* Add some docs & proxy configuration.

* Fixes.

* Fix remaining issues.

* Increase health timeout.

* Make sure to install curl for health monitoring.

* Fix kovan.

* Fix build.

* Create if does not exist.

* Fix benches.

* Revert CLI params requirements.

* cargo fmt --all

* Apply suggestions from code review

Co-authored-by: default avatarHernando Castano <[email protected]>

* Add some docs.

* Update BRIDGE_HASH to master

* Duplicate compose file.

* Rename testpoa to Rialto.

* Fix borked merge.

* Fix entrypoints to take arguments.

Co-authored-by: default avatarHernando Castano <[email protected]>
      010c65be
  11. Jul 14, 2020
  13. Jul 10, 2020
    • Svyatoslav Nikolsky's avatar
      do not panic when logging is enalbed (#180) · e5d939f0
      Svyatoslav Nikolsky authored
      e5d939f0
    • Hernando Castano's avatar
      Update Substrate to rc4 (#175) · dbf6ac71
      Hernando Castano authored 
      

* Bump Substrate to rc4

* Add BaseCallFilter type

* Add DenyUnsafe to SystemApi extension

* Use new ServiceBuilder build functions

* Add BaseCallFilter to test runtimes

* Remove old comments

* Add `rev` and `git` fields back

Turns out that if you don't have these future release candidates will
be used if available. For instance, once `rc5` is released a fresh pull
would use that instead of `rc4` which is what we want.

* Use tag release instead of specific commit

Will make scripted updates easier in the future

* Add short script to update between `rc` versions

* Update scripts/update_rc.sh

Co-authored-by: default avatarTomasz Drwięga <[email protected]>
      dbf6ac71
  15. Jul 08, 2020
  17. Jul 06, 2020
  19. Jun 29, 2020
  21. Jun 23, 2020
    • Hernando Castano's avatar
      Switch to new RPC interface (#131) · 5bf635e6
      Hernando Castano authored 
      

* Move EthereumRpc implementation to Eth client

* Move SubstrateRpc implementation to SubstrateClient

* Update deploy_contract to use new RPC interface

* Fix some types in the Substrate client

* Swap out method bodies in Eth sync loop

* Swap out method bodies in Substrate sync loop

* Remove Client from SourceClient trait return types

* Remove Client from TargetClient trait return types

* Remove client from Source select! arms

* Remove client from Target select! arms

* Add missing mutable refs in Substrate client

* Use mutable references in Source/Target Client traits

* Try and use mutable references in Source/Client trait implementations

* Handle errors more gracefully

* Remove unused imports

* Remove dead_code and unused_variables lints

* Remove usage of `jsonrpsee::RawClient`

By using a `jsonrpsee::Client` we are able to remove all the shared
mutable references required when interacting with the RPC server. This
is convenient as trying to sharing mutable references in code that uses
async/await is a bit of a pain.

However, using a `Client` instead of a `RawClient` is not yet supported
by the `jsonrpsee::rpc_api` macro, so a fork must be used for the moment.

* Clean up dead code and warnings

* Clean up higher level RPCs

Some of the RPCs that were "high level" didn't necessarily belong
as part of the trait, so they were removed.

* Use positional parameters for RPCs

Both Substrate and Ethereum's RPCs use positional (array) parameters,
so in order to be compatible with both we need to make sure that
our API is defined with positional paramters in mind.

* Rename argument for eth_getBlockByNumber

* Remove some unecessary Ok-wraps

* Process client requests synchonously

Before the refactoring the sync loop would wait until a client finished
handling a request before issuing another one. This behaviour was
inadvertently changed during the refactoring leading to race conditions.
This commit makes sure that the previous behaviour is respected.

* Reduce the errors that are considered a connection error

* Only decode bridge contract once

* Set genesis_config at RPC client startup

* Fetch genesis hash in SubstrateRpcClient::new()

* Move Decode error into SubstrateNodeError

* Suppress warnings caused by `rpc_api!`

* Implement From RpcError for String

* Handle Substrate client initalization errors more gracefully

* Remove match in favour of ?

Co-authored-by: default avatarSvyatoslav Nikolsky <[email protected]>
      5bf635e6
    • Tomasz Drwięga's avatar
      Update web3 dependency. (#140) · 55f8d744
      Tomasz Drwięga authored 
      * Update web3 dependency.

* Switch to crates.io.
      55f8d744
  23. Jun 22, 2020
  25. Jun 15, 2020
  27. Jun 11, 2020
  29. Jun 08, 2020
  31. Jun 05, 2020
  33. Jun 03, 2020
  35. Jun 02, 2020
  37. Jun 01, 2020
  39. May 27, 2020