D
D
Documentation
Search…
Full Node

Litmus RPC nodes

By default, Litmus has a few self-hosted, load-balanced RPC nodes which provide public service. Contrary to collators, the RPC nodes don't produce blocks but only sync the chain states and provide RPC/Websocket services to the users.
You can find the Litmus RPC entrypoint here on polkadot-js.
With the service, the end-users can query the chain state, inspect the constant and storage, and execute extrinsics.

Run your own full nodes

using docker

1
docker run litentry/litentry-parachain:latest \
2
--base-path=/data \
3
--chain=litmus \
4
--pruning=archive \
5
--ws-external \
6
--rpc-external \
7
--rpc-cors=all \
8
--execution=wasm \
9
-- \
10
--chain kusama
Copied!
If you want to use a specific release version other than latest, simply replace the docker tag accordingly. All docker tags can be found on docker hub.

using command line

To get the litentry-collator binary, either build it from source code or download it from the release page.
Only the Linux x64 version is built and published on the release page, for other platforms, please either build it from source code or use docker.
To start the node:
1
litentry-collator \
2
--chain=litmus \
3
--pruning=archive \
4
--ws-external \
5
--rpc-external \
6
--rpc-cors=all \
7
--execution=wasm \
8
-- \
9
--chain kusama
Copied!
After launching, the websocket service should be available at port 9944 and RPC service should be available at port 9933.