The Chain Agnostic Standards Alliance (CASA) is a collection of working groups dedicated blockchain protocol-agnostic standards. CASA also publishes Chain Agnostic Improvement Proposals which describe standards created by the different working groups.
- Purpose
- Organizational Structure
- Regular Meetings
- Working Groups
- Explicit and Implicit Agendas
- Discord Server
- Members
- Join CASA
CASA is a self-organized and autonomous alliance of crypto-blockchain developers and enthusiasts. Its aim to create standards which support interoperability and facilitate communication between blockchain protocols, software and companies.
CASA organizes working groups where proposals are debated, drafted and submitted as CAIPs for the purpose implementation and community adoption.
CASA participants are structured into three groups:
| Role | Description |
|---|---|
| Members | All participants who contribute in any form, including github review. Expected to participate in one or more topical working groups. |
| Working Groups | Topical clusters of CAIPs and namespaces. These change over time according to activity |
| Editoral board/"Codeowners" | A subset of membership including the authors of accepted CAIPs committed to ongoing review and maintainance of the CAIPs and namespaces |
All CASA stakeholders are invited to join our regular editorial meetings every four weeks, as well as regular meetings of the more focused topical working groups, which meet every 2 or every 4 weeks depending on the consensus of the group. These take place on jitsi, and a calendar can be found here (also here for Google Calendar users). Where possible, high-level minutes are taken, and entered into the notes as closed issues on this repo.
We also have periodic in-person meetings, to onboard new participants and, where possible, to advance working group progress. For information on these, see the Gatherings repository.
- Explicit agenda items, if any have been set by issues in the
meetings/repo (e.g., instance, a working group requests the whole community's input on a decision). - Implicit agenda: PRs in the
CAIPs/repo that have been marked as "next meeting" or "merge soon" by theCAIPs/codeowners and/or Maintainers. - Implicit agenda: Issues in the
CAIPs/repo that have been marked as "next meeting", as time allows. - Housekeeping, agenda requests for the following meeting, and open discussion.
Note: the purpose of the next meeting tag is to allow codeowners to prioritize or stack-rank additions. Codeowners and the broader membership alike are requested to use them to prioritize them in their review process to allow swift review. Approval by any 2 codeowners is enough to merge at a future meeting. In cases where a timely merge is desired, codeowners may also chose to apply a merge soon tag, which is a way of requesting more review for an approved PR (and avoid a valid PR sitting unmerged across multiple meetings for lack of discussion).
For those who prefer realtime/social-style communications, we also run a Discord server, which is secondary and non-archival-- it can be found using this Discord invite link (note: this link has a spam/crawler deterrent that requires manual removal).
| Working Group | Status | Description |
|---|---|---|
CAIPs discussion |
Standing | CAIPs are always being iterated and refined and introduced! |
Json RPC |
Active | Feature discovery and "session" model for dApps and wallets |
Browser Security |
Active | Working within the Browser protocols and data models |
CACAOs & AuthZ |
Active | Authorization models and token/receipt formats for Web3 |
Chain Id |
Inactive | TBC |
Account Id |
Inactive | TBC |
Asset Id |
Inactive | TBC |
Asset Registry |
Inactive | TBC |
- Join CASA.
- Create a description that explains the goal of your working group and related CAIP(s).
- Submit a Pull Request to the CASA repository adding your working group.
- Propose your working group at the next CASA meeting. If approved, your PR will be merged, and your working group meeting schedule will be added to the CASA calendar.
- Recruit participants for your working group.
Below, please find a list of all members and their organizations.
| Organizations | Members | Status | Working groups |
|---|---|---|---|
| ChainAgnostic | Ligi (@ligi), Pedro Gomes (@pedrouid), Antoine Herzog (@antoineherzog), Amadeo Pellicce (@pellicceama) | Maintainer | All Working groups |
| Epicenter | Sebastien Couture (@seb2point0) | Member | CAIPs discussion |
| Tally | Tarrence (@tarrencev) | Maintainer (go-caip) | All Working groups |
| Ceramic | Joel Thorstensson (@oed), Sergey Ukustov (@ukstv) | Member | All Working groups |
| Spruce | Wayne Chang (@wyc), Gregory Rocco (@obstropolos), Oliver Terbu (@awoie) | Member | CAIPs discussion |
| Learning Proof UG | Juan Caballero (@bumblefudge) | Maintainer | CAIPs |
| Block | Gabe Cohen (@decentralgabe), Daniel Buchner (@csuwildcat), Moe Jangda (@mistermoe) | Member | All Working groups |
| SKALE Network | Chadwick Strange (@cstrangedk) | Member | All Working Groups |
| Metagov | Joshua Tan (@thelastjosh) | Member | All Working Groups |
| kycDAO | Balázs Némethi (@nembal) | Member | All Working Groups |
| cheqd | Ross Power (@rosspower11) | Member | All Working Groups |
| Fission | Boris Mann (@bmann), Brooklyn Zelenka (@expede), Ryan Betts (@depatchedmode), Andy Vivash (@avivash) | Member | All Working Groups |
| Danube Tech | Markus Sabadello (@peacekeeper) | Member | All Working Groups |
| Obvious | Jebu Ittiachen (@jebu) | Member | All Working Groups |
| Dynamic | Itai Turbahn (@turbahn), Paolo Lim (@paololim) | Member | All Working Groups |
| Notabene | Andrés Junge (@ajunge) | Member | All Working Groups |
| Ledger | Rod Carraresi (@carraresi) | Member | All Working Groups |
| ITSA | Valentin Seehausen (@valleXYZ) | Member | All Working Groups |
| Protocol Labs | Eva Shon (@eshon) | Member | All Working Groups |
| Fireblocks | Oren Yomtov (@orenyomtov), Arik Galansky (@arikg) | Member | All Working Groups |
| MetaMask | Erik Marks (@rekmarks), Olaf Tomalka (@ritave) | Member | All Working Groups |
| Shovel Company | Prashant Mittal (@prashant3863) | Member | All Working Groups |
Submit a Pull Request to this repository adding yourself as a member in the table above.
Once a maintainer has confirmed you have completed this step, they will merge your PR. We recommend checking that your Github email is up-to-date and you are "Watching" these repos:
- Gatherings to stay up to date with in person gatherings
- CASA to stay up to date with the organisation and scheduled calls
- CAIPs
- namespaces