David Cumps

So this error occurs because you use `ASSET_BALANCE_METHOD = "lp_asset_balance"` while it should be `ASSET_BALANCE_METHOD = "lp_asset_balances"` Just checking, did you try this out? :)

It seems the error comes from the default `auto_discover = True` in `SubstrateInterface`, this seems to solve it: ```python instance = SubstrateInterface(url=url, auto_discover = False) checker = await cls.run_in_thread(instance.supports_rpc_method, CONSTANTS.ASSET_BALANCE_METHOD)...

Added a bunch of fixes in this PR so you can merge it: https://github.com/KodeSage/hummingbot/pull/4

Fyi: up to you again now @KodeSage to test it out before I review more :)

Let's test it first ;)

I would love to have this back too. We pass in the desired architecture in our CI pipeline and build scripts because we have both windows and Linux machines.

This would be great, it would allow to build a rigid baseplate over a big surface (bigger than my 3d printer's print area)

feel free to tag me when you got some chainflip specific questions, I'm a community member who uses the lp api a bit and will try to help you out...

So to run `chainflip-lp-api` you can use this docker compose: ```yaml services: lp: image: chainfliplabs/chainflip-lp-api:berghain-1.4.5 pull_policy: always stop_grace_period: 5s stop_signal: SIGINT platform: linux/amd64 restart: unless-stopped user: root ports: - "127.0.0.1:10589:80"...

@nikspz @fengtality I dont think you need to add Chainflip as an EVM-chain? Chainflip is not a chain you can send assets on, it's an application-chain built on Substrate. Users...