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

publickey check failed. #203

Open
ghqe opened this issue Oct 27, 2023 · 5 comments
Open

publickey check failed. #203

ghqe opened this issue Oct 27, 2023 · 5 comments

Comments

@ghqe
Copy link

ghqe commented Oct 27, 2023

Issue Description:
I'm facing an issue while trying to log in to AirGap Vault on https://zkbridge.com/pandraking. Every time I attempt to log in, I receive an error message that says "publickey check failed."

Error Message:

publickey check failed.
截屏2023-10-27 16 11 04

Problem Details:

Steps Taken:
I've tried to log in multiple times, but I keep encountering the same error message. I have ensured that I'm using the correct credentials and public key, but the issue persists.

Expected Behavior:
I expect to be able to log in to AirGap Vault without encountering the "publickey check failed" error.

Additional Information:

  • I'm using the URL https://zkbridge.com/pandraking to access AirGap Vault.
  • I have checked my public key and it appears to be correct.
  • I've tried clearing my browser cache and cookies, but the issue remains.
  • I've also attempted to log in from different devices and browsers, but the problem persists.

Note: It's important to provide as much relevant information as possible when reporting a GitHub issue to help the maintainers and contributors understand and address the problem effectively.

@mlaeng
Copy link
Collaborator

mlaeng commented Nov 22, 2023

Currently I can only confirm this happens with my setup as well. After scanning the QR code from the vault with metamask, the error is thrown.

@mlaeng
Copy link
Collaborator

mlaeng commented Nov 22, 2023

@ghqe I checked the Polyhedra discord and there are various users reporting the same issue with all sorts of wallets like rabby + metamask or with ledger. So I assume it's not an AirGap issue, but a zkbridge issue. Did you find a workaround in the meantime?

@suicide
Copy link

suicide commented Jan 5, 2025

I am running into a similar problem on interface.social. If I try to login from a private key in rabby, I can sign the message "successfully". But both workflows should be the same, shouldn't they?

@mlaeng
Copy link
Collaborator

mlaeng commented Jan 6, 2025

@suicide I am unfamiliar with that platform. Can you explain what you tried step by step?

@suicide
Copy link

suicide commented Jan 6, 2025

sure, interface.social is actually an android/ios app that is somewhat a social media platform in that it allows you to follow on chain activity of certain accounts. However, you need to have some onchain reputation like an ens name etc to be able to login.

On android, I opened the app and wanted to login via desktop. which instructs you to go to connect.interface.social on your computer. I connected to the website using rabby and the site wants you to sign a message, which I did using the qr code and airgap. The site returns a bad request with the error message 'invalid signature' (only seen in the dev tools)

2nd attempt was to login directly on the phone using metamask. when hitting login in the interface app, metamasks opens and wants to sign a message. I sign the message using qr and airgap and get redirected to the interface app. Here it just says "something went wrong"

3rd attempt: same as the first using desktop. however, I used the same seed phrase that was stored in rabby itself. Sign the message on desktop, the website accepts the signature and presents an interface specific qr code that I can scan with the android app to login.

Shouldn't signatures always be the same? never dug into this topic before, just an assumption.

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

3 participants