mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-05-30 22:11:02 +00:00
Hernando Castano
3236aa8000
* 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: Tomasz Drwięga <tomusdrw@users.noreply.github.com>
Substrate-to-Substrate Bridge Relay
The bridge relay is a process that connects to running Substrate nodes and sends data over the Substrate-to-Substrate bridge. The process communicates with the nodes over the JSON-RPC interface and reads data from the relays information required by the bridge pallet using runtime calls and writes data to the modules by constructing and submitting extrinsics.
For more details, see the design document.
Status
This is a not-in-progress prototype.
Running in development
Run two development Substrate chains:
> TMPDIR=(mktemp -d)
> cd $TMPDIR
> substrate build-spec --dev > red-spec.json
> cp red-spec.json blue-spec.json
# Modify the chain spec in an editor so that the genesis hashes of the two chains differ.
# For example, double one of the balances in '$.genesis.runtime.balances.balances'.
> substrate --chain red-spec.json --alice --base-path ./red --port 30343 --ws-port 9954
> substrate --chain blue-spec.json --alice --base-path ./blue --port 30353 --ws-port 9964
Now run the bridge relay:
> target/release/substrate-bridge --base-path ./relay \
--rpc-url ws://localhost:9954 \
--rpc-url ws://localhost:9964