Transaction Params (nonce, gasprice, etc)

Question

Transaction Params (nonce, gasprice, etc)

Closed this issue 2 years ago · 10 comments

ethermachine commented 2 years ago

Wondering how to define basic tx data on contract calls.

At the moment can only send the function params but failing due to low nonce (obvious)

ethermachine commented 2 years ago

contract

Answer 1 · 2022-04-07T06:57:38.000Z

Hi, are you talking about abigen generated contracts or the contract package?

Answer 2 · 2022-04-07T08:51:32.000Z

You are correct, there exists a TxnOpts parameter but it is not exposed at the Txn() level. I will change the API to make it available.

Answer 3 · 2022-04-07T12:31:15.000Z

Thanks ! So this means I am the first person trying to send a contract transaction? Or are there alternative most efficient ways like “populate transaction” and then send a regular transaction with the arguments and on that its already possible to define nonce

Answer 4 · 2022-04-07T13:09:07.000Z

I have found an extra problem, the provider for the contract here provider for the contract (which is the default one) does not populate the nonce and it should.

This contract object is new (one month) and it still needs a bit more cleaning to find the rough edges. Thank you for helping!

Answer 5 · 2022-04-07T13:29:27.000Z

Yeah I just seen a Go lang video and went straight forward to this library to learn, as my go playground.
Sorry I am unable to help further

Answer 6 · 2022-04-07T18:49:38.000Z

I have found an extra problem, the provider for the contract here provider for the contract (which is the default one) does not populate the nonce and it should.

This contract object is new (one month) and it still needs a bit more cleaning to find the rough edges. Thank you for helping!

In the meantime, is there any alternative approach to for example populate contract call transaction, and then send with regular tx, via signer and correct nonce? Thanks

Answer 7 · 2022-04-08T08:12:48.000Z

Yes, you could do what contract (here) package does internally and fill in the nonce.

Answer 8 · 2022-04-09T16:23:53.000Z

Yes, you could do what contract (here) package does internally and fill in the nonce.

apparently my go app is importing branch 0.1.0 from the go.dev packages repo. The reference you mentioned is only available in master. Will try to download from github..

Answer 9 · 2022-04-09T19:25:13.000Z

Indeed, that was the first change of the new release. I think I will have time to address this issue this week. I am travelling this weekend.