You lucky dude!
Ok, someone will jump in I hope
You lucky dude!
What exactly do you want to know ? How to distinguish successful and failed contract deployments?
Hey Nikita! Here’s a c/p from one of my previous replies:
- After posting the transaction, what is the correct way then to await for transaction to actually get included in the chain? Should I just wait for every new key block and try to fetch the tx info (as you’ve said, this lasted for 3 hours in my case)? Is there a proper way to do this using js-sdk?
- If I’m creating a contract , I’m only safe to interact with the contract once the creation transaction is provably included in the chain?
- If I’d like to post more then 1 transaction from the same wallet (transactions are not related and order of execution does not matter) can I do this safely? Or I have to go one by one, one per keyblock?
Don’t know if these are clear enough, or actually make any sense… Thanks for any help or info you can provide!
After posting the transaction, what is the correct way then to await for transaction to actually get included in the chain?
If you use the JS SDK’s native way of calling contracts, it returns a
promise once the transaction has successfully been included in a
microblock, no need to manually wait for keyblocks here except if you want to make sure you have a minimum block depth.
If I’m creating a contract , I’m only safe to interact with the contract once the creation transaction is provably included in the chain?
If I’d like to post more then 1 transaction from the same wallet…
…then you need to wait for the first one to get mined before you send the second one, because the
nonce of each transaction is unique and must get mined in a consecutive order. So tx nonce 2 must come after 1, or else it will get rejected.
A hint for the first question: I’ve included a code generator in AEstudio, you can use its output as a working example:
- Deploy a contract, 2. scroll to your function of choice and enter its parameters if necessary, 3. click:
Then you can chose to see the code for SDK setup, contract deployment and function calling , or deactivate tickboxes at the top to see only the desired part (e.g. only contract function calling)
Thanks mate. aestudio looks great, didn’t know about that one!
So the rabbit whole lead me to a certain race condition in nodes communication. There was a lot of digging and eventually I was able to expose this an actually issue in a reproducible test. All tracked and already fixed in this PR. The fix would be deployed in the next release.
In advance: I have no proof this is what we are facing on main net. It is extremely hard to debug in such distributed environment, especially we don’t have any access to the interesting logs. What I am sure is that this is a legit bug scenario and it would be fixed on main net soon.
That’s great news, thanks for all the hard work
Thanks for reporting it Those race conditions are notoriously hard to detect and fix, so let’s see if this fixes it
Hey, I have one more question but I won’t spam with new threads.
Some of my transactions take blocks and blocks before ending up in the chain. I’m tracking one of my transactions now and it’s been almost two hours when it finally it got mined. I’ve checked all the preconditions and transaction looks ok. This is something I’ve started noticing in the past few weeks. Is this related with variable hash rate? Can I do anything about this? Set a bigger gas price, or something. This is slowly killing my UX as the user sees pending transaction on frontend and this can last for hours…
hey @filip, that is actually a very good question you have there, it would actually be wort a new thread but lets keep it here. did this phenomenon occur only when sending the TX through
SuperheroWallet or directly through the
JS SDK or in both cases ? Actually, in both cases you should get a reasonably well gas price estimation automatically, but you can also always set a higher gas price yourself.
I broadcast transactions using js-sdk, the usual
. sendTransaction() method, with the default configuration. And I’ve done this on the mainnet/testnet for some time now, but only recently I’ve started noticing issues… Yeah I can try and double the gas price, I know the default value is 1e9, but I was always told that there is no need to change this value. Do you have any other suggestions? Thanks mate!
I just experienced the a similar issue with my
initially it was included in block
403530, then it was dropped and finally it was included in block
Ok, so I see 2 things now:
- The initial reports were that transaction is orphaned and then gone forever. This seems to be fixed with the introduction of release 5.10.1. Now orphaned transactions are reincluded again, only later on. Although this hurts finality, it seems like an issue had indeed been fixed but there is yet another one to track.
- So far we only had “the transaction is gone forever” which made the tracking of the issue really hard. Now we have some data, investigating generations
403534provides us with some clues what might be going on. I have 2 ideas I’d like to test, will keep you all updated.
Awesome! If you need more data, here’s another transaction hash:
I tracked this one, and it went through the series of transitions: being included at height N only to be excluded moments later (height: -1), then again included in N+1 or N+2 and so on, you get the point. After few transitions, it eventually got mined and included in the chain at height 401597. This might be useful for your research. Let me know if I can help in any other way, cheers!
Yes, this was really valuable, thank you. This excluded a few possibilities…
kk. also happening now with regular spendTx,
Just leaving this here, maybe you can get use of it
Just to let you know, my transactions are now failing regularly. Can’t even spendTx, tried over baseaepp, arkane wallet, everything. Can you confirm? Did you try sending Ae today/yesterday? Try spending and see what happens with the tx and balances
Yes, we are debugging this. We have a clue and it will be resolved soon.
hope to see this fixed soon, thanks! =)