-
-
Notifications
You must be signed in to change notification settings - Fork 775
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
Update Gitcoin for breaking MetaMask changes #1964
Comments
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work has been started. These users each claimed they can complete the work by 1 week, 6 days from now.
Learn more on the Gitcoin Issue Details page. |
This comment has been minimized.
This comment has been minimized.
Hey Zev, yes to documentation if you find it helpful to document what you learn!
I don't believe so, no. But they are the five most major use cases right now. I wonder if instead of trying to migrate away all the global variables, we instead use some of the code that proimps the user to 'unlock' their metamask when there is no web3 enabled, to instead 'enable Gitcoin on their Metamask? This would probably be a much cleaner way to do this. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
opened WIP PR #1992, making progress. will move whining to there. 😆 |
yea i agree this is an issue. seems like it should be fairly trivial to just include web3.js 0.20.3 as a dependancy on gitcoin and set metamask to the provider if it exists. i believe this PR ( #985 ) does this already! |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
1 similar comment
@zevaverbach Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
This comment has been minimized.
This comment has been minimized.
Hi @owocki,
If i understood well in this way the code should be ready also for changing that will be introduce in November, but before that date it is impossible to test the first How would you like the code to be implemented ? Thanks in advance. |
@PumpkingWok great question... i just asked them on medium and on the consensys internaly slack. pasting my message below
|
@PumpkingWok from metamask team:
|
hi @owocki, How would you like to proceed ? while i'm waiting the update i can look again into your code. I have seen |
you can download the new metamask and use that for testing.
i dont know enough about the new architecture of metamask to answer this question. |
Hi, |
Hi @owocki, |
Hi @owocki, |
great! |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Hi @owocki, |
@owocki, it seems like @PumpkingWok is still working on this. Should I
hold off? Also happy to pair on it, @PumpkingWok.
Zev Averbach
Averbach Transcription
(802) 276-5934
avtranscription.com <http://www.avtranscription.com/>
…On Mon, Oct 15, 2018 at 12:53 PM, Kevin Owocki ***@***.***> wrote:
let me snooze gitcoinbot for a bit.. since we've agreed to come back to
this in 10 days time
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1964 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACtRNOtifTD2bKYhJ2zh5P61r0APg3GJks5ulL2kgaJpZM4V0QKx>
.
|
@zevaverbach has a PR out @PumpkingWok FYI - #1992 -- recommend that if you start on this, you collaborate on his branch. i'm happy to pay ya both. @zevaverbach 's current plan is to revisit his PR in a week or two, did i get that correct? |
@thelostone-mc I am not sure on how to add the logo. Will take a look at it. |
@usmanmuhd it looks like that works ! Could you write up a button which does that for now ? Would you be able to wrap that up ? cc @willsputra If you have a design in mind for this -> I'll fix up the css once @usmanmuhd gets the functionality out ^_^ |
@thelostone-mc I am not sure if that is the way to go forward. Going by the comments on MetaMask/metamask-extension#4703, it currently returns false in all cases. They basically want to remove it. Maybe that is one of the reasons it works on your system and not mine. Could you please provide me the build that you are running? |
@thelostone-mc @willsputra |
@pinkiebell just allowing a click on the banner might do right? |
@usmanmuhd |
@pinkiebell @thelostone-mc putting it into one thing though. currently, if I have MetaMask locked and go to the Issue Explorer, it doesn't redirect me to I wonder if we should also put the button into the 'Web 3 locked. Please unlock MetaMask' red bar below. Could also just be a link under 'unlock Metamask'. |
From my discussion with @thelostone-mc offline, adding a banner that says "please allow gitcoin to access metamask" might just do. It should be clickable and will call |
@usmanmuhd I took their latest build @pinkiebell @usmanmuhd A click on the banner seems a lil misleading to me
@willsputra no it does not redirect but TBH we don't need access to web3 on that page as of now. But yeah that error would leaves users confused. Hmm would it be the right choice to trigger the popup on clicking on it too ? Additionally : Would it make sense to keep it in settings also so as the user has a way to enable it without having to visit the pages where |
I guess we should have a new check for the case where we need the user to allow gitcoin to access metamask.
We might just redirect it to the settings/account and have a button there to enable. But to me that seems like an overkill. |
@thelostone-mc hmm regarding the red bar on issue explorer, yea maybe we don't need to do anything if we don't need web3 access on that page (maybe we don't even need the red bar? 😛but that's a whole other discussion for some other time...). @usmanmuhd As @pinkiebell mentioned, I think putting a button on the banner is clearer rather than clicking on the banner itself. Additionally, the verb on the button should be the same as the one that pops up on MetaMask so users are not confused. (They seem to be using the verb 'Connect' MetaMask/metamask-extension#5644 so I used 'Connect' too lol) @pinkiebell @thelostone-mc is this what you all have in mind? |
@willsputra That's how privacy works 😄 |
@pinkiebell @willsputra From what I understand, currently we have an option to know if metamask is locked or we do not have permission, but it is not something that is absolutely necessary. We can just show a banner that says, "Allow access or Unlock wallet to continue" (can be better worded). |
Let's assume the user already approved permission but are now logged out of MetaMask, then we still can show that 'Connect MetaMask' button and if ethereum.enable() resolves with an empty |
@pinkiebell You cannot run |
@usmanmuhd |
Can't we just have another banner if user hasn't enabled metamask ? Or reuse the same banner but show the button only if the user hasn't given permission ? |
@thelostone-mc I will get a poc by today evening. We can discuss and make changes over it. Hope that is fine? |
Hi @usmanmuhd sounds good. Let us know if you have any questions! cc: @thelostone-mc |
@usmanmuhd sure thing! leave a ping when it's good for review ^_^ |
@usmanmuhd hows this going? we are keep to 🚢 since the new metamask is live already .. |
sorry which queries specifically? wahts the just left some QA comments |
i just responded.. im not sure why this was blocked on me, i dont have any special answers you couldnt find yourself. |
@owocki I guess it was specifically for the changes in |
just tested this.. works really good! |
Issue Status: 1. Open 2. Cancelled The funding of 150.0 DAI (plus a crowdfund of 0.1 ETH worth 21.08851715 USD) (150.0 USD @ $1.0/DAI) attached to this issue has been cancelled by the bounty submitter
|
⚡️ A tip worth 150.00000 DAI (150.0 USD @ $1.0/DAI) has been granted to @usmanmuhd for this issue from @owocki. ⚡️ Nice work @usmanmuhd! Your tip has automatically been deposited in the ETH address we have on file.
|
Please read this medium article before reading this desc.
https://medium.com/metamask/https-medium-com-metamask-breaking-change-injecting-web3-7722797916a8
OCTOBER edit: heres a new post from metamask about how to do this: https://medium.com/metamask/eip-1102-preparing-your-dapp-5027b2c9ed76
The scope of this ticket is to update Gitcoin for the above breaking metamask changes.
Please submit a PR with the updates in it; Make sure you've tested
before you submit the PR
The text was updated successfully, but these errors were encountered: