ICE-NET/docs/community/announcement_en.md
loki5512344 2e61688eb3
Some checks failed
rust-ci / checks (push) Has been cancelled
Initial import: ICE-NET research docs and Rust workspace (v0.4)
- Rust workspace: 7 library crates, icenetd CLI, icenet-city (Slint GUI)
- Sim: fix false Delivered after a route cut, derive traffic class from
  payload size, per-link airtime slots (link capacity, queueing)
- Docs: single docs/STATUS.md for all figures, remove v0.2/egui leftovers,
  drop unimplemented seed claims, uncheck store-and-forward
- License: LGPL-3.0-or-later (LICENSE, LICENSES/GPL-3.0.txt)
2026-11-13 12:28:48 +01:00

16 lines
854 B
Markdown

# Community post draft (EN)
Hi! I'm experimenting with ICE-NET, a research-oriented Rust project inspired by
the Net of cyberpunk fiction: an identity-centric network that can span multiple underlying links, including
wired, IP, Wi-Fi, and low-bandwidth radio.
Our first falsifiable hypothesis is that a strict, measurable scheduling
policy can keep slow radio available for discovery and tiny messages while
sending bulk data only through appropriate higher-capacity paths.
This is currently a graph-based simulator and a set of protocol design notes,
not an operating wireless network. I'd love critical feedback on routing,
control-plane airtime, failure handling, and comparisons to Reticulum and
Meshtastic. Please suggest reproducible scenarios rather than feature lists.
Repository: https://git.wihuk.pro/boba/ICE-NET.git (LGPL-3.0-or-later).