Chain (evm/evmlight) returns timeout for every write call

[iotaledger]

Chain (evm/evmlight) returns timeout for every write call

[dahof1]

Update:
Somehow it feels like it has something do to with the transaction nonce. The waspdb was not purged between the various develop releases and write calls stopped working after some block time. The strange thing is that i also don't get nonce errors anymore when i send some wrong nonce. I only see the the timout errors.

Just speculation but could it be that the nonce get out of sync with the new block time feature?

[dessaya]

I can't find anything interesting in the logs either.

Why do you think that the nonce is involved? (I take it you are referring to the nonce in the ethereum transaction).

Does the timeout only happen with the jsonrpc calls? Does something like wasp-cli chain info or wasp-cli chain deposit still work?

[dahof1]

Hi @dessaya,

it was just a wild thought :) because i spotted some (ethereum transaction) nonce errors before the timout occours. But it was just speculation.

wasp-cli chain info works, wasp-cli chain deposit returns a timout.

[dessaya]

Ok, so then I guess the consensus is somehow stuck.

@lunfardo314 @kape1395 maybe you can provide some insight?

[dahof1]

Today in the morning i setuped a fresh chain, wiped all db, logs etc. Returned in the afternoon to my setup and experienced again the timout error (on deposit, rpc was not running). I dont know if you guys can reproduce this... i will try it again (wipe all again, init a new seed...).

[Juliusan]

As I see it, level 1 took too long to approve the transaction. Am I right that you set the request handling timeout to 1 minute? I see, that request was received by node 0 at 2021-11-13T14:45:53Z and it was passed to L1 at 2021-11-13T14:45:59Z. However updated state has been received from L1 only at 2021-11-13T14:47:03Z. So the timeout occurred ~10 seconds before the success. But the request was accepted correctly.

[Juliusan]

By the way, I assume, the logs were produced using commit a6aed6275b157d92b76c01ebcbef19fdb9f2a382. It is important to know the exact version, as develop branch changes a lot and it might get confusing reading logs of different wasp version than the code is at.

[dahof1]

Hi @Juliusan,
the logs where produced with commit 3cd1e06

[dessaya]

Thanks @Juliusan !!

@dahof1 So if the request is being accepted, then after something like wasp-cli chain deposit IOTA:100 you should be able to check the balance with wasp-cli chain balance <your agent id> and see that it actually changed after a while, even if you got the timeout error. Is this the case?

[Juliusan]

@dahof1, thanks, I checked. It is one pull request earlier than I guessed. My comments should still stand.

[dahof1]

Hi @dessaya,

mmh... no unfortunately not. The balance stays the same. How long could it take? I waited a couple of minutes.

[dahof1]

I could reproduce this issue with an other chain:

EVM Flavor: evmlight
Commit: ebf4133

Created the chain on 2021-11-18, around 8:30 pm. Chain was running smoothy until block #13013 (blockTime 3s). Since then no block gets minted anymore.

wasp-cli chain deposit IOTA:1 gives timout, wasp-cli chain balance A/1GYusVqm3ip8Guq5dFFqYV5XLXsug1MPqNe5kC2Kcx1PZ::00000000 stays the same.

[fijter]

Hey guys, thanks for reporting. The bug is likely an issue due to a bug in GoShimmer - Given our full focus is on converting to Hornet for mainnet support right now we prefer not to spend much time on debugging this until we can try and replicate it on Hornet. Let's park it for now and revisit once we have a first version of that and go from there. If it's still an issue at that point we surely need to get to the bottom of it. Hope you understand.

[dahof1]

Thanks @fijter for the update! Then let's do it like this

[AdamEunson]

@fijter just wondering if there has been any movement on this or any temporary fix. We're looking at the Tangle Labs NFT launch on Friday, and this is currently a blocker to the release for us, so would be interesting to see what we can do to ensure a smooth NFT release. Thanks

[jigsnptel]

As I see it, level 1 took too long to approve the transaction. Am I right that you set the request handling timeout to 1 minute? I see, that request was received by node 0 at 2021-11-13T14:45:53Z and it was passed to L1 at 2021-11-13T14:45:59Z. However updated state has been received from L1 only at 2021-11-13T14:47:03Z. So the timeout occurred ~10 seconds before the success. But the request was accepted correctly.

how can i see all these details, once i have deployed contract using remix and metamask

[jigsnptel]

pls help

[jorgemmsilva]

The current EVM implementation on master branch will be deprecated soon.
We will be releasing the new shimmer-compatible ISC which will run in the new network (currently the devleop branch). A lot of things have changed and its likely this issue no longer applies.