Chris

@HughParry

@HughParry sorting by reporting on status API of provider, which can in turn tell us if the db is up.

I _can_ successfully deploy with substrate contracts node. This deploy failure relates to building the following substrate version: ``` commit 1cc97dd30537997ff4c9827beb2ef0cac9c49063 (HEAD -> polkadot-v0.9.34, upstream/polkadot-v0.9.34) ``` ``` ➜ substrate git:(polkadot-v0.9.34)...

Hi @HCastano, building the contract with the [latest ink release candidate](https://github.com/paritytech/ink/tree/v4.0.0-rc) makes no difference when deploying. The same error message appears. This time I was using the latest cargo contract...

Hi, I upgraded cargo contract to version 2 using ``` cargo install cargo-contract --version 2.0.0 ``` ``` cargo contract --version cargo-contract-contract 2.0.0-unknown-x86_64-unknown-linux-gnu ``` I upgraded substrate to branch `polkadot-v0.9.37` ```...

Can confirm this issue still exists with `polkadot-v0.9.39` branch. ``` (base) ➜ substrate git:(polkadot-v0.9.39) ✗ ./target/release/substrate --version substrate 3.0.0-dev-1837f423b49 ``` The contract does deploy with polkadot apps.

@wottpal Thanks for letting me know. The version changes with PJS are pretty tricky. We run into this issue constantly and we'll need to bump our own stuff to v11...

> Sorry, but I'm very confused... What do you mean that you tried to use it as a "drop in replacement for PJS"? Could you please share the code that...

> A straight switch to PAPI I just mean that `ApiPromise` from PJS was switched out for `createClient` from PAPI and the resultant objects were passed around in the faucet...

Having written a ["plugin", of sorts, for removing excess stuff from PolkadotJS](https://github.com/prosopo/captcha/blob/main/dev/config/src/polkadot/exclude.ts), I found that many things you would expect to be removed by tree shaking were still included when...