Skip to content
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

Editorial WG Mtg - 6 Apr #81

Closed
obstropolos opened this issue Apr 6, 2023 · 0 comments
Closed

Editorial WG Mtg - 6 Apr #81

obstropolos opened this issue Apr 6, 2023 · 0 comments

Comments

@obstropolos
Copy link
Contributor

obstropolos commented Apr 6, 2023

CASA Editorial 6 April

PRs to move to close

  • 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.
  • Solana fixes caip10/2 61 status:
    • Merged.

Ongoing projects/topics

  • Chainproofs 218 status:
    • Updates on the to-dos to find out when it'll be ready for more formal review. Items like multidid merged, so next steps is addressing to-dos.
    • Move to draft-PR in order to note additional time before assigning reviewers.
  • Block addressing model 220 status:
    • 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.
  • Transaction object addressing 221 status:
    • 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.
    • Additional strawman, Ligi added for review.
  • Added OpenRPC doc for CAIP-25 212 status:
    • Captured in the RPC minutes - will be bumped to include the new property namess once 217 is merged.
    • This will be merged once 217 is merged (blocker). Will ping Juan and Hassan once ready.
  • Block explorer routes 200 status:
    • Waiting on review from Ligi

WGs

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)
  • Cleaning house
    • Rocco beginning to auto-close
    • Ligi - stalebot status
  • Next Gathering
    • Potentially ETHCC (July), Potentially Devconnect (TBD)
@obstropolos obstropolos changed the title Editorial w - 6 Apr Editorial WG Mtg - 6 Apr Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant