MetaMask / MetaMask/metamask-mobile
[Bug]: Stellar vs other NEVM chains - Activities are not logged correctly for Bridge From/To tokens
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
### Describe the bug
**Scenario 1**
Bridge Activity for Stellar chain native asset (XLM) to any other EVM chain native token (like Ethereum chain ETH)
- Event in Activity list and details pages - Only Bridged ETH event is displayed
- Event in Bridged From token details page - **No event logged**
- Event in Bridged To token details page - **No event logged**
**Scenario 2**
Bridge Activity for Stellar chain native asset (XLM) to any other EVM chain ERC20 token (like BNB chain USDC)
Obsevations - Same as Scenario 1
**Scenario 3**
Bridge Activity for other NEVM chain native asset (TRX) to any other EVM chain native token (like Ethereum chain ETH)
- Event in Activity list and details pages - Only Bridged ETH event is displayed
- Event in Bridged From token (TRX) details page - Bridged ETH activity is displayed with same details
- Event in Bridged To token (ETH) details page - **No event logged**
**Scenario 4**
Bridge Activity for other NEVM chain native asset (SOL) to any other EVM chain ERC20 token (like BNB chain USDC)
Obsevations - Same as Scenario 3
**Scenario 5**
Bridge Activity for Stellar chain native asset (XLM) to any other NEVM chain native token (like Solana chain SOL)
- Event in Activity list and details pages - 2 events displayed (Bridged SOL and Received SOL)
- Event in Bridged From (XLM) token details page - **No event logged**
- Event in Bridged To (SOL) token details page - Event is displayed as **Bridged SOL** under Your Activity section **but the details page shows as Received SOL**
**Scenario 6**
Bridge Activity for other NEVM chain native asset (SOL) to another NEVM chain native token (TRX)
- Event in Activity list and details pages - 2 events displayed (Bridged TRX and Received TRX)
- Event in Bridged From (SOL) token details page - Bridged TRX activity is displayed with same details
- Event in Bridged To (TRX) token details page - Event is displayed as **Bridged TRX** under Your Activity section **but the details page shows as Received TRX**
**Scenario 7**
Bridge Activity for Stellar chain native asset (XLM) to any other NEVM chain TRC20 token (like SOL chain USDC)
Obsevations - Same as Scenario 5
**Scenario 8**
Bridge Activity for other NEVM chain native asset (BTC) to another NEVM chain TRC20 token (like SOL chain USDC)
Obsevations - Same as Scenario 6
**Scenario 9**
Bridge Activity for any other NEVM chain native token (like Tron chain TRX) to Stellar chain native asset (XLM)
- Event in Activity list and details pages - 2 events displayed (Bridged USDC and Smart contract interaction)
- Event in Bridged From (SOL) token details page - Bridged XLM event logged
- Event in Bridged To (Stellar-USDC) token details page - **No event logged**
**Scenario 10**
Bridge Activity for any other NEVM chain native token (like SOL chain SOL) to Stellar chain trustline asset (Stellar USDC)
Obsevations - Same as Scenario 9
### Expected behavior
Appropriate activities should be logged.
### Screenshots/Recordings
_No response_
### Steps to reproduce
Perform Bridge operations as described in the different scenarios.
### Error messages or log output
```shell
```
### Where was this bug found?
Internal release testing
### Version
8.9.0
### Build number
4532
### Build type
_No response_
### Device
Pixel 9 Pro XL
### Operating system
Android
### Additional context
_No response_
### Severity
_No response_
Contributor guide
Research direction
Reproduce the ten bridge scenarios on Android using version 8.9.0, build 4532, and compare the activity list, activity details, and bridged-token detail pages. Trace the activity handling and rendering entry points for these pages; done means each bridge direction and asset type shows the appropriate logged event and matching details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- blockchain, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100