Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
Top 15 C P2P Projects
-
lightning
Core Lightning — Lightning Network implementation focusing on spec compliance and performance
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
denarius
Denarius [$D] is a PoW/PoS Hybrid Cryptocurrency with Tribus a new PoW Hashing Algo built specifically for D, one of a kind hybrid masternodes called Fortuna Stakes, atomic swaps, staking, mining, IPFS, optional Native Tor and I2P, and much more!
-
-
-
vulkan-core
A light weight, fast and efficient cryptocurrency blockchain implementation written in C11.
-
netsukuku
Netsukuku aims to be a mesh network or a peer to peer protocol that generates and sustains itself autonomously.
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Project mention: Opening channel from external wallet in Core Lightning | /r/lightningnetwork | 2023-12-04
> but at the very least I think Bluesky could start with generating a private key on each client device, and then using a simple box algorithm to encrypt messages towards the user they want to talk to.
Furry cryptography nerd here.
No. This is inadequate.
> I don't think https://tweetnacl.cr.yp.to/ is hard to mess up.
Yes it is! If you're doing to encrypt some things in a constrained use-case, sure, NaCl is better than hand-rolling it yourself. But it's not sufficient for end-to-end encryption. Here's a few things that TweetNaCl (and other NaCl variants) is, without further protocol design, inadequate to protect against:
1. Invisible Salamanders. NaCl uses xsalsa20poly1305, which is not key-committing.
2. Key Compromise Impersonation. See also, Toxcore, which built atop NaCl: https://github.com/TokTok/c-toxcore/issues/426
3. How do you do group messaging? If you do it as just pairwise, do you use the same public key as your p2p messaging? If so, how do you make sure you don't have a nonce reuse condition between both interactions. Oops.
There is a damn reason end-to-end encryption involves authenticated key exchanges and forward-secure double ratchets.
Project mention: Filecoin Foundation Successfully Deploys IPFS in Space | news.ycombinator.com | 2024-01-16> because, right here right now, that is such a hypothetical situation that I have absolutely no idea why it needs a real-world demonstration of proof of concept using currently-available technology.
So I just want to point out that IPFS was fairly deliberately designed to have numerous, forward-compatible features that could be swapped out in the future : like https://multiformats.io/ and in particular https://multiformats.io/multiaddr/ .
In the IPFS community, there's always been a fairly heated discussion about which bit of the entire system should be stuck with the term IPFS. Like, if you took away the libp2p protocol, and just served CIDs over http, would it be IPFS? What if you took away CAR files (the merkle-tree file format used to define multi-item content)? What if you're a private IPFS network, with no shared nodes with the public network (like https://github.com/TryQuiet/quiet ). What if you didn't use bitswap, the file transfer protocol (Filecoin doesn't use bitswap, and mostly doesn't interconnect with the main public IPFS network). What about if you didn't use a DHT to find providers of a CID. What if you're not using any of the "IPFS" software stack, but your implementation still uses bits and pieces of content-addressability as defined in the standard?
Interestingly, right now, there are a bunch of experiments going in all of these directions: I think it's fair to say that if you wanted to test out content-addressable networks across the solar system, they probably wouldn't be IPFS as it is now, but their nature could probably be described using the primitives the IPFS stack uses, and learning about what needs to change would give a useful direction to some part of the extended IPFS ecosystem.
Project mention: FireChat was a tool for revolution. Then it disappeared | news.ycombinator.com | 2024-04-29They have a GH repository, but it is not clear to me if it contains everything.
https://github.com/clostra/newnode
Project mention: Building a decentralized name system on top of IRC | news.ycombinator.com | 2023-12-25
NOTE:
The open source projects on this list are ordered by number of github stars.
The number of mentions indicates repo mentiontions in the last 12 Months or
since we started tracking (Dec 2020).
C P2P related posts
-
Tox Core is one of the nicest-to-read C codebases
-
Building a decentralized name system on top of IRC
-
uTox – The Lightweight Tox Client
-
Converting my old pc to a backup solution
-
minexmr2.com updated to p2pool v3.1, monerod v0.18.2.0, and ready for Mar 18 p2pool (not monero) hardfork
-
Российские спецслужбы научились следить за пользователями Telegram
-
what are your digital decluttering routines?
-
A note from our sponsor - InfluxDB
www.influxdata.com | 2 Jun 2024
Index
What are some of the best open-source P2P projects in C? This list will help you:
| Project | Stars | |
|---|---|---|
| 1 | lightning | 2,778 |
| 2 | c-toxcore | 2,177 |
| 3 | quiet | 1,877 |
| 4 | toxic | 1,170 |
| 5 | newnode | 445 |
| 6 | KadNode | 405 |
| 7 | libjuice | 378 |
| 8 | tuntox | 343 |
| 9 | denarius | 109 |
| 10 | xmr | 27 |
| 11 | libuvpp | 26 |
| 12 | vulkan-core | 13 |
| 13 | netsukuku | 12 |
| 14 | c-toxcore | 9 |
| 15 | xfsgo | 0 |
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com