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.
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. Expected to participate in working groups. |
| Working Groups | Collections of members tackling specific areas of interest. |
CAIPs/ codeowners |
Subset of authors of accepted CAIPs committed to ongoing review and maintainance of CAIPs |
| Maintainers | Members running CASA meetings (excluding working group) and ensuring overall process integrity. |
All CASA stakeholders are invited to join a meeting every four weeks, for the purpose of:
- Evaluating CAIPs, registries, and related publications
- Sharing progress in individual working groups
- Proposing the creation of new working groups
Since CASA meetings are primarily intended to sharing the working groups progress, at least one member from each active working group is expected to attend, or entire working groups if the WG has topics agenda'd for a given meeting.
- 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).
CASA members self-organize into topic-specific working groups. Individual working groups set their own meeting schedule and communicate in designated communication channels. We expect working groups to meet frequently enough to share their progress at CASA meetings.
The CASA meetings note template may help keep stakeholders aligned.
| Working Group | Status | Description | Repository | CAIP |
|---|---|---|---|---|
CAIPs discussion |
Active | TBC | TBC | All |
Chain Id |
Active | TBC | TBC | CAIP-2 |
Account Id |
Active | TBC | TBC | CAIP-10 |
Asset Id |
Active | TBC | TBC | CAIP-19 |
Json RPC |
Active | TBC | TBC | CAIP-24, CAIP-25 |
Asset Registry |
Active | TBC | TBC | CAIP-19 |
- 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) | 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 |
CASA will begin meetings in 2021 as we wait for the initial working groups to form.
- 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 and send you a welcome email containing your invitations to the CASA Call Calendar and Discord.