Marcus Mönnig

I'm seeing the same problem when putting parity under rpc load: ``` 2019-03-07 11:05:34 UTC Starting Parity-Ethereum/v2.3.5-stable-ebd0fd0-20190227/x86_64-linux-gnu/rustc1.32.0, 2019-03-07 11:05:34 UTC Keys path /root/parity_chain/keys/ethereum, 2019-03-07 11:05:34 UTC DB path /root/parity_chain/chains/ethereum/db/... 2019-03-07...

Since 2.3.5. was really unsuable for me, I've updated to v2.4.0-beta ~~and I no longer see any problems.~~ After some time and RPC load I again see ```Error serving connection:...

I'm running parity in Docker and noticed that once I removed the parameters "--ws-interface=0.0.0.0", "--ws-origins=all", I no longer see the problem.

"Finish smart contract" needs a better defintion, but maybe not in this issue. How much time do we have until we actually want to deploy our contract? Minus the time...

I propose: https://zeppelin.solutions/ :-)

https://www.reddit.com/r/ethdev/comments/78ugki/do_indexed_parameters_in_events_cost_more_gas/ 375 + unindexedBytes * 8 + indexedTopics * 375 event Deposit(address token, address user, uint amount, uint balance); 375 + (20+20+32+32) * 8 + 0 * 375 = 1207...

Which parameters to index? Only up to three parameters per event are indexable. event Order(address **tokenGet**, uint amountGet, address **tokenGive**, uint amountGive, uint expires, uint nonce, address **user**); event Cancel(address...

https://ethereum.stackexchange.com/questions/40396/can-somebody-please-explain-the-concept-of-event-indexing explains it better than I could.

There's more to indexing parameters. Example for ECR20 token contract 0x9e96604445Ec19fFed9a5e8dd7B50a29C899A10C which defines the event: ` event Transfer(address indexed from, address indexed to, uint256 value); ` Example tx: https://etherscan.io/tx/0x5fc21564240314ee2cbc87c2a854afc75f6e0692c4325a91226ecf14a7f928fc where...

freeatnet: > self-healing is basically > - schedule orders to be queried whenever (or often enough) when someone requests the orderbook > - try to update orders that haven't been...