https://github.com/l2beat/l2beat

L2BEAT is an analytics and research website about Ethereum layer two (L2) scaling solutions.
https://github.com/l2beat/l2beat

ethereum layer-2 research

Last synced: 6 days ago
JSON representation

L2BEAT is an analytics and research website about Ethereum layer two (L2) scaling solutions.

• Host: GitHub
• URL: https://github.com/l2beat/l2beat
• Owner: l2beat
• License: mit
• Created: 2021-03-24T14:18:55.000Z (almost 4 years ago)
• Default Branch: main
• Last Pushed: 2024-12-30T12:24:07.000Z (10 days ago)
• Last Synced: 2025-01-01T09:51:15.684Z (8 days ago)
• Topics: ethereum, layer-2, research
• Language: Solidity
• Homepage: https://l2beat.com
• Size: 227 MB
• Stars: 528
• Watchers: 15
• Forks: 450
• Open Issues: 44
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# L2BEAT 💓

L2BEAT (Layer 2 Beat) is a website dedicated to providing research and statistics about the very exciting layer 2 technology on Ethereum.

You can visit the site yourself at https://www.l2beat.com/.

## Contributing

We welcome and encourage contributions. To learn about the project structure and contributions please read [`CONTRIBUTING.md`](https://github.com/l2beat/l2beat/blob/main/CONTRIBUTING.md).

🔍 Here is also a visual step-by-step guide for creating a Pull Request - [link](https://www.notion.so/l2beat/How-to-add-milestones-0e8684a83c3c48ce8bc7b605d9c9a1bf)

## License

We believe in knowledge sharing and open access. Our code is and will remain open source with the permissive MIT license.

## Versioning and publishing (tooling)

Some of the sub-packages are published to NPM. We use a tool called [changesets](https://github.com/changesets/changesets) to manage versioning, cross-dependency versioning and publishing new versions to NPM.  When you make a change, before merging to master:

- run `pnpm changeset` and mark the packages you wish to publish, select what kind of a change it is (major,minor,patch) and provide the summary of the changes

When you want to publish all previous changes to NPM:

- now run `pnpm changeset version`, this will change the generated `.changeset/file.md` into an entry into `CHANGELOG.md` and `package.json` in changed packages

After your PR with changed `CHANGELOG.md` and `package.json` is merged into `main`, a CI step will run which will try to publish all change changes.