@juanfranblanco I'm having project where we can possibly have a lot of pending smart contracts transactions (all types, contract deployment, read only txs, regular state change txs) on one account, but sometimes when we try to have multiple at the same time we receive "gas required exceeds allowance". We are using one instance of web3 and we are maintaining nonce in memory in order to have always correct nonce of next transaction (can this have downsides if there are a lot of pending transactions and some of them fails and is not mined?) Also we are using Nethereum 2.5.1, did something change in RC regarding this things? Cheers

Hi @juanfranblanco , I'm used to the web3.js version of the RPC but due to work am exploring the Nethereum stack. I just had a couple questions. First, does this currently have support for websockets? Second, if it does, or does not, is it possible for Nethereum contract wrappers to fire on an event and for me to read the event in real time?

@VoR0220 I am doing a POC for event enumeration / processing at the moment. It’s on the block chain processing project Juan mentioned above. The use case is almost exactly as you describe. I’ll be pushing to the master branch tomorrow. It’ll be easy to inject your own handlers for the events.