Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploying Smart Contracts hangs, takes your money but just do nothing. Transaction fees should be refundable when a contract creation fails #400

Closed
ghost opened this issue Mar 18, 2022 · 4 comments

Comments

@ghost
Copy link

ghost commented Mar 18, 2022

Hello,

At the moment I have been trying to deploy the contracts I have been working on to mainnet. I have lost probably around 2,000 USD trying to get somewhere with this network but it just seems to fall on deaf ears.

Basically deploy a modest sized contract. And if you are lucky it deploys if not then bad luck your money is gone with absolutely no trace of it.

I already feel the pains of any developer trying to do something on this network and fail to do so because the network just keeps taxing you more and more money on the transaction fees with no way to get a refund.

@yihuang
Copy link
Collaborator

yihuang commented Mar 18, 2022

https://rpc-cronos.crypto.org/tx_search?query=%22ethereum_tx.ethereumTxHash=%270x9fd351953d4085b54efb5003c865c59cad945affa1f970ebb971387d59bf808b%27%22

I take your latest contract deploy tx hash and checked the error message with above url, it shows: contract creation code storage out of gas. so it's indeed an out of gas issue.
Unfortunately, there's indeed this gas refund issue on mainnet(#221), it's fixed in next version, because it's a consensus breaking change, so have to wait for the next breaking upgrade, hopefully early Apirl.
My suggestion is always use estimate gas to get the accurate gas limit first for now.

@ghost
Copy link
Author

ghost commented Mar 18, 2022

It is using the gas estimate I tested in different ways.

  • Raising the gas price
  • Letting it do it itself. Which at the end of the day is the same it would either get the tx make it look like a success. And it would also most of the time just "hang" and take the fees.

@yihuang
Copy link
Collaborator

yihuang commented Mar 18, 2022

Can you share the tx object so I can try to reproduce it locally?

@yihuang
Copy link
Collaborator

yihuang commented Aug 18, 2022

There were unlucky tx scenarios where tx fee is deducted while can't be found in json-rpcs, I believe they are already fixed in v0.7.x upgrade, closing now, feel free to reopen if it happens again.

@yihuang yihuang closed this as completed Aug 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant