You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know this is outside of the scope right now, but is there a way to omit relay chain for networks that don't have it?
relay_chain:
chain: "xxnetwork"wss: ws://192.168.1.70:63007create_db: true # Set to true if database needs to be createdretain_db: true # Set to true to retain database after the end of process.
...
It appears that without it one could hack the startup script, but what happens after that is probably not good (haven't gotten that far, but I assume). If it could be skipped in config file and later (if relay_chain == None, etc) , that would let us proceed even at the cost of some functionality being unavailable and I could live with that.
Another question/problem (maybe not highly relevant now, but..): what is the chain value supposed to be? Is that arbitrary or based on the SS58 registry entry entries? For some network this doesn't matter, but our network name has a space in it, but in SS58 registry it does not.
For relay_chain we use solo for chains that are neither polkadot nor kusama. I believe the chain name is arbitrary and probably best not to include spaces.
@armchairancap Added a little more info on how to setup the config.yaml to README.
Also added default values for relay_chain and chain in case if you don't add anything on the config file.
I know this is outside of the scope right now, but is there a way to omit relay chain for networks that don't have it?
It appears that without it one could hack the startup script, but what happens after that is probably not good (haven't gotten that far, but I assume). If it could be skipped in config file and later (
if relay_chain == None
, etc) , that would let us proceed even at the cost of some functionality being unavailable and I could live with that.Another question/problem (maybe not highly relevant now, but..): what is the
chain
value supposed to be? Is that arbitrary or based on the SS58 registry entry entries? For some network this doesn't matter, but our network name has a space in it, but in SS58 registry it does not.My network RPC and ID (+ metadata):
ss58_format=55
(Metadata file: xxnetwork.json (V14))The text was updated successfully, but these errors were encountered: