You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Decouple CAIP-27 from CAIP-25 and introduce CAIP-217 for Authorization Scopes 217 (also below in RPC WG) status:
One more approval from Hassan to push this forward.
CAIP-25 - the basic design keeps changing, so it's still subject to change. Merging this would update what's on the CAIP page. This keeps the CAIP up to date.
Scope authorizations to be broken into 217, other idea was how to rename the chains array to call them sub-scopes so that if you had identical authorizations for EVM chains, you could define each chain as a sep object.
Next step: Hassan needs to be pinged for review, and should have it done by Sunday.
There are some use-cases people have asked for like having a CAIP URN scheme for addressing block metadata and transaction metadata across chain. ISCC is one of them - it's a way to register hashes on multiple blockchains. In Bitcoin they do it in block header space, ETH space is arbitrary transaction data, etc.
This is just a very basic CAIP on how those properties are named and formalizing it.
Want a strawman for people to improve, relevant reviewers have been tagged.
There was talk of leaving transaction object addressing out of the block explorer CAIP and potentially opening up a new CAIP for it. This is that CAIP.
Chunningham (spruce) to give a quick review on the first version PR in varsig.
Get quick update from Joel on CACAOv3 (any movement on UCAN updates)
Namespaces
(housekeeping)
Backlog / Housekeeping
Need teams per repo with merging rights
Chain Agnostic GitHub team can now merge on namespaces and CAIPs and merge rules will require two approvals.
Trustmark
Devise plan for Trustmark usage - conformance tools, auditing tools, etc. Trustmark can use Git - repo can just be hosted to house a registry of 'CASA Fresh' implementations.
Investigate: publish JSON files as static URL (audited / approved implementations that get updated via CI).
Potential grant: implement a package or crate with a validator for CAIPs (conformance suite) and put yourself in the registry for a sample implementation. (CAIP-10, CAIP-19, CAIP-2 are a good starting points: config file saying which namespaces you want to support and in the library, should consume the spec's regex and say yep or no). (CAIPFORMANCE SUITE), and after we can do a SIWX detection.
Would be a good way to bolster CASA (SIWE folks interested in a badge of honor)
CASA Editorial 6 April
PRs to move to close
chains
array to call them sub-scopes so that if you had identical authorizations for EVM chains, you could define each chain as a sep object.Ongoing projects/topics
WGs
Backlog / Housekeeping
namespaces
andCAIPs
and merge rules will require two approvals.The text was updated successfully, but these errors were encountered: