You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are on this one, we also tried the non-archive one
It does seem like they are hanging with no specific error message
We are sending the tx in a standard way, no special params that I know of are supplied
It's a regular transaction to our message gateway contract, all I have is the computed hash, I don't have a standalone script to share no sorry
Nibiru:
Maybe taking a step back, have you completed any successful transactions on the chain?
Via Labs:
Simple transfers or deploying other contracts, for example
There have been some config and transfers from quite a while ago when we initially deployed
Is there anything you can look up in your network with that hash? I don't believe we can do that from the explorer
In general the system then just works, as we have it running on over 250 testnetd and mainnets so that's why I'm a bit lost what to kick on our side
In both cases, the cli command did not receive a response from the node and it seems like the command was stuck. But the node successfully processed the tx.
github-actionsbot
added
the
S-triage
Status: This issue is waiting on initial triage. More Info: https://tinyurl.com/25uty9w5
label
Oct 18, 2024
Unique-Divine
added
x: evm
Relates to Nibiru EVM or the EVM Module
and removed
S-triage
Status: This issue is waiting on initial triage. More Info: https://tinyurl.com/25uty9w5
labels
Oct 18, 2024
Problem Evidence 1
Nibiru:
If the txs are hanging, they may be failing silently. Could you share the settings you're using to broadcast the transaction, so we can help debug?
Via Labs:
https://evm-rpc.archive.devnet-3.nibiru.fi
Chain ID: 7222
We are on this one, we also tried the non-archive one
It does seem like they are hanging with no specific error message
We are sending the tx in a standard way, no special params that I know of are supplied
It's a regular transaction to our message gateway contract, all I have is the computed hash, I don't have a standalone script to share no sorry
Nibiru:
Maybe taking a step back, have you completed any successful transactions on the chain?
Via Labs:
Simple transfers or deploying other contracts, for example
There have been some config and transfers from quite a while ago when we initially deployed
Is there anything you can look up in your network with that hash? I don't believe we can do that from the explorer
In general the system then just works, as we have it running on over 250 testnetd and mainnets so that's why I'm a bit lost what to kick on our side
Note on Forge/Foundry
feat(evm-forge): foundry support and template for Nibiru EVM develoment #2084
Problem Evidence 2
For example, when interacting with a Solidity contract to execute a tx:
or when deploying a contract via Forge,
forge create Nibiru --rpc-url=http://127.0.0.1:8545 \ --mnemonic="guard cream sadness conduct invite crumble clock pudding hole grit liar hotel maid produce squeeze return argue turtle know drive eight casino maze host" \ --nonce=2 --gas-price=10
In both cases, the cli command did not receive a response from the node and it seems like the command was stuck. But the node successfully processed the tx.
Also,
to retrieve the TX receipt returned the following error:
Haven't verified the root cause though
The text was updated successfully, but these errors were encountered: