Create users.md #389
Create users.md #389
Conversation
Create an index of current notable users of libp2p. This is just a start and likely has many unintentional omissions. Please add more!
🍻 Co-authored-by: Daniel Norman <1992255+2color@users.noreply.github.com>
Signed-off-by: Dave Grantham <dwg@linuxprogrammer.org>
|
I removed Radicle and added webAI. |
|
I also asked @galargh about the "fleek/build" required check. It comes from the libp2p/github-mgmt config here: https://github.com/libp2p/github-mgmt/blob/f499f712fdfaafa15bdb3a364e2109a907b405ef/github/libp2p.yml#L880-L883 None of the other fleek deployed websites have that setting and I think this is an error considering the other Fleek action. This looks gtg and I'm happy with bypassing the "fleek/build" check since the Fleek test deploy passed. |
Just for clarity, it doesn't come from The check itself though, I suspect it's a historical ID that the fleek team used for the checks they put on the repos. They must have changed since the requirement was created in this repository. I now updated the required check to point at |
|
Thanks for the feedback and edits everyone! I need an approving review to merge. Can someone approve and merge for me (or I can merge)? |
There was a problem hiding this comment.
A good start to documenting some users. Called out a couple I'm not sure are direct users.
A few things I think would be nice to have here are:
- Project links vs just names
- Some consistency around formatting + what's expected here. For example:
- Are we listing companies, projects, implementations, etc.? (Would probably help clarify if how various client implementations built by different companies for Ethereum, Starknet, Celestia, Filecoin, ... are listed)
- Some consistency around what makes sense to call out
- e.g. How transitive are the users here? e.g. does Uniswap make sense even if they don't directly touch the p2p layer but underlying chains like Ethereum do? Might be very reasonable, but will help in fleshing this table out over time.
Don't think they block merging, but some upfront consistency or guidelines would be nice to have since things look a little hodgepodge at the moment.
| | **Avail** | By utilizing libp2p, Avail has created a robust, scalable, and efficient light client network that enhances its data availability guarantees and improves user experience in interacting with the blockchain. | | ||
| | **Prysm (Prysmatic Labs)** | The adoption of libp2p has allowed Prysm to be interoperable with other Ethereum consensus clients, contributing to client diversity in the ecosystem. | | ||
| | **Lighthouse (Sigma Prime)** | The adoption of libp2p aligns with Lighthouse's security-first mindset, allowing for extensive reviews and monitoring of the networking stack. | | ||
| | **Arbitrum** | Arbitrum, which uses libp2p as part of its networking stack, has established itself as the most dominant and adopted L2 chain in the Ethereum rollup ecosystem, commanding approximately 50% of the L2 market share. | |
There was a problem hiding this comment.
IIUC Arbitrum itself doesn't depend on libp2p (although as an Ethereum L2 there's ofc an implicit dependency). Am I mistaken?
|
I merged this PR after editing it a bit, can do follow ups (like addressing these comments #389 (review)) here #391 |
Create an index of current notable users of libp2p. This is just a start and likely has many unintentional omissions. Please add more!