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

Upgrade to latest @stacks/wallet-sdk #2283

Closed
kyranjamie opened this issue Mar 3, 2022 · 15 comments
Closed

Upgrade to latest @stacks/wallet-sdk #2283

kyranjamie opened this issue Mar 3, 2022 · 15 comments
Assignees
Labels

Comments

@kyranjamie
Copy link
Collaborator

We need to upgrade the wallet-sdk to the version including @friedger's PR hirosystems/stacks.js#1204

This will fix profile signing for new users

cc/ @markmhx @pradel

@pradel
Copy link
Contributor

pradel commented Mar 3, 2022

To add to the context, I saw that a commit with 3.4.0 release was created but I couldn't find the tag on npm so maybe something went wrong during the release process.

@fbwoolf
Copy link
Contributor

fbwoolf commented Mar 3, 2022

Will need to address this when we do the update: #2282

@markmhendrickson
Copy link
Collaborator

@kyranjamie @pradel Can one of you spell out the exact problem that will or does occur already without this upgrade, so that we capture clearly here the specific UX benefit to this upgrade?

@markmhendrickson markmhendrickson modified the milestones: Resolve legacy BNS support, Improve username support Mar 4, 2022
@pradel
Copy link
Contributor

pradel commented Mar 4, 2022

This fix is for signing the profile.json with the right key, no UX changes are required.

@markmhendrickson
Copy link
Collaborator

markmhendrickson commented Mar 4, 2022

I mean to ask, what UX problems will occur if we don't make this upgrade (aside from us needing to make any UX changes per se, since I agree those aren't required)?

In other words, what will go wrong exactly (e.g. with Sigle usage) if we don't upgrade how the profile.json is signed? I presume something akin to what we outlined here in Notion, but would like to capture here on GitHub as well.

@pradel
Copy link
Contributor

pradel commented Mar 4, 2022

From the notion, the part not working is:

  • Accounts displayed all the same as before
  • Others attempting to view sigle.io/mary.id.blockstack/mypost can view her blog post
  • Others attempting to view sigle.io/mary1.btc/mypost cannot view her blog post

The profile.json is signed with the wrong key, so when we fetch the profile we can't verify that mary1.btc did sign it properly.

@beguene beguene self-assigned this Mar 16, 2022
@beguene beguene moved this to Development in Hiro Wallet (DEPRECATED) Mar 16, 2022
beguene pushed a commit that referenced this issue Mar 16, 2022
Add webpack aliases to esm instead of polyfill
closes #2283
closes #2282
beguene pushed a commit that referenced this issue Mar 18, 2022
Add webpack aliases to esm instead of polyfill
closes #2283
closes #2282
@markmhendrickson markmhendrickson moved this from Development to Review in Hiro Wallet (DEPRECATED) Mar 21, 2022
kyranjamie pushed a commit that referenced this issue Mar 22, 2022
Add webpack aliases to esm instead of polyfill
closes #2283
closes #2282
kyranjamie pushed a commit that referenced this issue Mar 22, 2022
Add webpack aliases to esm instead of polyfill
closes #2283
closes #2282
kyranjamie pushed a commit that referenced this issue Mar 22, 2022
Add webpack aliases to esm instead of polyfill
closes #2283
closes #2282
kyranjamie pushed a commit that referenced this issue Mar 25, 2022
Add webpack aliases to esm instead of polyfill
closes #2283
closes #2282
@beguene beguene moved this from Review to QA in Hiro Wallet (DEPRECATED) Mar 28, 2022
beguene pushed a commit that referenced this issue Mar 28, 2022
Add webpack aliases to esm instead of polyfill
closes #2283
closes #2282
@timstackblock
Copy link
Contributor

timstackblock commented Mar 31, 2022

.btc names still do not work with the latest version of the app https://sigle-git-feature-stacks-wallet-extension-sigle.vercel.app/

Ran a test with a regular ID it works fine.
Then ran a test with my .btc username and it wont allow you into the app

VIDEO of the issue
https://somup.com/c3evqbOVTC

cc @Eshwari007 @markmhx

@andresgalante
Copy link
Contributor

@Eshwari007 can you please test this issue with a .btc name?

@Eshwari007
Copy link

Eshwari007 commented Apr 5, 2022

Test findings

Tested the PR on https://sigle-git-feature-stacks-wallet-extension-sigle.vercel.app/login
Test failed, I was not able to login and notice errors in console log
Attaching the screenshots for perusal

Screen Shot 2022-04-05 at 4 41 03 PM

Screen Shot 2022-04-05 at 4 41 44 PM

cc @andresgalante @markmhx @pradel

@andresgalante
Copy link
Contributor

Thanks @Eshwari007 🙇 @pradel @beguene what are the next steps?

@beguene
Copy link
Contributor

beguene commented Apr 7, 2022

@andresgalante Not sure about the next steps. In this PR I fixed the unit tests errors but I did not touch the profile signing issue maybe @pradel Can give more details.

@pradel
Copy link
Contributor

pradel commented Apr 7, 2022

@beguene @andresgalante @Eshwari007 I will have to look next week what's going on.

But looks like I can't login anymore using an account with a .btc domain with the latest 3.7.0 version. I tried on Arkadiko, Alex and Frens. So the issue you faced might not be related to the changes?

Screenshot 2022-04-07 at 15 41 35

@pradel
Copy link
Contributor

pradel commented Apr 7, 2022

Created a separate issue #2354

@markmhendrickson
Copy link
Collaborator

markmhendrickson commented Apr 18, 2022

I believe we need to upgrade Stacks.js for the test app to include the changes made with hirosystems/stacks.js#1230 then retest the related PR.

@janniks can confirm if that's indeed the case here given the case encountered above during testing before.

@andresgalante andresgalante moved this from Development to QA in Hiro Wallet (DEPRECATED) Apr 18, 2022
@andresgalante
Copy link
Contributor

Waiting for the test app to update stackjs to be QAed

@andresgalante andresgalante moved this from QA to Ready to merge in Hiro Wallet (DEPRECATED) Apr 25, 2022
@andresgalante andresgalante moved this from Ready to merge to Closed in Hiro Wallet (DEPRECATED) May 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment