mirror of
https://github.com/Cuprate/cuprate.git
synced 2024-12-22 19:49:28 +00:00
Cuprate, an upcoming experimental, modern & secure monero node. Written in Rust
https://cuprate.org
cryptocurrencymoneromonero-integrationsmonerodnetworknetwork-programmingpeer-to-peerrustrust-langsecurity
Boog900
b510739701
* p2p changes * clippy * a few more docs * init cuprate-p2p * remove some unrelated code and add some docs * start documenting client_pool.rs * add more docs * typo * fix docs * use JoinSet in connection maintainer * small changes * add peer sync state svc * add broadcast svc * add more docs * add some tests * add a test * fix merge * add another test * unify PeerDisconnectFut and add more docs * start network init * add an inbound connection server * remove crate doc for now * fix address book docs * fix leak in client pool * correct comment * fix merge + add some docs * fix doc * dandelion_tower -> dandelion-tower * fix async-buffer builds * check if incoming peers are banned * add interface methods * update docs * use a JoinSet for background network tasks * Apply suggestions from code review Co-authored-by: hinto-janai <hinto.janai@protonmail.com> * Update p2p/monero-p2p/src/services.rs Co-authored-by: hinto-janai <hinto.janai@protonmail.com> --------- Co-authored-by: hinto-janai <hinto.janai@protonmail.com> |
||
|---|---|---|
| .github | ||
| benches | ||
| binaries | ||
| books | ||
| consensus | ||
| cryptonight | ||
| helper | ||
| misc | ||
| net | ||
| p2p | ||
| pruning | ||
| rpc | ||
| storage | ||
| test-utils | ||
| types | ||
| zmq | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CONTRIBUTING.md | ||
| deny.toml | ||
| LICENSE | ||
| LICENSE-AGPL | ||
| LICENSE-MIT | ||
| README.md | ||
| SECURITY.md | ||
| typos.toml | ||
An up and coming Rust Monero node.
Cuprate will be an alternative Monero node written from the ground up in Rust. It will be able to independently validate Monero consensus rules providing a layer of security and redundancy for the Monero network.
Cuprate will help to protect the network from implementation bugs that could cause a variety of issues, plus because it's written in a memory safe language Cuprate will be less likely to suffer from memory safety issues compared to monerod.