-
Notifications
You must be signed in to change notification settings - Fork 177
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
CAIP-341 - Extension ID Target Type Specification #341
base: main
Are you sure you want to change the base?
CAIP-341 - Extension ID Target Type Specification #341
Conversation
CAIPs/caip-341.md
Outdated
--- | ||
caip: 341 | ||
title: Extension ID Target Type Specification | ||
author: [Joao Tavares] (@ffmcgee725) |
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.
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.
resolved in 916e37e
I think this closes #294 ? |
Example of establishing a connection and sending a message: | ||
|
||
```ts | ||
const port = chrome.runtime.connect(walletData.target.value); |
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.
really like this pattern here... but realistically it's an array so you need an index
but more importantly than correcting this typo.... I think it raises the question of how valuable is it for target
to be an array
icon: string; | ||
rdns: string; | ||
// Optional properties | ||
target?: { type: "caip341", value: any }[], |
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.
target?: { type: "caip341", value: any }[], | |
target?: { type: string, value: any }[], |
Defining extension id as a valid target type for wallet data.