-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
feat: OS to Reservoir migration #9547
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
|
|
Hey @sahar-fehri this PR looks good to me, but can we have a recording with the nft auto detect and custom import to have a history of how it was the functionality now? It's good as well to record playing around with the IPFS Gateway Enabled and Display Nft Media privacy toggles to make sure the privacy features |
Thanks @tommasini 🙏 i added videos to the description! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Description
This PR adds patches to mobile to enable Open Sea (OS) migration.
Related issues
MMASSETS-156. (Restricted access Jira issue)
Main core PR: MetaMask/core#4030
Core Compare link used to create the assets patch: https://github.com/MetaMask/core/compare/patch/mobile-assets-controllers-v-18-0-0...patch/mobile-assets-controllers-v-18-0-0-os-migration-v2?expand=1
Context
Problem: We want to roll out Reservoir to Extension and Mobile similar to how we have done in Portfolio.
Requirements:
Define a way to compare OpenSea’s spam filtering and Reservoir’s spam filtering. Ideally the spam filtering is similar.
Create Core PR to migrate calls from OS to Reservoir.
Create PR on mobile to migrate from OS to Reservoir.
Create Extension PR to migrate from OS to Reservoir
Define roll out plan for Extension and Mobile
Roll out Reservoir to Extension and Mobile
Today, to get the NFTs core is calling opensea V2 api to fetch user nfts and to add new nfts (get NFT metadata)
In this ticket we wanted to call Reservoir API instead of calling openseaV2.
We are not changing any of the functional behaviors of the app, we are just swapping third party providers.
So the app should behave the exact same regarding any NFT related functionality:
Like showing NFT details when clicking on the NFT
And being able to remove/add the NFT
Mark it as favorite
Sending NFts
Manual testing steps
Screenshots/Recordings
The NFT tab should behave the same. You should be able to see the same NFTs you had.
Only thing noticed while testing is for some collections you might see either a different image or the mobile default image (if the new third party provider was not able to return the image)
Before
Screen.Recording.2024-05-08.at.00.15.48.mov
Screen.Recording.2024-05-08.at.01.38.49.mov
After
Screen.Recording.2024-05-07.at.23.44.39.mov
Screen.Recording.2024-05-08.at.00.08.08.mov
Pre-merge author checklist
Pre-merge reviewer checklist