fix: adds a unique id to RPC events for extension

[andreahaku]

Explanation

Fixes the unique id (5a374dcd2e5eb762b527af3a5bab6072a4d24493 - SHA1 of sdk string) for all analytics events coming from extension. It adds a UUID that is stored in the localStorage with a key that is the base64 of the url and name coming from the dapp metadata.

It also includes #1000 setting the from to mobile for RPC calls events when a dapp is opened in the MM mobile in-app browser.

Testing

• Check that when using MM Extension on a dapp using the MM SDK, a unique id (uuid) is sent when tracking RPC calls and that this id is not 5a374dcd2e5eb762b527af3a5bab6072a4d24493
• Check that when opening a dapp using the MM SDK, in the MM mobile in-app browser, when tracking RPC calls events, the from is set to mobile and not extension

References

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've highlighted breaking changes using the "BREAKING" category above as appropriate

[BjornGunnarsson]

I don't think we can use this approach.
After thinking it through, sending the address ( even hashed ) to then store and use in our analytics is not something we can do as pertains to Privacy.
There has been a lot of work related to MetaMetricsID, that down the line we can use, but as a short term solution we should just generate a random ID.

So if we can generate and store a randomID on the client browser to use for the sdk_analytics.

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@types/uuid@10.0.0	None	0	7.82 kB	types

View full report↗︎

[codecov]

Codecov Report

Attention: Patch coverage is 94.11765% with 2 lines in your changes missing coverage. Please review.

Project coverage is 80.69%. Comparing base (ec20994) to head (9b4dd06).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...rc/provider/extensionProviderHelpers/handleUuid.ts	93.33%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #996      +/-   ##
==========================================
+ Coverage   80.57%   80.69%   +0.11%     
==========================================
  Files         177      178       +1     
  Lines        4001     4035      +34     
  Branches      993     1001       +8     
==========================================
+ Hits         3224     3256      +32     
- Misses        777      779       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[abretonc7s]

LGTM

[BjornGunnarsson]

LGTM 🚀

[christopherferreira9]

Analytics being sent to socket server with unique UUID for extension connection different than 5a374dcd2e5eb762b527af3a5bab6072a4d24493:

localStorage storing the key above:

Base64 decoding of the key stored in localStorage that referes to the UUID above:

[christopherferreira9]

Inapp browser showing from as mobile.

[BjornGunnarsson]

The functionality of how we distinguish what the "from" value is critical.
I do not see any reason for us to re-implement that if we already have a method exposed by the SDK that can get the connected "from" in a more detailed manner.

[andreahaku]

The functionality of how we distinguish what the "from" value is critical. I do not see any reason for us to re-implement that if we already have a method exposed by the SDK that can get the connected "from" in a more detailed manner.

When on a desktop browser, the user connects with the MM mobile app via QRCode, the from is correctly set to mobile:

Video:
https://github.com/user-attachments/assets/ff97c582-f157-44c4-a725-f431153efeea

[BjornGunnarsson]

@omridan159 could you take a look over the code here, and approve if everything is good.
Then we can get this into the next release of the SDK

[abretonc7s]

approved to get into release but might need to adjust logic to simplify later.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud