Tomek Drwięga

@jakehemmerle I'd recommend switching to ethers, this package is barely maintained.

Can you elaborate more on a use case for this?

Interesting might be an issue with web3 client library or http server. Perhaps the payload is just too big. Will investigate when I have a bit more time.

@usd-yamazaki thanks for the input, will try out to reproduce today. Perhaps we can create a mock server (say in node.js) to figure out if the issue is part of...

@fubuloubu If your goal is to compile to WASM, I think that: ``` $ cargo check --target wasm32-unknown-unknown --no-default-features ``` would be a good starting point. Then fixing dependencies one-by-one...

I just re-read that you want to use it inside substrate runtime. This will cause additional issues and require `no_std` feature and depending on `core/alloc` stuff. Switching to `BTreeMap` imho...

Hi @afck! sorry for a late answer, that's definitely an awesome idea, we are working on a solution internally in Parity as well to figure that out. Static contract interface...

Indeed, deployment using a signed account is not really supported, it shouldn't be that hard to add though. Take a look at: https://github.com/tomusdrw/rust-web3/blob/a0c18680646828df5c70500c7de28bedfa609f9f/src/contract/mod.rs#L288 and it needs to be plugged somewhat...

Yes, I think so.

The no-value return type is `()`, have you tried that?