Type: Bug
Cannot submit work for a bounty posted on Rinkeby using Chrome and Metamask extension (4.5.5).
The submit work screen appears, all fields have the (apparently) correct data.
When I click _Submit_, Metamask opens but shows the wrong gas limit (6 mil) and _"Transaction Error. Exception thrown in contract code."_ message (see attached screenshots).
After approving the transaction, it soon fails and I am sent back at the first screen.
The transaction should pass and I should be able to claim the bounty.
I am unaware if this is a general issue with Rinkeby or/and Metamask, so I am describing the steps to reproduce for _that particular bounty_:
Screenshots:


cannot claim bounty bc its expired. should be fixed when https://github.com/gitcoinco/web/issues/445 is merged
https://github.com/gitcoinco/web/commit/0287e7734340233ec1f19a19629ea0e948e04c36#r28508476
normally you can submit work after the expiration date.. but it looks like that was accidentally reverted in the above commit. i've put in a fix.
cc @mbeacom @vs77bb @PixelantDesign we should be prepared for questions about why submissions after expiration date aren't working.. looks like the reverted code was submitted a month ago.
鈿★笍 A tip worth 0.05 ETH (19.78 USD @ $395.53/ETH) has been granted to @JDFind for this issue from Mitchell Adam Kosowski XI. 鈿★笍
The sender had the following public comments:
Thanks for your bug discovery and documentation! Please keep it up and tell your friends about https://github.com/gitcoinco/web/issues/760 :) Bug Bounty 6/6 for Pilot Study Sent. Pilot study complete!
Nice work @JDFind! To redeem your tip, login to Gitcoin at https://gitcoin.co/explorer and select 'Claim Tip' from dropdown menu in the top right, or check your email for a link to the tip redemption page.
Hey @owocki, any update on this issue?
@JDFind this has been resolved ASAIK
Right now -> If as long the bounty hasn't expired , you should be able to submit it
We are yet to add a UI pop up that tells the hunter that it's expired and parallely send a notif to the funder to say someone has requested for the issue timeline to be extendede
@thelostone-mc
I tried submitting work to the same bounty and still get the same "transaction failed in contract code" error inside Metamask, then send it anyway, only to have the transaction fail afterwards.
Here is the txn: https://rinkeby.etherscan.io/tx/0x6be37d960da42c157f89c550f13c63d494ff8f2ae435b82a55d5849f64036461
At this point I will communicate with the author to post a new bounty, but the underling issue doesn't seem fixed.
as i explained in https://github.com/gitcoinco/web/issues/854#issuecomment-380116048, the issue is expired and was not created after we fixed https://github.com/Bounties-Network/StandardBounties/issues/25 -- that is why you cannot submit the bounty.
there is no fix we can put in as the smart contract is immutable. if this was a mainnet bounty id say we should cancel it and pay out via other means, but its not -- its just a rinkeby bounty.. so i'm not sure it matters if it gest submitted and paid out.
@JDFind i can send you two RETH if you want. DM me your address
@owocki
Ah, I didn't thought of it that way, it makes sense now.
Thanks for the info. :)
glad to makes sense now :)
Most helpful comment
https://github.com/gitcoinco/web/commit/0287e7734340233ec1f19a19629ea0e948e04c36#r28508476
normally you can submit work after the expiration date.. but it looks like that was accidentally reverted in the above commit. i've put in a fix.
cc @mbeacom @vs77bb @PixelantDesign we should be prepared for questions about why submissions after expiration date aren't working.. looks like the reverted code was submitted a month ago.