Tomek Drwięga

@bryanapperson released `0.16.0` just now, let me know if that's good enough or if there are some unwanted changes and you'd rather have `0.15.1`.

Is the backend you are using actaully producing empty blocks? The `web3` library might simply be waiting for enough confirmations (As the name suggests), but since empty blocks are not...

> `RPC error: Error { code: ServerError(-32000), message: "already known", data: None }` This one seems to be a correct error in case you try to submit a transaction which...

It's because Ganache sends a response which is not a valid JSON-RPC response, since it contains both `result` and `error`. It's a bit similar to https://github.com/tomusdrw/rust-web3/issues/544 The fix would need...

I haven't been looking into Solidity examples, but perhaps the bytecode is a bit outdated now?

> I tried to import this function using [#wasm_bindgen] but the return type of web3::Result is not compatible some one more experienced may be able to help. @bytesoul The `web3::Result`...

I think ideally this kind of throttling should be handled by the transport layer itself. Obviously I'm also fine with exposing this as a typed error. I think `Error::Transport` would...

Related: https://github.com/tomusdrw/rust-web3/pull/585

Can't we spawn a background task to uninstall the filter? Or maybe we shall panic in case it wasn't uninstalled (or at least display an error), wdyt?

The closes we have is `crate::api::accounts::Transaction`, but currently it only implements RLP encoding and is not exposed ([see code](https://github.com/tomusdrw/rust-web3/blob/feaf212f41b8183ea1191fbdf93d6e92877ed9b6/src/api/accounts.rs#L198)) . A decoding counterpart implementation would be required for this. Happy...