search

smol-dot / smoldot

Lightweight client for Substrate-based chains, such as Polkadot and Kusama.
GNU General Public License v3.0
179 stars 47 forks source link

smoldot doesn't compile rococo asset-hub #1763

Closed josepot closed 5 months ago

josepot commented 5 months ago

It seems to happen when smoldot has many active chains at the same time.

The logs: logs.txt

For context, during this weekend I have been developing a dApp using Polkadot-API with smoldot for teleporting assets. Overall it works fairly well. However, it's not possible to interact with Rococo Asset Hub because for some reason smoldot is not able to compile the runtime.

tomaka commented 5 months ago

I don't see what makes you believe that smoldot can't compile the runtime?

josepot commented 5 months ago

I don't see what makes you believe that smoldot can't compile the runtime?

Maybe I didn't explain myself well. What I mean is that it's not possible for the dApp to interact with the rococo-asset-hub chain. Also, if we search for "compile" in the logs of the console, then we can see this:

image

I assumed that since there is a "Successfully compiled runtime" message for all the asset-hub parachains, other than the rococo one, combined with the fact that the chain is not responsive, that meant that smoldot wasn't compiling its runtime.

Is there anything that we should be doing differently to be able to interact with rococo asset-hub? 🤔

josepot commented 5 months ago

Oh, shut, I just saw what the issue was... There are no TLS Websocket entries in the bootnodes list. Therefore, smoldot can't connect to the chain. 😬