Cuprate/cuprate
Cuprate/cuprate
1
0
Fork 0
mirror of https://github.com/Cuprate/cuprate.git synced 2024-12-23 03:59:31 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

forgot Cargo.toml

Browse source
This commit is contained in:
Someone Else 2023-02-08 13:54:55 +01:00
parent 259bb9bd2b
commit 1701d724dc
2 changed files with 26 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
Cargo.toml
View file

@ -1,11 +1,31 @@
[package] [package]
name = "cuprate" name = "cuprate"
version = "0.1.0" version = "0.0.1"
edition = "2021" edition = "2021"
rust-version = "1.67.0"
description = "An upcoming experimental, modern & secure monero node"
readme = "readme.md"
repository = "https://github.com/SyntheticBird45/cuprate"
license = "BSD-3-Clause"
license-file = "LICENSE"
# All Contributors on github
authors=["SyntheticBird45"]
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[dependencies] [dependencies]
monero = {version = "*", features = ['serde']} monero = {version = "*", features = ['serde']}
serde = "*" serde = "*"
heed = "0.20.0-alpha.0"
# As suggested by /u/danda :
thiserror = "*"
[profile.release]
opt-level = 3
debug = 0
strip = "symbols"
lto = "thin"
panic = "abort"
build.rustflags=["-Zcf-protection=full", "-Zsanitizer=cfi", "-Crelocation-model=pie", "-Cstack-protector=all"]

8
readme.md
View file

@ -30,18 +30,18 @@ I'm working on rewriting the blockchain_db part atm.
### Contributions ### Contributions
Any help on rewriting other parts of the node while also proposing improvements and respecting the goal of the project (which means try to be async and no weird api, or at least talk about it) is appreciated. Any help on rewriting other parts of the node while also aligning with the targeted improvements is appreciated.
I encourage anyone to review the work being done, discuss about it or propose agressive optimizations (at architectural level if needed, or even micro-optimizations in 'monolithic components'). I encourage anyone to review the work being done, discuss about it or propose agressive optimizations (at architectural level if needed, or even micro-optimizations in 'monolithic components').
For non-developers people, it is time for you to unleash your ideas.
### Code & Repo ### Code & Repo
For the moment i try to organize the repo like the official one. For the moment I try to organize the repository like the official one. But it won't last for long.
### Improvements & Features ### Improvements & Features
<details> <summary>Asynchronous Design</summary> </br> Networking will be more performant and versatile by using Tokio. It will permit the simultaneous connections of a hundred peers. Handling different protocols by peers will be possible in a modular manner.</details>
<details> <summary>Traffic Obfuscation</summary> </br> Different protocol to bypass DPI will be available, such as with <a href="https://github.com/vtnerd/monero/blob/docs_p2p_e2e/docs/LEVIN_PROTOCOL.md#encryption">Levin protocol</a> (TLS based, see https://github.com/monero-project/monero/issues/7078) and QUIC <a href="https://github.com/syncthing/syncthing/pull/5737">like Syncthing have done</a>, but with offset and timing mitigations. Unless the monero-core team decide to implement these protocols, they'll only by available between cuprate peers.</details> <details> <summary>Traffic Obfuscation</summary> </br> Different protocol to bypass DPI will be available, such as with <a href="https://github.com/vtnerd/monero/blob/docs_p2p_e2e/docs/LEVIN_PROTOCOL.md#encryption">Levin protocol</a> (TLS based, see https://github.com/monero-project/monero/issues/7078) and QUIC <a href="https://github.com/syncthing/syncthing/pull/5737">like Syncthing have done</a>, but with offset and timing mitigations. Unless the monero-core team decide to implement these protocols, they'll only by available between cuprate peers.</details>
<details> <summary>Blockchain Storage</summary> </br>LMDB is replaced by RocksDB, a high-performance database designed for SSD, already used by the Parity ethereum's rust client. HSE is also going to be implemented, as a more dsitributed and scalable alternative. </details> <details> <summary>Blockchain Storage</summary> </br>LMDB is replaced by RocksDB, a high-performance database designed for SSD, already used by the Parity ethereum's rust client. HSE is also going to be implemented, as a more dsitributed and scalable alternative. </details>