MetaMask / MetaMask/metamask-extension

Add `chain_id_caip` jproperty to segment events

Open
#30,790 1 comment 0 reactions 0 assignees View on GitHub
INVALID-ISSUE-TEMPLATE
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

This issues supersedes https://github.com/MetaMask/MetaMask-planning/issues/1840

New plan is to set `chain_id: null` for chains that don't have a hexidecimal `chain_id` (like bitcoin, solana, etc), and set `chain_id_caip` to their respective CAIP2 chain ids instead.

For ethereum-like chains (chains with a hexidecimal chain_id) we'll need to send both `chain_id` and `chain_id_caip`.

We'll likely need additional information and details, as the issue this issue replaces has a couple of other changes it proposes that need to be confirmed (as its been a while since that issue was updated).

Contributor guide

Open the contributing guide

Research direction

Review the superseded planning issue at https://github.com/MetaMask/MetaMask-planning/issues/1840 and confirm which additional changes still apply. Done means segment events send chain_id_caip for all chains, use null chain_id for non-hexadecimal chain IDs, and send both fields for Ethereum-like chains.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
analytics, blockchain
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.