docs: retarget README to Reticulum 1.3.8

This commit is contained in:
DeFiDude 2026-07-17 08:38:11 -06:00
parent 6c8dba7dd4
commit 27e6d03235

View file

@ -7,7 +7,7 @@
[![License: AGPL-3.0-or-later](https://img.shields.io/badge/license-AGPL--3.0--or--later-blue.svg)](LICENSE)
[![Rust 1.85+](https://img.shields.io/badge/rust-1.85%2B-orange.svg)](https://www.rust-lang.org)
[![Reticulum 1.2.5](https://img.shields.io/badge/target-Reticulum%201.2.5-success.svg)](https://reticulum.network/)
[![Reticulum 1.3.8](https://img.shields.io/badge/target-Reticulum%201.3.8-success.svg)](https://reticulum.network/)
[![Status](https://img.shields.io/badge/status-experimental-yellow.svg)](#feature-status)
[Reticulum Manual](https://reticulum.network/manual/) |
@ -150,7 +150,7 @@ intentional.
`rnodeconf-rs` in the current build only covers safe inspection/device setting paths, EEPROM
dump/backup, and trusted-key storage.
`rnid-rs` tracks the Reticulum 1.2.5 identity utility surface for normal
`rnid-rs` tracks the Reticulum 1.3.8 identity utility surface for normal
software identities: public/private import and export, destination hashing,
`.pub` public identity files, and signed `.rsg` signature files. The
hardware-backed `rnid-rs hw` path is a Rust extension behind the `hardware`
@ -174,7 +174,7 @@ rnid-rs -i ~/.rsReticulum/identities/mgmt -X -w mgmt.rid
rnid-rs -m <public_identity_data> -w peer.pub
rnid-rs -M <private_identity_data> -X -w restored_identity
# Sign and validate. New signatures are Reticulum 1.2.5 .rsg envelopes.
# Sign and validate. New signatures are Reticulum 1.3.8 .rsg envelopes.
rnid-rs -i ~/.rsReticulum/identities/mgmt -s message.txt
rnid-rs -V message.txt.rsg
rnid-rs -i <signer_hash> -N -V message.txt.rsg
@ -186,7 +186,7 @@ rnid-rs -i ~/.rsReticulum/identities/mgmt -d message.txt.rfe
Use `--raw -s <file>` only when a workflow intentionally needs the legacy raw
64-byte signature form. Normal `rnid-rs -s <file>` produces a `.rsg` file that
embeds the signer metadata needed for 1.2.5 validation.
embeds the signer metadata needed for 1.3.8 validation.
## Configuration
@ -252,7 +252,7 @@ instance_control_port = 37433
| BLE RNode | Config-backed with the `ble` feature. |
| Bluetooth Peer | Runtime API used by Ratspeak. |
| Android USB-OTG | Runtime API for Android app embeddings. |
| Weave | Not implemented. |
| Weave | Partial: interface driver implemented, not yet config-wired in the runtime. |
| Bluetooth Classic RFCOMM | Not implemented. |
## Compatibility Notes
@ -261,8 +261,8 @@ Most daemon and utility flows are implemented for the public `*-rs` tools:
`rnsd-rs`, `rnstatus-rs`, `rnpath-rs`, `rnid-rs`, `rnprobe-rs`, `rncp-rs`,
`rnsh-rs`, and `rnodeconf-rs`.
The current compatibility target is Reticulum 1.2.5 where the matching Rust
surface is implemented and tested. `rnid-rs` has explicit 1.2.5 coverage for
The current compatibility target is Reticulum 1.3.8 where the matching Rust
surface is implemented and tested. `rnid-rs` has explicit 1.3.8 coverage for
the normal identity utility flow.
Known gaps and intentional limits: