Question: Polkadot Mainnet AssetHub Migration Configuration

[pc-quiknode]

Hello There,
In the assethub migration doc I see:

# Primary Asset Hub node
SAS_SUBSTRATE_URL=wss://westend-asset-hub-rpc.polkadot.io
# Additional chain configuration (relay chain in this case)
SAS_SUBSTRATE_MULTI_CHAIN_URL='[{"url":"wss://westend-rpc.polkadot.io","type":"relay"}]'

Would substrate-api-sidecar still work if I point SAS_SUBSTRATE_URL to the relay chain RPC url and point SAS_SUBSTRATE_MULTI_CHAIN_URL to the assethub RPC url?

[filvecchiato]

Hello! There are some edge cases where for staking endpoints this is not ideal. Ideally the SAS_SUBSTRATE_URL is set to the assethub rpc. However, in SAS_SUBSTRATE_MULTI_CHAIN_URL you can declare both the RC and asset hub RPCs specifying the type respectively as "relay" and "assethub", and it should mitigate some edge cases (on top of having the classic rpc string in SAS_SUBSTRATE_URL).

However, Asset hub is meant to be the main connnection between the two since after AH migration, most of the datasets will be in AH and not relay chain.

This being said, if the RPC is set to RC, sidecar would continue working, just that it would provide data available on RC only

[pc-quiknode]

Hello @filvecchiato
Thank you for the clarification.
Can I start setting SAS_SUBSTRATE_MULTI_CHAIN_URL to polkadot mainnet relay chain now for testing already? Is it going to break anything?