rust-libp2p
consensus-specs

rust-libp2p | consensus-specs | |
---|---|---|
34 | 158 | |
4,802 | 3,641 | |
2.3% | 0.9% | |
9.6 | 9.9 | |
3 days ago | 3 days ago | |
Rust | Python | |
MIT License | Creative Commons Zero v1.0 Universal |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rust-libp2p
- How Nat Traversal Works
- Peer to Peer Network Stack
-
You can help Anna's Archive by seeding torrents
* (i.e. WebRTC: https://github.com/libp2p/rust-libp2p/tree/master/examples/browser-webrtc)
-
On Implementation of Distributed Protocols
Substrate and Lighthouse use libp2p as a networking stack for communication between nodes. The libp2p framework is a versatile modular peer-to-peer networking stack. It provides a collections of abstractions, mechanisms, and protocols for facilitating communication in P2P systems. In particular, libp2p supports multiple transport mechanisms (TCP, QUIC, WebSocket, WebTransport, etc.), encryption schemes (TLS and Noise), and stream multiplexing. Higher-level protocols in libp2p are implemented on top of reliable, ordered, bidirectional binary streams, which are transparently encrypted and multiplexed by the framework.
-
Bifrost: A peer-to-peer communications engine with pluggable transports
It's a peer-to-peer "engine" with switchable components. Seems to run on different platforms (browsers, mobile, desktop, server).
At a glance, it looks pretty much like libp2p (https://libp2p.io/) but seems to integrate with libp2p as well (meaning you should be able to use Bifrost on one end, and libp2p on the other), so I'm guessing there is at least some fundamental difference, but I cannot spot it. Seems to use slightly different terminology compared to libp2p.
- Libp2p – A Modular Network Stack
- [AskJS] Any js browser based p2p libraries?
-
Decentralized Databases: ComposeDB
ComposeDB is a graph database created by 3BoxLabs, a company well-known in the Web3 ecosystem for their work on decentralized identifiers (DIDs) and their main product the Ceramic network. Ceramic is a network of nodes that store and share composable data streams on top of libp2p, the network stack that also powers IPFS.
-
What about a Zig implementation of lib2p2?
Yes, there is already a Rust version (https://github.com/libp2p/rust-libp2p) that behaves well at this level but I think we can reach a higher level of performance on this point with Zig. Also, if you look at the long term roadmap of libp2p (https://github.com/libp2p/specs/blob/master/ROADMAP.md), the mobile devices and IoT integrations for example are part of the considerations.
-
A Rust client library for interacting with Microsoft Airsim https://github.com/Sollimann/airsim-client
libp2p
consensus-specs
- Daily General Discussion - June 23, 2023
-
Daily General Discussion - May 20, 2023
I think its 1 million: https://github.com/ethereum/consensus-specs/issues/2137
-
Ethereum's pending withdrawals total $1.34 billion after Shapella
how "radically decentralized" the development of the Ethereum core is. In the past half a decade only 133 devs have contributed to Ethereum source code. 2 devs have written 25% of the code. The first 10 developers have written 70% of the Ethereum code. Consensus specifications the ones that all the clients implement. Half are Consensys employees https://github.com/ethereum/consensus-specs
-
Daily General Discussion - February 18, 2023
I think this will be defined here: https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/fork-choice.md
- Daily General Discussion - February 17, 2023
-
There are over 7000 pending validators on the Ethereum test net. Looks like a lot of people want to practice staking before the Shanghai hardfork
Clients dependent on Consensys core and ETH management repo. A client is just the implementation directed by Consensys written in a different language. Fact is about 10 developers are the only reason those clients will update with staking. https://github.com/ethereum/consensus-specs
-
Set your Ethereum validator withdrawal address with CLWP today
Exits are processed at 7 per epoch (currently). There is no queue for withdrawals. See https://github.com/ethereum/consensus-specs/pull/3068
-
Evolution of the Ethereum Proof-of-Stake Consensus Protocol
https://github.com/ethereum/consensus-specs/blob/dev/specs/p...
-
How to merge an Ethereum network right from the genesis block
For that, we have to take the vanilla deposit contract from the consensus specs: deposit_contract.sol, get the Solidity compiler version 0.6.11, compile the binary of the runtime part, and create an empty deposit tree.
-
Centralization of ETH developer community?
The PoS consensus specification
What are some alternatives?
cosmos-sdk - :chains: A Framework for Building High Value Public Blockchains :sparkles:
ethereum-org-website - Ethereum.org is a primary online resource for the Ethereum community.
automerge-rs - Rust implementation of automerge [Moved to: https://github.com/automerge/automerge]
l2beat - L2BEAT is an analytics and research website about Ethereum layer two (L2) scaling solutions.
y-crdt - Rust port of Yjs
core - Lido DAO smart contracts
freenet-core - Declare your digital independence
annotated-spec - Vitalik's annotated eth2 spec. Not intended to be "the" annotated spec; other documents like Ben Edgington's https://benjaminion.xyz/eth2-annotated-spec/ also exist. This one is intended to focus more on design rationale.
ChainBridge - 🌉 Modular Multi-Directional Blockchain Bridge to interact with Multiple Networks; Ethereum, Ethereum Classic, Substrate, based chains. Stay tuned for ChainBridge Hub!
prysm - Go implementation of Ethereum proof of stake
go-livepeer - Official Go implementation of the Livepeer protocol
ergo - Ergo protocol description & reference client implementation
