Skip to content

Commit

Permalink
Merge pull request #301 from ChainAgnostic/caip-25/remove-sessionProp…
Browse files Browse the repository at this point in the history
…erties-add-scopedProperties

[Caip 25] add scopedProperties; update examples to include `eip155:0`, `scopedProperties`, and `sessionProperties`
  • Loading branch information
bumblefudge authored Jul 15, 2024
2 parents c3fa100 + d66c6bc commit 31e0de4
Show file tree
Hide file tree
Showing 2 changed files with 130 additions and 148 deletions.
14 changes: 4 additions & 10 deletions CAIPs/caip-217.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,16 +64,10 @@ The syntax of a `scopeObject` is as follows:
Where:

- {`scopeString`} (conditional) = EITHER a namespace identifier string registered in the CASA [namespaces][] registry to authorize multiple chains with identical properties OR a single, valid [CAIP-2][] identifier, i.e., a specific `chain_id` within a namespace.
- `scopes` (conditional) = An array of 0 or more [CAIP-2][] `chainId`s. For each
entry in `scopes`, all the other properties of the `scopeObject` apply, but in
some cases, such as when members of `accounts` are specific to 1 or more
chains in `scopes`, they may be ignored or filtered where inapplicable;
namespace-specific rules for organizing or interpreting properties in
multi-scope MAY be specified in a [namespace-specific profile][namespaces] of
this specification.
- This property MUST NOT be present if the object is already scoped to a single `chainId` in the string value above.
- This property MUST NOT be present if the scope is an entire [namespace][namespaces] in which `chainId`s are not defined.
- This property MAY be present if the scope is an entire [namespace][namespaces] in which `chainId`s are defined.
- `scopes` (conditional), formerly `chains` = An array of 0 or more [CAIP-2][] `chainId`s. For each entry in `scopes`, all the other properties of the `scopeObject` apply, but in some cases, such as when members of `accounts` are specific to 1 or more chains in `scopes`, they may be ignored or filtered where inapplicable; namespace-specific rules for organizing or interpreting properties in multi-scope MAY be specified in a [namespace-specific profile][namespaces] of this specification.
- This property MUST NOT be present if the object is already scoped to a single `chainId` by the `scopeString` value above.
- This property MUST NOT be present if the scope is an entire [namespace][namespaces] in which no `chainId`s are defined or no [CAIP-2] profile has been published.
- This property SHOULD be present if the scope is an entire [namespace][namespaces] in which `chainId`s are defined. An empty `scopes` array MUST NOT be interpreted as authorizing an entire namespace in which a finite list of [CAIP-2] value could be set, but rather, as applying equal to zero members of that finite list until 1 or more of them are added to `scopes`.
- `methods` = An array of 0 or more JSON-RPC methods that an application can call on the agent and/or an agent can call on an application.
- `notifications` = An array of 0 or more JSON-RPC notifications that an application send to or expect from the agent.
- `accounts` (optional) = An array of 0 or more [CAIP-10][] identifiers, each valid within the scope of authorization.
Expand Down
Loading

0 comments on commit 31e0de4

Please sign in to comment.