-
Notifications
You must be signed in to change notification settings - Fork 191
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
Gas fee estimate for trade different than Metamask #526
Comments
@SS-FOX-McCloud - any concerns to bounty this one out? Seems like it should be a straightforward fix for a new contributor. |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 250.0 FOX (171.47 USD @ $0.69/FOX) attached to it as part of the ShapeShift fund.
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Workers have applied to start work. These users each claimed they can complete the work by 1 week, 6 days from now. 1) hyuze has applied to start work (Funders only: approve worker | reject worker). Make sure that I am carrying out tasks as stated to ensure full completion. Learn more on the Gitcoin Issue Details page. |
Hey, I just took a look at this issue. Is there any chance that the problem is with the gas value sent by the API? I haven't checked the API that Metamask uses yet, but it might be sending a different value. |
Hey @armr-dev - I just saw your comment on the other GH issue I had approved you for work on. I didn't realize someone had already submitted a PR for that since I didn't approve their work. Anyways, I appreciate you bringing that up. Would you want to pick this one up instead? Happy to have you dive in and see if you can figure out a fix and if the fix is more complex than originally expected, I am very willing to make sure we can get more FOX heading your way ;) Thanks for the interest in ShapeShift and the great communication so far. |
Hey! I already took a look at this one. It does look complex, but that won't keep me from trying 😎. I will be working on this one and will keep you updated on the progress. |
@armr-dev - awesome, can you apply for the bounty on gitcoin here and i will approve you? https://gitcoin.co/issue/shapeshift/web/526/100027238 Also - on Monday the rest of the team will be around, and we can happily answer any questions in our discord |
Done! I'll join the Discord server. Ty! 😊 |
⚡️ A tip worth 200.00000 FOX (138.18 USD @ $0.69/FOX) has been granted to @armr-dev for this issue from @0xean. ⚡️ Nice work @armr-dev! 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.
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Workers have applied to start work. These users each claimed they can complete the work by 1 month, 1 week ago. 1) sdmg15 has applied to start work (Funders only: approve worker | reject worker). I want to take a look at this when it's rebountied ... :) I want to take a look at this task. Learn more on the Gitcoin Issue Details page. |
Adding some more info from @pastaghost on where to look,
|
Hello, I am a software engineer with 6 years of experience in JS/TS and React. I am interested in dipping my toes into web3 development. This looks like something that might be a good place to start. I have already applied on gitcoin. Thanks! |
I have the fix for this issue, even though the culprit is not in this repo ;) Let me know if I can send a PR. I applied to gitcoin also. |
@Neurone - Will approve you now. Yea, just saw your comment in gitcoin and looking at the screenshots, makes sense! That MaxPriorityFee is way off. Anyways, will approve you now and yea, the PR is probably in TY. |
The bug is in the hdwallet library. It seems safe to disclose it but, just to be extra sure, I already sent an inquiry to the security team following the responsible disclosure program, I used the ticket form via zendesk. As soon as they give me green light I'll publish the PR. |
Appreciate the caution. (CC @reidrankin please see above) |
@Neurone - confirmed with our Security workstream that you are fine to publish. |
Sent the PR, I summarize also here the problem. Metamask and other web3 libraries (i.e. |
fixed in shapeshift/hdwallet#389 - will need to up hd wallet version in web |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work for 600.0 FOX (244.6 USD @ $0.41/FOX) has been submitted by: @0xean please take a look at the submitted work:
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done The funding of 600.0 FOX (178.9 USD @ $0.3/FOX) attached to this issue has been approved & issued to @Neurone. Additional Tips for this Bounty:
|
@0xdef1cafe the latest published shapeshift/hdwallet is still Side note: there is also some misalignment about the tagging on that repo; the last tag was |
comment above still valid as of writing, requires new hdwallet version to publish, likely to come week of 2/21 |
@0xdef1cafe - to check with highlander on the release of HD wallet |
@Neurone hdwallet finally got released - are you interested in picking this back up? |
`Successfully published:
version 1.19.0 is published should be gtg @Neurone |
Sure, no problem. It should be just a matter of an upgrade in package.json. I can send a PR for that. |
When a user previews a trade on V2 using Metamask, the gas fee estimate given is significantly different than the gas fee given by the Metamask extension when signing the trade.
A/C:
The text was updated successfully, but these errors were encountered: