Expand description
WebRTC peer-to-peer connectivity for hashtree data exchange
Uses Nostr relays for signaling with the same protocol as iris-client:
- Event kind: 30078 (KIND_APP_DATA)
- Tag: [“l”, “webrtc”]
- Message types: hello, offer, answer, candidate
Re-exports§
pub use types::DataMessage;pub use types::DataRequest;pub use types::PeerDirection;pub use types::PeerId;pub use types::PeerPool;pub use types::PoolConfig;pub use types::PoolSettings;pub use types::SignalingMessage;pub use types::WebRTCConfig;pub use types::encode_request;pub use types::MAX_HTL;
Modules§
- types
- WebRTC signaling types compatible with iris-client and hashtree-ts
Structs§
- Peer
- WebRTC peer connection with data channel protocol
- Peer
Entry - Peer entry in the manager
- Pending
Request - Pending request tracking (keyed by hash hex)
- WebRTC
Manager - WebRTC manager handles peer discovery and connection management
- WebRTC
State - Shared state for WebRTC manager
Enums§
- Connection
State - Connection state for a peer
Traits§
- Content
Store - Trait for content storage that can be used by WebRTC peers
Type Aliases§
- Peer
Classifier - Callback type for classifying peers into pools