ethereum / ethereum/L2-interop

[Task] Compare efforts

Open
#4 0 comments 0 reactions 1 assignee Claimed by @Joxess View on GitHub
task
Dominant language
No language data
Stars
75
Forks
14
PR merge metrics
No merged PRs in 30d

Description

## Overview
Create one document per category (3 total) that aggregates current interop efforts and compares them both against each other and against the defined [PROPERTIES](https://github.com/ethereum/L2-interop/PROPERTIES.md)

## Objectives
- [x] **Objective 1:** Compare current efforts for Chain-Specific Addresses.
- [ ] **Objective 2:** Compare current efforts for Message Passing.
- [ ] **Objective 3:** Compare current efforts for Intents.
- [ ] **Objective 4:** Evaluate, on each respective document, the efforts against the defined [PROPERTIES](https://github.com/ethereum/L2-interop/PROPERTIES.md).

## Details
- **Background:** We need to understand not only what each team is doing within a category but also how these efforts stack up against our defined PROPERTIES for success.
- **Requirements:**
- Create a markdown document for each category.
- For each document, list the current efforts, compare them against each other, and evaluate how well they meet the PROPERTIES.
- **Acceptance Criteria:**
- All three documents are complete.
- Each document includes clear comparisons between efforts and against the PROPERTIES.
- Documents are verified by the respective teams and merged into the repo.

## Dependencies
- Coordinate with each team lead for accurate data and property definitions.
- Ensure alignment with existing documentation formats.

## Deliverables
- Three markdown documents (one per category) that aggregate and compare current interop efforts against one another and against the PROPERTIES.

## Additional Notes
- Follow our standard documentation format.
- Ensure the documents are clear, concise, and easy to update.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.